On Mon, 2005-12-26 at 21:56 -0800, bernd wrote:
On Friday 23 December 2005 18:01, Carl Hartung wrote: <snip>
Sorry for the delay, but it's family and holidays time of year again...
Here are some diagnostic steps to take:
Post a copy of your /etc/hosts file and your /etc/resolv.conf file. Run "lpstat -t" on Machines #1 and #2 and post here.
regards,
- Carl
Thanks for taking the time!
***Machine #2:***
/etc/hosts:
# # hosts This file describes a number of hostname-to-address # mappings for the TCP/IP subsystem. It is mostly # used at boot time, when no name servers are running. # On small systems, this file can be used instead of a # "named" name server. # Syntax: # # IP-Address Full-Qualified-Hostname Short-Hostname #
127.0.0.1 localhost 192.168.1.100 officesuse.koepsell officesuse
# special IPv6 addresses ::1 localhost ipv6-localhost ipv6-loopback
fe00::0 ipv6-localnet
ff00::0 ipv6-mcastprefix ff02::1 ipv6-allnodes ff02::2 ipv6-allrouters ff02::3 ipv6-allhosts 192.168.1.101 paf.koepsell paf 127.0.0.2 suse.koepsell suse
Why do you have this entry, it is not needed and is confusing. Delete it.
# with -R. If you only want to keep your searchlist, set # DHCLIENT_KEEP_SEARCHLIST=yes in /etc/sysconfig/network/dhcp or # (manually) use the -K option. # ### END INFO search ver 69.28.32.180
Is this just a typo?
nameserver 69.28.32.16 nameserver 69.28.32.180
/etc/hosts:
# # hosts This file describes a number of hostname-to-address # mappings for the TCP/IP subsystem. It is mostly # used at boot time, when no name servers are running. # On small systems, this file can be used instead of a # "named" name server. # Syntax: # # IP-Address Full-Qualified-Hostname Short-Hostname #
127.0.0.1 localhost
# special IPv6 addresses ::1 localhost ipv6-localhost ipv6-loopback
fe00::0 ipv6-localnet
ff00::0 ipv6-mcastprefix ff02::1 ipv6-allnodes ff02::2 ipv6-allrouters ff02::3 ipv6-allhosts 192.168.1.101 paf.koepsell paf 192.168.1.102 suse.koepsell suse 127.0.0.2 officesuse.koepsell officesuse
Same with this entry, delete it and give officesuse the same address as it has in it's hosts file which is 192.168.1.100. One ip address per customer is all that is needed. The localhost 127.0.0.1 address has special meaning.
Something just happens to jump right out. The /etc/hosts file does not match what my router-based dhcp server has assigned to the machines.
I hear a collective DUH! coming from the throngs on suse-e regarding the hosts file! Yet...
I just manually changed the /etc/hosts file on the machines to reflect the correct ip's and ran a test.
If you are going to use DHCP then leave the /etc/hosts files alone. You are causing one naming system to fight with the other. Either use DHCP or the hosts file, not both. If this is not a small lab setup why use DHCP at all? Each machine needs to be asigned one address, which is what DHCP will do if setup correctly. You also have three different host names but only show the /etc/hosts file for two. The three host names: paf.koepsell 192.168.1.101 officesuse.koepsell 192.168.1.100 and 127.0.0.2 suse.koepsell 192.168.1.102 and 127.0.0.2 You have two different host names assigned the same address 127.0.0.2 address which should not be used at all in the first place. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998