Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

We have a machine with Win7-x64 installed. On this machine, with VirtualBox, we're running a guest Fedora-x64. We've defined an NFS share on this Fedora instance. Here is the entry in /etc/exports:

/dvr 192.168.0.0/192.168.255.255(rw)

The ip address of the windows machine is, 192.168.1.100, the ip address of the Fedora guest is 192.168.1.110. The networking mode of the VM is set to be bridged networking.

Now, from another linux box, when we ping the Fedora guest (192.168.1.110), we get responses just fine. However, when we try to mount the nfs share, we get a "no route to host" error. The command we use is:

mount -t nfs 192.168.1.110:/dvr /mnt/test

Just to make sure there are no iptables issues, on the fedora guest, we did:

service iptables stop

and re-tried to mount, to no avail.

Any ideas what might be wrong in our setup? All these machines are connected to each other through a hub. A linksys router is configured as a DHCP server, from which all the machines grab an ip address.

Thanks.

share|improve this question

2 Answers 2

Fedora uses firewalld as the firewall these days. Stopping iptables directly is not the correct way to stop the firewall. Try systemctl stop firewalld.service instead.

You have started the NFS service on the Fedora VM haven't you?

You'd do that by running systemctl start nfs.service on the VM.

If you've changed the /etc/exports file since starting the nfsd, then you need to either systemctl restart nfs.service or re-export filesystems with the exportfs -a command.

share|improve this answer

/etc/exports expects an IP address, optionally followed by a CIDR or old-style netmask.

So you need to change it to one of:

/dvr 192.168.0.0/255.255.0.0(rw)

or:

/dvr 192.168.0.0/16(rw)

(Hostnames can also be used, but that's not relevant here.)

share|improve this answer
    
thanks for the very fast response. We tried that as well without success. We also tried 255.255.255.0, with no success. After each change to /etc/exports, we did a "service nfs-server restart". Do we have to do anything else? –  SomethingBetter Feb 25 '13 at 7:33
    
Just to be clear, it should be "/dvr 192.168.1.0/255.255.255.0(rw)", correct? This would make 192.168.1.0-192.168.1.255 to be available? –  SomethingBetter Feb 25 '13 at 7:41
    
If that's the network you want to be accessible, then yes. –  Michael Hampton Feb 25 '13 at 7:42
    
Hmm. still no go. Any more ideas? Just noticed that, running rpcinfo -p 192.168.1.110 on the linux machine results in "can't contact portmapper". However, on the linux guest, portmapper service seems to be running. –  SomethingBetter Feb 25 '13 at 8:36
    
You have a network or firewall issue, then. –  Michael Hampton Feb 25 '13 at 8:37

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.