I'd add one more step to Szemir's process of working through the network problems.
If you can successfully ping your name servers, then try pinging a web site by name. I routinely use www.google.ca for this type of troubleshooting. i.e. (in a console window, and as root) ping www.google.ca should return some successful pings. If so, then you should be able to browse the web. It is possible the name resolution may fail though. If this is the case, then you need to troubleshoot name resolution on your computer (check default gateway, check how your box is configured to resolve names, etc.) If you cannot ping the name servers at all (by IP address), then you have a lower level problem - likely something to do with the NIC itself (improper drivers, bad NIC, invalid IP configuration, etc.) Troubleshooting hardware or network related problems can sometimes be a real pain. But it's even more of a pain if you don't understand what the diagnostic tools are indicating to you. HTH Shawn -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of bogi Sent: Friday, June 11, 2004 2:18 PM To: CLUG General Subject: Re: [clug-talk] Mandrake 10 Woes a2: Your NIC seems to be on good working order, 8139too is a very widely user module, my box actually uses the same, and i am sure my nic is somewhat different then yours :-) The network settings look ok for me. I will ask you to open a terminal window, and try the following things: become root ifconfig and see the output, if eth0 (say) is on and has the parameters you just described in the gui, then go to the second part. ping 64.59.135.133 ping 64.59.135.135 you may stop ping by pressing ctrl+c after a few good pings. In this case, you would be pinging your dns servers. (try to activate this Alphashield before you start the pinging) secondly try browsing the net, if the ping is ok. _______________________________________________ clug-talk mailing list [EMAIL PROTECTED] http://clug.ca/mailman/listinfo/clug-talk_clug.ca
