NFS

[Dagmar Bendová]

Nfs is running on both servers and I have released port 111 and 2049 on firewall.

If I run rpc -p ... it finish at error:
rpcinfo: can't contact portmapper: RPC: Rpcbind failure - RPC: Failed (unspecified error)
Which port have to be still allowed to access?

[Vijaya Kumar_3]

hmm...did u check rpcbind is running in the server? Check with "ps -ef"

Are you able to access the NFS shares inside firewall.

Also, try bouncing NFS Server..

-Vijay

[Fabio Ettore]

Hi,

the only one time that I saw this error was a wronged IP address configured into /etc/hosts file. Try to check it.
Just a thought...

Best regards,
Ettore

[Sergejs Svitnevs]

Try to find packets being dropped at the firewall log file.

Regards,
Sergejs

[Stuart Abramson_2]

We had a problem like this once.

The problem is that the NFS client establishes connection to the NFS server on fixed ports (2049), but once the original request is established, the daemons involved request and use a random unused port for each server-client nfs export-mount transfer. You can't just "open a port" to get NFS mounts to work.

Basically the issue is that:

"nfsd uses port 2049. However, the ports used by mountd, statd and other rpc daemons are not static. So, there is no predictable way to open specific ports for NFS on the firewall.

"..if your firewall is RPC-aware, e.g. firewall software such as Checkpoint (and others), you can perhaps setup rules that check with the nfs portmapper to figure out which ports are being used at any time and allows nfs traffic thru those ports..".