https://bugzilla.novell.com/show_bug.cgi?id=727870 https://bugzilla.novell.com/show_bug.cgi?id=727870#c5 --- Comment #5 from Lukas Ocilka <locilka@suse.com> 2011-11-15 13:17:30 UTC --- (In reply to comment #0)
Steps to Reproduce: 1.I have a NFS Server running on IP 192.168.1.20 2.I setup a NFS Client and IF I enter the Servers IP above I see the directories. 3.If I use the 'Choose' button no NFS Servers are found in the first instance. THE FIREWALL IS NEVER THE PROBLEM - the error response is erroneous always, always, always. Actual Results: Every single server, client, or locate printer or locate host in Yast fails and has never work as tested on my network since Suse Linux 10.0 to current.
I've reproduced the issue you've reported, except the problem was the firewall. bestie:~ # rcSuSEfirewall2 status Checking the status of SuSEfirewall2 running bestie:~ # yast2 nfs-client # Here, YaST NFS Client could not find any NFS server bestie:~ # rcSuSEfirewall2 stop Unloading firewall rules done bestie:~ # yast2 nfs-client # Here it was able to find all NFS servers around If it doesn't work for you, there might be several reasons: 1.) NFS server doesn't reply for a broadcast 2.) Your firewall is on even if it says it's off 3.) Your router doesn't support broadcast or drop the packets somehow 4.) Your NFS client is in a different network to your NFS server and thus unreachable by brodcast You can easily check the packets going back and forth by tcpdump: tcpdump -n port 111 Run this command before starting YaST, then perform the network search and evaluate the tcpdump output. You should find one or more UDP packets sent from $YOUR_CLIENT.$SOME_HIGH_PORT to $NETWORK.255.111 And get one or more UDP replies from $SERVER.111 to $YOUR_CLIENT.$SOME_HIGH_PORT -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.