Hi Paul, Thanks for your advice.
- snip - > > What happens if you try pinging 66.218.71.86 (w7.scd.yahoo.com, one of > the servers that listens to www.yahoo.com)? # ping -c 3 66.218.71.86 PING 66.218.71.86 (66.218.71.86): 56 data bytes --- 66.218.71.86 ping statistics --- 3 packets transmitted, 0 packets received, 100% packet loss ifconfig ppp0 ppp0 Link encap:Point-to-Point Protocol inet addr:202.123.68.108 P-t-P:202.123.71.254 Mask:255.255.255.255 UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1492 Metric:1 RX packets:152 errors:0 dropped:0 overruns:0 frame:0 TX packets:73 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:10 RX bytes:10109 (9.8 KiB) TX bytes:1932 (1.8 KiB) > Take a look at /sbin/ifconfig and see if eth0 is listed there, and if > so, what the IP on it is. # ifconfig eth0 Link encap:Ethernet HWaddr 00:50:BF:70:F6:DD inet addr:192.168.2.3 Bcast:192.168.2.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:804 errors:0 dropped:0 overruns:0 frame:0 TX packets:535 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:114717 (112.0 KiB) TX bytes:96191 (93.9 KiB) Interrupt:5 Base address:0xec00 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:3924 Metric:1 RX packets:36068 errors:0 dropped:0 overruns:0 frame:0 TX packets:36068 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:12467899 (11.8 MiB) TX bytes:12467899 (11.8 MiB) ppp0 Link encap:Point-to-Point Protocol inet addr:202.123.68.108 P-t-P:202.123.71.254 Mask:255.255.255.255 UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1492 Metric:1 RX packets:347 errors:0 dropped:0 overruns:0 frame:0 TX packets:158 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:10 RX bytes:24167 (23.6 KiB) TX bytes:3972 (3.8 KiB) sl0 Link encap:Serial Line IP inet addr:192.168.0.1 P-t-P:192.168.0.2 Mask:255.255.255.255 UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1492 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:10 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) > If that looks good, check /etc/resolv.conf and make sure there's a > nameserver or two listed. /etc/resolv.conf could not be edited even as ROOT (the file can be opened and its content can be edited. But saving is impossible) # cat /etc/resolv.conf search domain.com\000 nameserver 192.168.2.1 # ls -l /etc/resolv.conf -rw-r--r-- 1 root root B.R. Stephen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]