Bugzilla – Bug 188560
YAST2 - NSF Client Browse for NFS server does not work unless IP address of NFS Server is entered
Last modified: 2008-06-03 10:19:41 UTC
Situation. Firewall temporarily disabled on both NFS Server and client NFS Client> Choose> result empty. BUT IF NFS Client> enter IP address of server> Select remote file system> result directories are displayed as normal. NFS functionality not impeded with entering IP address of server in any application let alone YAST when browse fails or Host Name does not work.
What do you get when you run this as root? This is what yast uses to detect nfs servers. # /usr/sbin/rpcinfo -b mountd 1
1. I am su when in YAST 2. # performed as su at console>result no display eventual time out.
*** Bug 132490 has been marked as a duplicate of this bug. ***
If you have all requested info pleas change status New or Aggigned
Q.A Repeat do you have all info or change status to Assigned or Invalid or ....
Created attachment 102201 [details] .jpg output re comment 2# Personally I see nothing wrong with referring to a PC by IP. But you have decided on using names references which I find more difficult to recall. So, regrettably I publish this bug. IF your problem with this is DHCP being used and the device holding the NFS drive possibly changing IP. Then I suggest that the world does NOT run on DHCP as it is far too dangerous to hand the keys to your server to ANYONE who can plug in. I am a security consultant by trade and whilst DHCP is convenient - it is NEVER used in secure installations. P.S the CUPS server only works on nominating an IP as well rather than the name.!
This is strange. Please verify on the server that the firewall is indeed not filtering the packets (iptables -L) and portmap is listening (netstat --inet -a | grep sunrpc) and mountd is listening (rpcinfo -p). All the server is running Linux :) Do you recall doing anything special with the server setup? You can also try watching the network traffic using tcpdump while retrying the rpcinfo from comment 1. I do not understand comment 6. It seems it belongs to a different bug. BTW it is wasteful to attach a 1.6MB picture when you could have pasted the three lines of text from the terminal instead.
I have had to re-build a new system and this bug has not been look at since last months so please bear with me. 1. In response to item output is as follows. - NIL and eventual time-out as before as a new prompt is eventually displayed. couston@multivac-ii:~> su Password: multivac-ii:/home/couston # /usr/sbin/rpcinfo -b mountd 1 As we are dealing with YAST the obligatory files are also attached, however your published save command doenot always work a another tech and I worked a way of compressing the YAST log files as attached. I have also zipped the screen shot to save space.
Created attachment 105171 [details] 1 of 2 yast files
Created attachment 105175 [details] 2 of 2 yast log files
In this case the yast logs do not contain the relevant info and you did not need to attach them. That is why I asked you to check the commands in comment 7.
I have no understanding of what you wish me to do re comment #7 to indicate the information you require. I attached the YAST2s as each and every time I speak of an issue with yast comes an automatic request for the files. Tis strange the one time you do not require logs with a yast issue and I attached them I still do the wrong thing. However lets us move on with issue #7. The firewall has the following services open NFS client as the only entry and everything works perfectly. Without the NFS client being present I could not see of the servers NFS Server as per screen shot. Please supply the command lines you require for 7# and I will relay their output. As far as installation went, straight vanilla. Nothing had to be done over on either the client NFS or Server NFS. Installations are very easy and straight forward without error. Please offer command line input you requie for #7 on both Server and client I do not think I can get etheral to capture the appropriate TCP dump. The issue that I CAN see the NFS drives when I enter an IP certaily indicates that packetsare being sent and accepted. I can copy and do large amounts of data between the NFS drives. There is nothing unusual or different in the behaviour or both PC's every application does as it should usng a KDE desktop. thanks..Tis late talk after I have had a few hours sleep. regards
The only other strangle things that comps to lite is the NFS Server is also the cups server. And static IP of the cups server was required for it to be found. Over the mailing lists no-one recognises this as a bug - If someone has a problem locating a PC the advice always given is to supply the IP address of the PC. There are 5 PC's on the LAN, all static IP NO DHCP. No PC serves as a routing - all hardware, NO NIS, Only NTP server works just fine , No DNS services are supplied by any PC - all done via hardware. Network runs like a dream clock. As I said the email forums ALL say use the IP of the PC you want to provide the service. No one is confident to rely on name formates. I do NOT use IFUP only network manager like most.
Changing maintainers.
closed due NOACK and No confidence bug opened in 2006 an is still an problem
Add CC