Another computer not connecting to the net
Heya...
I've been working on a computer for a friend of mine who's had it to a number of different people including the local ISP because it will not connect to the internet.
My approach has been to wipe the system clean, completely wipe the harddrive and do a fresh install of winXP while disconnected phsyically from teh net. Upon startup, it detects the ethernet card, the settings look good, but no dice once I plug it back in. Will not connect.
To be sure, I've gone through and disabled the onboard ethernet card, switched out the pci card for a brand new one, and even removed the firewire card for her ipod in case of conflict.
I've basically got two conclusions: Either the service I'm testing it on is not allowing the connection (I'll confirm that today by plugging it into my home network) or some element of her mother board is preventing the communication. Has anyone ever heard of such a thing? This one has me stumped.
I've run and re-run the network detect and networking setup many times. No errors on that part at all. The card, when status is checked, shows either an IP of 0.0.0.0 or an automatic address in the 169.*.*.* range.
Ideas?
Brian911 posted this at 20:36 — 2nd August 2004.
He has: 14 posts
Joined: Aug 2004
if your IP is in the 169.* range it shows a problem with your DNS server... it means your computer cannot get a suitable IP address.
Are you connecting directly or is there a router in between?
Also try replacing the cable
Web Hosting Directory
mairving posted this at 21:58 — 2nd August 2004.
They have: 2,256 posts
Joined: Feb 2001
Actually has nothing to do with DNS. It means that it can't find a DHCP server. IP addresses in the 169. range are called APIPA addresses, which means that IP is auto-assigned when it can't find a DHCP server.
Standard troubleshooting techniques should root out the problem. In other words eliminate what it could be one by one until you get your answer. I have occasionally seen some NIC's behave very troublesome. It seems that removing the card and sticking it back in fixed those.
Mark Irving
I have a mind like a steel trap; it is rusty and illegal in 47 states
Brian911 posted this at 11:42 — 3rd August 2004.
He has: 14 posts
Joined: Aug 2004
I did indeed write DNS server instead of DHCP... been late yesterday
sorry about that
Web Hosting Directory
compwolf posted this at 07:00 — 3rd August 2004.
He has: 72 posts
Joined: Nov 2003
I fully agree about the trouble shooting. Also though there are too many questions left unanswered, such as what is the network configuration (Router to a Broadband, direct connect to modem, etc.) The first thing that comes to mind is whether the drivers are correct for the card. Also is the configuration correct for the setup. In other words check your TCPIP configuration, including your gateway (if needed) as well as the IP address for the DNS server (again if needed).
If all of the above checks out then start in on the easiest of the hardware, such as network cables and resetting other devices (Router, Modem, etc.) Another question is whether the actual connection is working. Testing it with another PC is a good plan.
Want to join the discussion? Create an account or log in if you already have one. Joining is fast, free and painless! We’ll even whisk you back here when you’ve finished.