Re: [SLE] Why isn't my LAN, etc. working??? (SuSE 9.3)
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 /etc/resolv.conf: ### BEGIN INFO # # Modified_by: dhcpcd # Backup: /etc/resolv.conf.saved.by.dhcpcd.wlan0 # Process: dhcpcd # Process_id: 11724 # Script: /sbin/modify_resolvconf # Saveto: # Info: This is a temporary resolv.conf created by service dhcpcd. # The previous file has been saved and will be restored later. # # If you don't like your resolv.conf to be changed, you # can set MODIFY_{RESOLV,NAMED}_CONF_DYNAMICALLY=no. This # variables are placed in /etc/sysconfig/network/config. # # You can also configure service dhcpcd not to modify it. # # If you don't like dhcpcd to change your nameserver # settings # then either set DHCLIENT_MODIFY_RESOLV_CONF=no # in /etc/sysconfig/network/dhcp, or # set MODIFY_RESOLV_CONF_DYNAMICALLY=no in # /etc/sysconfig/network/config or (manually) use dhcpcd # 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 nameserver 69.28.32.16 nameserver 69.28.32.180 lpstat -t: suse:/home/bernd # lpstat -t lpstat: Unable to connect to server: Connection refused ***Machine #1:*** /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 /etc/resolv.conf: ### BEGIN INFO # # Modified_by: dhcpcd # Backup: /etc/resolv.conf.saved.by.dhcpcd.wlan0 # Process: dhcpcd # Process_id: 5380 # Script: /sbin/modify_resolvconf # Saveto: # Info: This is a temporary resolv.conf created by service dhcpcd. # The previous file has been saved and will be restored later. # # If you don't like your resolv.conf to be changed, you # can set MODIFY_{RESOLV,NAMED}_CONF_DYNAMICALLY=no. This # variables are placed in /etc/sysconfig/network/config. # # You can also configure service dhcpcd not to modify it. # # If you don't like dhcpcd to change your nameserver # settings # then either set DHCLIENT_MODIFY_RESOLV_CONF=no # in /etc/sysconfig/network/dhcp, or # set MODIFY_RESOLV_CONF_DYNAMICALLY=no in # /etc/sysconfig/network/config or (manually) use dhcpcd # 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 koepsell nameserver 69.28.32.16 nameserver 69.28.32.180 lpstat -t: officesuse:~ # lpstat -t scheduler is running system default destination: deskjet940c device for deskjet940c: usb://HP/DeskJet%20940C?serial=CN2671B1VYCO device for laserjet4l: parallel:/dev/lp0 deskjet940c accepting requests since Jan 01 00:00 laserjet4l accepting requests since Jan 01 00:00 printer deskjet940c is idle. enabled since Jan 01 00:00 printer laserjet4l is idle. enabled since Jan 01 00:00 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. CUPS up and printing fine from machine #2 with OOo, but not from any other apps! Here's an error message I get when trying to print my e-mail from Kontact: "An error occurred while retrieving the printer list: Connection to CUPS server failed. Check that the CUPS server is correctly installed and running. Error: host not found." Here's the lpstat results from machine #2: bernd@suse:~> lpstat -t lpstat: Unable to connect to server: No route to host How can the /etc/hosts file be modified to always match? How can I print using apps aside from OOo?
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
On Tuesday 27 December 2005 04:53, Ken Schneider wrote: <snip>
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.
I did not manually add the 127.0.0.2, so I "assumed" it was necessary.
# 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?
Is what a typo???
nameserver 69.28.32.16 nameserver 69.28.32.180
<snip>
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
Deleting 127.0.0.2 on both machines! paf.koepsell is a windoze machine. I have changed its' hosts and lmhosts files to reflect the correct addresses. I have changed the hosts files to reflect the correct ip's for each suse machine also. My ip's are set by my linksys routers dhcp server. The /etc/hosts does not automatically change to reflect any changes in the ip's from the linksys router. Should I disable the linksys routers dhcp server and set static addresses??? I have 3 machines, and at most will have 2 more in the future. Thanks you guys! Bernd
Something I learned recently that might be useful here (or might not) is that there are three ways of assigning IP addresses in the presence of a DHCP server such as the one built into the Linksys routers: 1. Assign a static IP address outside the range allotted to DHCP. 2. Let DHCP assign the address, which might change. 3. Assign a static IP address through DHCP, specifying it in the appropriate section of the router setup screens. This address, unlike #1, will be in the DHCP range. I hadn't realized that #3 is possible. Paul
On Tue, 2005-12-27 at 13:01 -0500, Paul W. Abrahams wrote:
Something I learned recently that might be useful here (or might not) is that there are three ways of assigning IP addresses in the presence of a DHCP server such as the one built into the Linksys routers:
1. Assign a static IP address outside the range allotted to DHCP. 2. Let DHCP assign the address, which might change. 3. Assign a static IP address through DHCP, specifying it in the appropriate section of the router setup screens. This address, unlike #1, will be in the DHCP range.
I hadn't realized that #3 is possible.
The place I worked for I would use it for printers sent to remote offices that needed a static address. I would setup the entry in the DHCP server using the mac address so that a predefined IP address would be assigned. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998
On Tue, 2005-12-27 at 09:23 -0800, bernd wrote:
On Tuesday 27 December 2005 04:53, Ken Schneider wrote: <snip>
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.
I did not manually add the 127.0.0.2, so I "assumed" it was necessary.
OK. It had to added by something as it is certainly not the default entry for everyone, perhaps something youo set in YaST.
# 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?
Is what a typo???
The search criteria should be a domain name not an IP address.
nameserver 69.28.32.16 nameserver 69.28.32.180
<snip>
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
Deleting 127.0.0.2 on both machines!
paf.koepsell is a windoze machine. I have changed its' hosts and lmhosts files to reflect the correct addresses.
I have changed the hosts files to reflect the correct ip's for each suse machine also.
My ip's are set by my linksys routers dhcp server. The /etc/hosts does not automatically change to reflect any changes in the ip's from the linksys router.
That's because DHCP is dynamic and /etc/hosts is static.
Should I disable the linksys routers dhcp server and set static addresses??? I have 3 machines, and at most will have 2 more in the future.
As I stated earlier, if you are going to use DHCP ( does not matter what provides it ) do not add or change the /etc/hosts file and use the Linksys router IP address for the first DNS server entry. This can be set in the Linksys router, I know as I use one. Either use a static environment or dynamic on your PC's but not both or you will at some point run into problems and get lost trying to figure out where the problem is. And make sure you assign IP's that are not in the same range as the DHCP addresses in the Linksys router. You can still run the DHCP setup on the Linksys router for any guests that may stop by for a visit. For a small network like yours I suggest you stick with a static setup as it will be much easier to maintain. Use static /etc/hosts and /etc/resolv.conf files I used to work in a mid sized company with over 60 offices and over 1000 PC's and DHCP was much easier to use in that context. If you need any further help post another message to the list. That's what the "old timers" on this list are here for. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998
On Mon, 2005-12-26 at 21:56 -0800, bernd wrote:
From: bernd <suse@koepsell.info> To: SuSE Users Group <suse-linux-e@suse.com> Subject: Re: [SLE] Why isn't my LAN, etc. working??? (SuSE 9.3) Date: Mon, 26 Dec 2005 21:56:29 -0800 (Tue, 00:56 EST) Mailer: KMail/1.8
Please fix your clock settings. You are showing that you are in the pacific timezone (USA) yet you have conflicting times showing, 21:56 and 00:56 which is a three hour difference. I doubt that this is a problem with KMail/1.8. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998
On Tuesday 27 December 2005 05:06, Ken Schneider wrote:
Date: Mon, 26 Dec 2005 21:56:29 -0800 (Tue, 00:56 EST) Mailer: KMail/1.8
Please fix your clock settings. You are showing that you are in the pacific timezone (USA) yet you have conflicting times showing, 21:56 and 00:56 which is a three hour difference. I doubt that this is a problem with KMail/1.8.
I am in Pacific (PST), which shows as correct. The time zone in parenthesis shows Eastern (EST), which IS 3 hours difference. This is not conflicting?!?! I have no settings on my side which are Eastern (EST)?!?! Bernd
On Tuesday 27 December 2005 00:56, bernd wrote: <big, very big snippage>
I hear a collective DUH! coming from the throngs on suse-e regarding the hosts file! Yet...
Hi Bernd, Ken beat me to it (thanks, Ken!) and gave you some great advice, but let me add something: When you're posting configuration files to the list, especially long ones, please trim out all the unnecessary paragraphs/instructions (leading "#" on each line). Just leave the comments that serve as section and parameter identifiers... So, please let us know when you've cleaned up your basic network configuration and if that has fixed your problems, OK? regards, - Carl
Carl Hartung wrote:
So, please let us know when you've cleaned up your basic network configuration and if that has fixed your problems, OK?
And then you to can sing the networking song. "This lan is your lan. This lan is my lan..." ;-)
At 12/27/05 17:03, James Knott wrote:
Carl Hartung wrote:
So, please let us know when you've cleaned up your basic network configuration and if that has fixed your problems, OK?
And then you to can sing the networking song.
"This lan is your lan. This lan is my lan..." ;-)
Thb-b-b-t-t There is no nonsense so errant that it cannot be made the creed of the vast majority by adequate governmental action. --Bertrand Russell
On Tue, 2005-12-27 at 18:03 -0500, James Knott wrote:
Carl Hartung wrote:
So, please let us know when you've cleaned up your basic network configuration and if that has fixed your problems, OK?
And then you to can sing the networking song.
"This lan is your lan. This lan is my lan..." ;-)
"This lan will surely vote for me" :) Mike - just jib-jabbering away
On Tuesday 27 December 2005 08:15, Carl Hartung wrote: <snip>
So, please let us know when you've cleaned up your basic network configuration and if that has fixed your problems, OK?
Disabled DHCP from linksys router and set static addresses for each machine. Can now print from everything on each machine, NFS mounts directories just fine. One problem that I am left with (at present)... I wanted to be able to log on to one machine (#1) as if I were on the other (#2). I set up NFS on #2 to serve the /home directories to #1, mounting them to /home. There are no users on #1, so no conflicts with the directory. I am able to logon without a hitch, using all my documents and settings, and even my desktop as if I were on #2. Some apps won't run because I'm not importing /usr or /opt directories. Problem is: When I try to use the internet from #1 from my NFS mounted /home directory, things come to a near screeching halt. My download and upload speeds are in the double digits, 30-40 kb/s instead of 900+ kb/s. Sometimes the speed picks up, but it's short lived and inconsistent In trying to do a remote login to #2 I just get a black screen with a mouse pointer, and no menus or access to anything. This is why I set up NFS to mount the /home directories the way I did. Thoughts??? Bernd
On Thursday 29 December 2005 21:30, bernd wrote:
Disabled DHCP from linksys router and set static addresses for each machine. Can now print from everything on each machine, NFS mounts directories just fine.
Excellent!
One problem that I am left with (at present)... Problem is: When I try to use the internet from #1 from my NFS mounted /home directory, things come to a near screeching halt....
I'll pass on this question, Bernd... haven't a clue and it's making my head spin just thinking about it! ;-)
In trying to do a remote login to #2 I just get a black screen with a mouse pointer, and no menus or access to anything. This is why I set up NFS to mount the /home directories the way I did.
Thoughts???
If you can otherwise ssh in to #2 normally, then you probably need to enable X11 forwarding. I found a note in my archives stating "set 'X11Forwarding yes' in /etc/ssh/sshd_config" but there may also be a YaST setting somewhere. Note: X11 forwarding is off by default because of the inherent security risks, so please be careful... changing the default port and using really good passwords come to mind. I'm sure others will chime in as necessary to fill in any blanks. regards, - Carl
participants (7)
-
bernd -
Carl Hartung -
Eric Hines -
James Knott -
Ken Schneider -
Mike McMullin -
Paul W. Abrahams