|
Bugzilla – Full Text Bug Listing |
| Summary: | yast2-nfs-client cannot locate any nfs server | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE LINUX 10.0 | Reporter: | Gilles Sabourin <sabourin.gilles> |
| Component: | YaST2 | Assignee: | Martin Vidner <mvidner> |
| Status: | RESOLVED DUPLICATE | QA Contact: | Klaus Kämpf <kkaempf> |
| Severity: | Minor | ||
| Priority: | P5 - None | ||
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | 32bit | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Found By: | Customer | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
nfs server search function testcase
Hardware info / Network nfs server search function testcase |
||
|
Description
Gilles Sabourin
2005-11-06 08:42:51 UTC
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 *** |