Bugzilla – Bug 132490
yast2-nfs-client cannot locate any nfs server
Last modified: 2006-10-13 12:30:14 UTC
in nfs client configuration, whenever you want to add a nfs name server / ip address, you can simply write down an ip address or you can click on select button to have a list of nfs server in your local network. This automatic search does not work and return always (unknown), even if the nfs server is running on the same machine! As I cannot see anything interesting in yast2 logs, I wonder if this function is really implemented.
Please attach the logfiles nontheless. Also attach `hwinfo --network' and explain your configuration more detail. Thanks.
Created attachment 56611 [details] nfs server search function testcase
Created attachment 56612 [details] Hardware info / Network
Why are you attaching the same log-snippet as in bug #132461 here? You're adressing another problem there. Check that condition first.
Created attachment 56626 [details] nfs server search function testcase Sorry Michael, I've made a mismatch between my logs. Here's the good one.
I have also added explicitly nfs client and server as authorized services in firewall configuration. My configuration is the following : 3 PC connected to a WRT54GS router with #4.70.6 firmware - 2 desktop linked on 100 Mb LAN interfaces of the router - 1 laptop connected with a wifi radio link I have noticed the same problem on the desktop where the nfs server is running or on the laptop.
Reassigning it to the maintainer.
I think it is the same as bug 55582. The discovery is done by broadcast pings which are blocked since some time. I need to port the fix to Code 10.
Actually no, that should have been fixed in bug 71064, 8 months earlier. Let's track this together with a recent report. *** This bug has been marked as a duplicate of bug 188560 ***