You need to check the NetVista's DNS setting. Make sure that THOSE IPs are accessable (pingable) from the NetVista. Chances are they are not. Also, check that your default gateway is set too (/sbin/route -n). Khanh Tran Network Operations Sarah Lawrence College -----Original Message----- From: elefino [mailto:kevinmcl@magma.ca] Sent: Friday, December 31, 2004 1:38 PM To: suse-linux-e@suse.com Subject: [SLE] Ping, but no web Here's my setup, with one PC able to browse, and one not. Two PCs with SuSE 9.2 connect to the LAN side of a D-Link DI-704 residential router. The router provides DHCP and basic port-closer firewall, and connects (WAN side) via ADSL to my ISP. (Router takes care of PPPoE with ISP.) One PC (this one, from which I'm writing) has been successfully connecting to the internet for years using exactly this setup (D-Link and ADSL modem). The other PC is an old IBM NetVista (Pentium 3) that we just acquired. I loaded 9.2 onto it yesterday, so probably overlooked something in setup.
From the NetVista, I can ping this computer (by IP only, I don't have a DNS server), I can ping the router, and I can browse (Konqi) the router's internal (admin) web pages. I can also ping the NetVista from this PC. LAN addresses are the default 192.168... range. But I cannot see the internet and cannot reach even my ISP's home page (host not found) from the NetVista.
The router has the basic port-blocking firewall with just about everything closed. I have switched off the SuSE firewall in the NetVista until I'm able to browse. No effect. I don't do this very often. What obvious next step am I overlooking? What setup is missing for the NetVista to look past the router to browse the web (and to perform YOU updates...)?? Any help appreciated -- the wife is tapping her foot impatiently. . . :-) Kevin -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
On Friday 31 December 2004 13:48, Khanh Tran wrote:
You need to check the NetVista's DNS setting. Make sure that THOSE IPs are accessable (pingable) from the NetVista. Chances are they are not. Also, check that your default gateway is set too (/sbin/route -n).
Ok, thanks. That was the kick I needed. I had already set to what I thought was a match for the setting on the "working" computer. In YaST, under "Network Services" > "DNS and Host Name", the dialog has space to input the DNS server IPs, but that dialog also has a checkbox to select "Update nameservers and search list via dhcp". When that box is checked, the system is supposed to look to the dhcp server and ignore whatever is in the DNS server IP fields. At least, that's what I interpreted, and so I left those fields blank and just checked the checkbox. However, on my "working" PC (this one) I must have, at some time in the past, filled in the explicit addresses for my ISP's primary and secondary DNS servers. Then I had gone back to "Update..... via dhcp", which grayed out the explicit addresses. When I went back to the NetVista (which had blank fields, but which had "Update . . . via dhcp" checked), typed in explicit DNS server IPs and then re-selected "Update . . . via dhcp", it started working. According to me, this should not have any effect, but it seems that it did. We'll file this under "yet another thing that I just don't get", because it seems to be working. Thank you. Kevin
Replying to myself. . . On Friday 31 December 2004 14:58, elefino wrote: [...]
However, on my "working" PC (this one) I must have, at some time in the past, filled in the explicit addresses for my ISP's primary and secondary DNS servers. Then I had gone back to "Update..... via dhcp", which grayed out the explicit addresses.
When I went back to the NetVista (which had blank fields, but which had "Update . . . via dhcp" checked), typed in explicit DNS server IPs and then re-selected "Update . . . via dhcp", it started working. According to me, this should not have any effect, but it seems that it did. We'll file this under "yet another thing that I just don't get", because it seems to be working.
Well, now that I think about this a little more, it seems unlikely that it is any kind of Linux-related glitch, especially since it occurs on two very different PCs on my little network. So, the common element (other than my foggy brain and fumbly fingers) is the D-Link. It's at least six years old. Maybe its built-in DHCP server is going wonky. There were a few close-by lightning strikes this summer. Next time I'm at the computer store, I'll get something newer, just to try. Kevin
participants (2)
-
elefino -
Khanh Tran