[SOLVED] Fedora 16 nfs server won't let me mount from client

SharpyWarpy · 05-01-2012, 04:25 PM

Hi, all. I just installed Fedora 16 on my LAN server PC. I can't get my laptop running 16 also to mount a filesystem on the server.
I didn't have this problem before when the server was running Fedora 12 but now I get

Code:

mount -v /mnt/sdc1
mount.nfs: timeout set for Tue May  1 15:58:21 2012
mount.nfs: trying text-based options 'vers=4,addr=192.168.0.4,clientaddr=192.168.0.5'
mount.nfs: mount(2): No such file or directory
mount.nfs: trying text-based options 'addr=192.168.0.4'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: portmap query failed: RPC: Remote system error - No route to host
mount.nfs: trying text-based options 'vers=4,addr=192.168.0.4,clientaddr=192.168.0.5'
mount.nfs: mount(2): No such file or directory
mount.nfs: trying text-based options 'addr=192.168.0.4'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: portmap query failed: RPC: Remote system error - No route to host
mount.nfs: trying text-based options 'vers=4,addr=192.168.0.4,clientaddr=192.168.0.5'
mount.nfs: mount(2): No such file or directory
mount.nfs: trying text-based options 'addr=192.168.0.4'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: portmap query failed: RPC: Remote system error - No route to host

Now, on the server I have set up configuration every way I know how but this new "systemctl" and "systemd" is kicking my butt. Here is my /etc/hosts content on the server

Code:

127.0.0.1   localhost localhost.localdomain localhost4 localhost4.localdomain4 server
::1         localhost localhost.localdomain localhost6 localhost6.localdomain6 server
192.168.0.5     toshiba
192.168.0.10    sharpy

And on the server, here is the content of /etc/exports

Code:

/            toshiba(rw,no_root_squash)
/mnt         toshiba(rw,no_root_squash)
/mnt/sda1    toshiba(rw,no_root_squash)
/mnt/sdc1    toshiba(rw,sync,no_root_squash)

Here is server /etc/hosts.allow

Code:

# hosts.allowThis file contains access rules which are used to
#allow or deny connections to network services that
#either use the tcp_wrappers library or that have been
#started through a tcp_wrappers-enabled xinetd.
#
#See 'man 5 hosts_options' and 'man 5 hosts_access'
#for information on rule syntax.
#See 'man tcpd' for information on tcp_wrappers
#
ALL: ALL: ALLOW

Now, I have run "exportfs -a -r" after starting nfsd with "systemctl start nfs-server.service" and it ran okay. I rebooted and rpc.mountd actually started automatically. The nfs daemon is another problem because of my lack of knowledge of the new way of getting it to start on boot. Yeah, I've read the manuals on both systemctl and systemd and still can't get figure THAT out. But
even after I start the nfs daemon manually as I said before I still can't get the client maching (laptop) to mount a filesystem from the server. The content of fstab on the laptop is

Code:

# Accessible filesystems, by reference, are maintained under '/dev/disk' 
# See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info
#
UUID=5630a7df-0d15-4239-b491-2b907efed51b /     ext4    defaults         1 1
UUID=a788c6fe-db0b-4e61-8086-4680434ee798 swap  swap    defaults         0 0
192.168.0.4:/mnt/sdc1  /mnt/sdc1_server nfs rw,noauto,user,exec,dev,suid 0 0
/dev/sr0   /media/cdrecorder   iso9660 defaults,noauto               0 0

I will provide any other information necessary. Any help will be very, very much appreciated because that 1tb WD HDD on the server
has all my photos, music, assorted storage and backups.

EDIT: Apparently the problem is with a setting in iptables. I can disable the firewall on the server and I can then mount the nfs filesystem.

SharpyWarpy · 05-01-2012, 11:48 PM

Okay I got it fixed reading this link:
http://www.linuxquestions.org/questi...server-889664/
It's funny 'cause this forum's search engine did not show that thread. I searched all kinds of ways using various key words but the way I found it was via Google. Now, I don't like having to use Google to find stuff like this, especially since they dropped "www.google.com/linux", but I wasn't getting any replies and I Googled for 4 hours, taking small breaks from time to time regaining my composure. But here it is, a solution. If you scroll way on down the page you'll find a reference to the "rpcinfo" utility and a way to use it to find out which ports rpc uses. Well when I ran the commands it spit out a bunch of port numbers with other extreaneous information, I then opened the GUI firewall tool and clicked on "Other Ports" and couldn't even see several of the ports but I found one key port -- 20048. I highlighted the tcp version of that port and enabled it. I had already enabled the tcp protocol ports 111 and 2049. Those three ports opened allowed me to mount the HDD partition on the server on my laptop.