https://bugzilla.novell.com/show_bug.cgi?id=727870 https://bugzilla.novell.com/show_bug.cgi?id=727870#c3 Scott Couston <scott@aphofis.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |scott@aphofis.com --- Comment #3 from Scott Couston <scott@aphofis.com> 2011-11-03 21:13:30 UTC --- DHCP will always try to use the same mappings - unless a netadmin has cause to instruct termination of these mappings via a Router. It is NOT fare to say that you can ALWAYS reply on a Workstation to always have the same IP if DHCP allocates it. The only completely safe way is to create static IP's - Yes. Now on to the Issue...The problem is that ANY yast application, like the example, cannot auto locate workstation or devices on the network, without the user entering the actual IP. THE PROBLEM IS NOT THE FIREWALL! Look at the attached example again - you can see that in the case of a NFS Client, that using the 'Choose' button, NO NFS Server is found on the Network with exported directories. The only way to locate exported directories is by entering the IP of the NFS Server Workstation. In respect to the printer Module, I have no problems using the connection wizard with a TCP Port 9100 IF I input the IP of the device. If I use 'scan all hosts' etc. which relies on the same preface as the 'choose button' the device is not found. If I input the IP of the printer in the device is found immediately. Most all of the Network Services in Yast have a Server/Client type relationship, yet using the 'choose' or 'browse' of 'find' option does NOT find their partner. In all cases it only works by entering the IP as the 'Host Lookup' has never worked. If you would like me to further clarify with any other Yast Network Service please ask and I will, capture the image -- 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.