[opensuse] Home network problem
I have a problem with suse 8.2 and my home network. There is a windoze XP machine on the network that is not experiencing any problems reaching the internet. The suse box can ping the router and open the administration of the network through the default gateway of the router. Any attempt to reach the internet results is www..... can not be found. /etc/resolv.conf changes dynamically and shows the ISP in the search line and their 2 nameservers, also. Still not joy. Any ideas? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Monday 04 December 2006 20:04, eharrison@tampabay.rr.com wrote:
I have a problem with suse 8.2 and my home network. There is a windoze XP machine on the network that is not experiencing any problems reaching the internet.
The suse box can ping the router and open the administration of the network through the default gateway of the router. Any attempt to reach the internet results is www..... can not be found. /etc/resolv.conf changes dynamically and shows the ISP in the search line and their 2 nameservers, also. Still not joy.
Any ideas?
Can you ping outside the router? Like, ping 207.69.188.186 (an Earthlink nameserver), or ping google.com? Mark -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Monday 04 December 2006 19:04, eharrison@tampabay.rr.com wrote:
The suse box can ping the router and open the administration of the network through the default gateway of the router. Any attempt to reach the internet results is www..... can not be found. /etc/resolv.conf changes dynamically and shows the ISP in the search line and their 2 nameservers, also. Still not joy. Can you ping an outside address:
ping 209.97.46.5 This is the address for www.usatoday.com. If you can ping the outside address, but can not ping www.usatoday.com, then there is something wrong with your name resolution... and probably /etc/resolv.conf is the problem. Has this setup ever worked in the past? What has changed? Do you have a firewall running on your router? -- Kind regards, M Harris <>< -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
----- Original Message -----
From: M Harris
The suse box can ping the router and open the administration of the network through the default gateway of the router. Any attempt to reach the internet results is www..... can not be found. /etc/resolv.conf changes dynamically and shows the ISP in the search line and
On Monday 04 December 2006 19:04, eharrison@tampabay.rr.com wrote: their 2
nameservers, also. Still not joy. Can you ping an outside address:
ping 209.97.46.5
This is the address for www.usatoday.com.
If you can ping the outside address, but can not ping www.usatoday.com, then there is something wrong with your name resolution... and probably /etc/resolv.conf is the problem.
Has this setup ever worked in the past? What has changed? Do you have a firewall running on your router?
I am in DC for a few days and I can not remember if I tried to ping an IP address or not. I know I had no luck with URLs, but the resolv.conf file looked as it alwasys has. It worked well except just after the hurricanes shut the electricity down for a few days, but was working fine until yesterday. We tried a new router with a different default gateway IP address. We went back to the old router. I believe both had the firewall enabled, but that had not been a problem in the past. The SuSE Firewall is off. I will check it out on Thursday and repost. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Mon, 2006-12-04 at 20:10 -0600, M Harris wrote:
On Monday 04 December 2006 19:04, eharrison@tampabay.rr.com wrote:
The suse box can ping the router and open the administration of the network through the default gateway of the router. Any attempt to reach the internet results is www..... can not be found. /etc/resolv.conf changes dynamically and shows the ISP in the search line and their 2 nameservers, also. Still not joy. Can you ping an outside address:
ping 209.97.46.5
This is the address for www.usatoday.com.
If you can ping the outside address, but can not ping www.usatoday.com, then there is something wrong with your name resolution... and probably /etc/resolv.conf is the problem.
That file should point to the router, the router should get the dynamic name server information from the ISP. I have a similar intermittent problem with my SMC4008ABR. Other than forcing the name server information into the Config file (via YaST) I have found that dis-connecting the DSL connection, and then reconnecting, using it's administration software, to be a cure. {snip} -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tue, 2006-12-05 at 05:55 -0500, Mike McMullin wrote:
On Mon, 2006-12-04 at 20:10 -0600, M Harris wrote:
On Monday 04 December 2006 19:04, eharrison@tampabay.rr.com wrote:
The suse box can ping the router and open the administration of the network through the default gateway of the router. Any attempt to reach the internet results is www..... can not be found. /etc/resolv.conf changes dynamically and shows the ISP in the search line and their 2 nameservers, also. Still not joy. Can you ping an outside address:
ping 209.97.46.5
This is the address for www.usatoday.com.
If you can ping the outside address, but can not ping www.usatoday.com, then there is something wrong with your name resolution... and probably /etc/resolv.conf is the problem.
That file should point to the router, the router should get the dynamic name server information from the ISP. I have a similar intermittent problem with my SMC4008ABR. Other than forcing the name server information into the Config file (via YaST) I have found that dis-connecting the DSL connection, and then reconnecting, using it's administration software, to be a cure.
{snip}
Just a followup on a couple of thins I read after posting this. Your Linux system worked find until recently, and recently there was a major storm in your area. Is it possible that your NIC is fried and you are getting intermittent connections with it? When I get the network is unreachable problem, I usually open YaST delete the network card information, and then re-install the network card. YaST picks up the info and I get a network connect again. IT's not pretty but could be informative. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
--- 209.97.46.5 ping statistics --- 120 packets transmitted, 120 received, 0% packet loss, time 119019ms --- www.usatoday.com ping statistics --- 7 packets transmitted, 7 received, 0% packet loss, time 6007ms rtt min/avg/max/mdev = 165.125/165.926/166.666/0.629 ms lxuser@ranzor:~> Is this good enough? zoran On Tuesday 05 December 2006 12:06, Mike McMullin Schreef:
On Tue, 2006-12-05 at 05:55 -0500, Mike McMullin wrote:
On Mon, 2006-12-04 at 20:10 -0600, M Harris wrote:
On Monday 04 December 2006 19:04, eharrison@tampabay.rr.com wrote:
The suse box can ping the router and open the administration of the network through the default gateway of the router. Any attempt to reach the internet results is www..... can not be found. /etc/resolv.conf changes dynamically and shows the ISP in the search line and their 2 nameservers, also. Still not joy.
Can you ping an outside address:
ping 209.97.46.5
This is the address for www.usatoday.com.
If you can ping the outside address, but can not ping www.usatoday.com, then there is something wrong with your name resolution... and probably /etc/resolv.conf is the problem.
That file should point to the router, the router should get the dynamic name server information from the ISP. I have a similar intermittent problem with my SMC4008ABR. Other than forcing the name server information into the Config file (via YaST) I have found that dis-connecting the DSL connection, and then reconnecting, using it's administration software, to be a cure.
{snip}
Just a followup on a couple of thins I read after posting this. Your Linux system worked find until recently, and recently there was a major storm in your area. Is it possible that your NIC is fried and you are getting intermittent connections with it? When I get the network is unreachable problem, I usually open YaST delete the network card information, and then re-install the network card. YaST picks up the info and I get a network connect again. IT's not pretty but could be informative. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tue, 2006-12-05 at 12:43 +0100, zoran korac wrote:
--- 209.97.46.5 ping statistics --- 120 packets transmitted, 120 received, 0% packet loss, time 119019ms
--- www.usatoday.com ping statistics --- 7 packets transmitted, 7 received, 0% packet loss, time 6007ms rtt min/avg/max/mdev = 165.125/165.926/166.666/0.629 ms lxuser@ranzor:~>
Is this good enough?
zoran
I cannot complain seeing as my ping resulted in: ping 209.97.46.5 PING 209.97.46.5 (209.97.46.5) 56(84) bytes of data. 64 bytes from 209.97.46.5: icmp_seq=1 ttl=240 time=163 ms 64 bytes from 209.97.46.5: icmp_seq=2 ttl=240 time=157 ms 64 bytes from 209.97.46.5: icmp_seq=3 ttl=240 time=161 ms 64 bytes from 209.97.46.5: icmp_seq=4 ttl=240 time=164 ms --- 209.97.46.5 ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 3014ms rtt min/avg/max/mdev = 157.061/161.535/164.755/2.920 ms But this does not answer DNS resolution, did you use ping someplace.onnet or the 4d address (i.e. 209.97.46.5)?
On Tuesday 05 December 2006 12:06, Mike McMullin Schreef:
On Tue, 2006-12-05 at 05:55 -0500, Mike McMullin wrote:
On Mon, 2006-12-04 at 20:10 -0600, M Harris wrote:
On Monday 04 December 2006 19:04, eharrison@tampabay.rr.com wrote:
The suse box can ping the router and open the administration of the network through the default gateway of the router. Any attempt to reach the internet results is www..... can not be found. /etc/resolv.conf changes dynamically and shows the ISP in the search line and their 2 nameservers, also. Still not joy.
Can you ping an outside address:
ping 209.97.46.5
This is the address for www.usatoday.com.
If you can ping the outside address, but can not ping www.usatoday.com, then there is something wrong with your name resolution... and probably /etc/resolv.conf is the problem.
That file should point to the router, the router should get the dynamic name server information from the ISP. I have a similar intermittent problem with my SMC4008ABR. Other than forcing the name server information into the Config file (via YaST) I have found that dis-connecting the DSL connection, and then reconnecting, using it's administration software, to be a cure.
{snip}
Just a followup on a couple of thins I read after posting this. Your Linux system worked find until recently, and recently there was a major storm in your area. Is it possible that your NIC is fried and you are getting intermittent connections with it? When I get the network is unreachable problem, I usually open YaST delete the network card information, and then re-install the network card. YaST picks up the info and I get a network connect again. IT's not pretty but could be informative.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Monday, December 04, 2006 @ 7:05 PM, eharrison wrote:
I have a problem with suse 8.2 and my home network. There is a windoze XP machine on the network that is not experiencing any problems reaching the internet.
The suse box can ping the router and open the administration of the network through the default gateway of the router. Any attempt to reach the internet results is www..... can not be found. /etc/resolv.conf changes dynamically and shows the ISP in the search line and their 2 nameservers, also. Still not joy.
Any ideas?
If you are using a router, I believe the router address should show as your nameserver, not the actual nameservers of the ISP. Greg Wallace -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 2006/12/06 22:03 (GMT-0600) Greg Wallace apparently typed:
If you are using a router, I believe the router address should show as your nameserver, not the actual nameservers of the ISP.
I have my router's DNS service disabled, and set my ISP server IPs plus one other in resolv.conf. -- "Let your conversation be always full of grace." Colossians 4:6 NIV Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://mrmazda.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wed, 2006-12-06 at 23:12 -0500, Felix Miata wrote:
On 2006/12/06 22:03 (GMT-0600) Greg Wallace apparently typed:
If you are using a router, I believe the router address should show as your nameserver, not the actual nameservers of the ISP.
I have my router's DNS service disabled, and set my ISP server IPs plus one other in resolv.conf.
I did that too for a while Felix. I was on the phone to their tech support and they informed me that they wanted all client routers to dynamically look to their DNS servers as they change the addresses on them periodically. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 2006/12/07 06:18 (GMT-0500) Mike McMullin apparently typed:
On Wed, 2006-12-06 at 23:12 -0500, Felix Miata wrote:
On 2006/12/06 22:03 (GMT-0600) Greg Wallace apparently typed:
If you are using a router, I believe the router address should show as your nameserver, not the actual nameservers of the ISP.
I have my router's DNS service disabled, and set my ISP server IPs plus one other in resolv.conf.
I did that too for a while Felix. I was on the phone to their tech support and they informed me that they wanted all client routers to dynamically look to their DNS servers as they change the addresses on them periodically.
Nothing in the rules says you need depend on your ISP's DNS servers. Setting manually means when theirs go down you aren't stuck with nothing. -- "Let your conversation be always full of grace." Colossians 4:6 NIV Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://mrmazda.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (7)
-
eharrison＠tampabay.rr.com -
Felix Miata -
Greg Wallace -
M Harris -
Mike McMullin -
phantom21＠mindspring.com -
zoran korac