Let's be a little systematic. Roughly, you need to test from lowest to highest level. If something is broken at some level, don' t mess with higher levels until you get the first problem resolved.
Lowest: hardware. Card is seated, cable is good, cable is plugged in securely at both ends. (Have you swapped cables yet?) Most Ethernet ports have colored LEDs in the Ethernet jack at each end, and they should be lit. Usually green, but maybe another color. Electrical connectivity between the CPU and the NIC. Run "lspci | grep Ether". Verify you see each installed device. Drivers. This was working when you showed that ifconfig sees eth0. If you have two cards installed, then "ifconfig -a" should show both. If it's not working, try to revert to where you were when it worked. IP configuration. Run ifconfig, verify you have an IP address. (You didn't in the screen shot you showed.) If you're using DHCP, then you need a working DHCP server. I'm not a Comcast customer, but it sounds like the DHCP server should be outside your premises. Either look in syslog (/var/log/message or /var/log/daemon.log) for DHCP activity. You should see DHCP DISCOVER followed by DHCP OFFER. If you don't see DISCOVER, your box isn't configured to use DHCP. If you don't see OFFER, either the DHCP server can't hear your box, your box can't hear the server, or the server is refusing to serve you. The first two problems indicate that your hardware connectivity is bad -- revert to first level. The last problem indicates that Comcast sucks. I'm not a Comcast customer, so I don't know what their rules are nor how they enforce them. If you have an IP address, then the next thing to check is routing. Run "ip route". You should have a local route and a default route. Here's mine. Yours will be similar with different numbers. ~> ip route 192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.4 default via 192.168.0.1 dev eth0 metric 100 If you have a default route, verify that you can ping your default gateway. Your default gateway is on the default line (192.168.0.1 for me). Now, see if you can route packets past your default gateway. Use mtr or traceroute. Run "mtr 1.2.3.4" (or any fictitious public address that's past the gateway) or "traceroute 1.2.3.4". You should see replies from a bunch of routers in your ISP and maybe beyond. If all that works, it's time to test DNS. Look in /etc/resolv.conf. It should list some DNS servers. Use mtr or traceroute to see if you can reach each of them. If so, see if you can resolve a hostname. Run "gethostip www.google.com". At this point, you should be home free. So give it a try and let us know about THE FIRST thing in the list above that doesn't work. On Thu, Nov 19, 2009 at 4:12 PM, marbux <[email protected]> wrote: > Hi, folks, > > Can't seem to work this through with the aid of Google. I'm down to > seeking help. > > I recently acquired a second, used AMD 64-bit box with an ASUS > motherboard. It came with WinXP Pro and didn't get an internet > connection to Comcast. Acting on a suspicion that the onboard ethernet > connection was dead, I ordered a Gigabit ethernet card. While awaiting > its delivery, I wiped the hard drives and installed Ubuntu 9.10 > 64-bit. Received and installed the ethernet card. No joy. > > A few things I've tried without success, in no particular order: > > -- Selecting eth0 as the connection type in Network Tools. > -- Selecting "connect automatically" under Network Connections eth0 > properties. > -- Pulling the card and seeing if I could revive the onboard ethernet > connection. > -- Rotating cards in the machine in hopes of resolving an imaginable > IRQ conflict > -- Installing Ubuntu 32-bit as a virtual machine on my old box so I > could compare configuration details. > -- Confirmed that the right driver for the card is installed and active. > -- Installed Puppy 4.3.1 on both machines and compared configuration > details (my experience is that Puppy does better at auto-configuring > for hardware than Ubuntu). > -- etc. > > All of which has got me nowhere over several days. > > This is new turf for me because ethernet connections have always just > worked for me. So I'm unsure what information folks will need to > assist me. > > Appreciate some hand-holding here. > > Best regards, > > Paul > > > > > > > -- > Universal Interoperability Council > <http:www.universal-interop-council.org> > _______________________________________________ > EUGLUG mailing list > [email protected] > http://www.euglug.org/mailman/listinfo/euglug > -- Bob Miller K<bob> [email protected] _______________________________________________ EUGLUG mailing list [email protected] http://www.euglug.org/mailman/listinfo/euglug
