what ports need to be opened for NAT

Article:TECH145412  |  Created: 2010-12-02  |  Updated: 2010-12-02  |  Article URL http://www.symantec.com/docs/TECH145412
Article Type
Technical Solution


Environment

Problem



what ports need to be opened for NAT


Error



sudo mount -t nfs
217.27.88.119:/vx/fs2 /Users/cormil/mnt
mount_nfs: bad MNT RPC: RPC: Timed out\n
mount_nfs: bad MNT RPC: RPC: Timed out\n
mount_nfs: can't access /vx/fs2: Permission denied

 


Environment



Filestore 5.5


Cause



configuration on nfs share


Solution



nfs> server status
nfs> share show
network> ip addr show
network> ip route show

while mounting from the client, collect ethereal traces from filestore nodes using
# tethereal -i any -w /tmp/nfs_node01.trace port 2049 or port 4001 or port 111 and host not 127.0.0.1

Once verification is done to ensure mounts from internal network are successful, from the client try telnet to filestore

# telnet 217.27.88.119 111
# telnet 217.27.88.119 2049
# telnet 217.27.88.119 4001

Ports that need to be opened are:

2049 nfs (core nfs protocol)
4001 mountd
4045 NLM (NFS locking protocol)
portmappper is run on 111
Both TCP and UDP ports on 111,2049,4001,4045

Note Due to the way nfs works on Linux you might also need to add the insecure option to any volumes you export on certain clients.

On filestore the default nfs share option is 'secure' this means it will use ports in reserved port range (less than 1024). if insecure is set - then it can use ports outside that range.

 




Article URL http://www.symantec.com/docs/TECH145412


Terms of use for this information are found in Legal Notices