0

I am not able to mount a drive that is located on server A to server B. I have followed this document step by step just replacing portmap to rpcbind as the system installed rpcbind instead of portmap. I am getting the below exception when I try to mount the file system.

mount.nfs connection timed out

My servers are located on Microsoft Azure. I tried pinging from client(server B) to server A but I was not able to. I believe it is a port issue but how to rectify that I am not able to get it.

Please let me know what i need to check to get it working.

1 Answer 1

0

Check telneting to the port on the Azure server, if that fails you might have to modify the Azure servers security group and add a rule that allows ingress to Port 111 (TCP and UDP) and 2049 (TCP and UDP) for the NFS server, and egress rules for the client. if they are on the same subnet then something else is wrong.

https://azure.microsoft.com/en-us/documentation/articles/virtual-networks-nsg/

3
  • also check local firewalls such as firewalld or iptables
    – Sum1sAdmin
    Apr 8, 2016 at 12:56
  • Thanks Rob, It was a port issue, I was able to mount the directory. I added the ingress rule on my server A and was able to mount the drive on server B as you said. I want to know, is it necessary to add egress rule also on my server A as it seems to be working fine without it. Apr 11, 2016 at 6:26
  • I think in azure the default outbound rule (egress) is for all ports so you should be fine with the default
    – Sum1sAdmin
    Apr 11, 2016 at 8:24

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .