[NTLUG:Discuss] SuSE and nfs
Leroy Tennison
leroy_tennison at prodigy.net
Tue Jul 12 05:01:25 CDT 2005
Chris Cox wrote:
>Fred wrote:
>
>
>>I am running suse 9.1 on one box (2.6 kernel) and suse 8.2 (2.4
>>kernel) on another. The 8.2 is wifi to a 4-port router, the 9.1 is
>>wired to the same router. They are 192.168.1.102 and 192.168.1.100,
>>respectively.
>>
>>I set up the nfs server on the 9.1 box with the yast tool which seems
>>to have put everything in the right places (/etc/exports, for ex). I
>>then set up nfs client on the 8.2 box... or tried to. Here's the
>>problem: the browse feature on the client setup only shows itself
>>(192.168.1.102) and does not show the 9.1 box.
>>
>>I verified that the nfs ports (2049) were open on the 9.1 box.
>>
>>Also, I set up the nfs server as 192.168.1.100, the server directory
>>as /tmp (to test with since it is global readable) and /mnt as the
>>directory to mount on the client box. The entry in 8.1 box /etc/fstab
>>looks ok:
>>192.168.1.100:/tmp /mnt nfs defaults 0 0
>>
>>but it won't mount. In fact, it just hangs and will eventually time
>>out with a can't connect message.
>>
>>I can ssh from 8.2 to 9.1. Likewise, I can ping 9.1. So what am I
>>doing wrong?
>>
>>Thanks,
>>Fred
>>
>>
>
>Does the reverse (PTR) lookup resolve on the server for the client??
>If not, try adding a static entry for the client in /etc/hosts on
>the NFS server and see if that allows you to connect.
>
>_______________________________________________
>https://ntlug.org/mailman/listinfo/discuss
>
>
>
What about the firewall on your client, could it be blocking nfs?
More information about the Discuss
mailing list