AT WITS END: Cannot get online through LAN

Extas

Junior Member
May 10, 2005
1
0
0
Here's my scenario, I'm looking for any help that anyone could provide.

About once a year, I reinstall Windows for performance reasons. This past weekend was the one that I used. I made backup DVDs of everything that I would like to keep, and formatted C:/.

I did a fresh install of Windows XP Professional SP1 and then I started having problems. For the sake of reference, I have an Asus SK8V motherboard with an Athlon FX53 processor. After installing drivers for the devices that did not have any, I attempted to get online. I use the 3Com Gigabit (3c940) to get online up until the reinstall.

When I opened Internet Explorer, I got the DNS error page. I thought this was odd, since I was online not a few hours earlier. I decided to uninstall the onboard LAN and reinstall it just to make sure. I transferred the latest drivers from the Asus Web site onto my PC from a garbage laptop that I have (and am currently using). Unfortunately, I could still not get online.

I've now spent two evenings trying to get online with my PC. Here's a summary of the things I have tried.

  • Fresh Install of Windows XP SP1
  • Uninstall/Reinstall onboard LAN
  • Installed a Linksys NIC card I had (with drivers)
  • More reformats & reinstalls of Windows XP SP1
  • Removing ALL PCI cards (in hopes of clearing any conflicts), reinstalling Windows and using onboard LAN
  • Attempted another LAN card I had, don't remember the brand
  • Tried moving LAN card to another PCI slot
  • Changing from DHCP to an assigned IP, subnet, dns, etc - and back again, several times

To be more specific about the problems I am having, the Local Connection comes up with an IP of 0.0.0.0 when I initially boot up. After about 30 seconds, the IP changes to an "Automatically assigned address" of 168.something or other, which shouldn't be my IP (just a default?). I've tried the ipconfig /release and ipconfig /renew combo, but I get an error of "Unable to assign IP address."

Another thing that I have tried is instead of using a NIC card or the onboard LAN, I used my cable modem's (Motorola SB5100) USB drivers and connected to the computer via USB. I get the same damn errors!! IP of 0.0.0.0 which becomes 168.... after like 30 seconds.

There has been another issue that has just come up since this reinstall. I cannot get my Soundblaster Audigy ZS2 to work. Not only that, I cannot even get the onboard AC97 chip to work.

These problems are leading me to believe that my problems are not tied to the DHCP issue, but I am not sure. I've never had so much trouble with a computer in my lifetime, normally I can figure it out after some trial & error or some Google'ing. My only thought is perhaps my motherboard went bad somehow? That's all I can come up with that would tie all these problems in together. Unfortunately it is hard to find a socket 940 motherboard nowadays that is priced reasonably.

Does anyone have any thoughts as to what else I could try, or what may be the issue?

Thank you for taking the time to read this.
 

ktwebb

Platinum Member
Nov 20, 1999
2,488
1
0
This is a hardware issue. As such it's in the wrong forum. What does device manager say about your NIC's? SOundcard too while we're at it?
 

nweaver

Diamond Member
Jan 21, 2001
6,813
1
0
this is why I keep an old hub....connect PC->hub->Modem, and also plug the laptop (with static IP) into the hub and fire up ethereal. You should see the DHCP discovoery packets, and then DHCP requests/responses. How do you get your IP? (i.e. is there a router between your modem and you computer, service private ip. Do you get IP from provider (live IP), etc. We need more about your setup to the internet, cable, dsl, dialup?)
 

PlatinumGold

Lifer
Aug 11, 2000
23,168
0
71
basically your ip address says you are not getting connectivity to your DHCP.

are you going directly to your modem? or are you using a router?

if you are going directly to you modem, who is your carrier? dsl? cable?

do you have a login procedure with you broadband company?

 

bwnv

Senior member
Feb 3, 2004
419
0
0
The 168 network is XP's default. It will give that if you haven't assigned an address, or if using DHCP it's not getting one from your server. Try resetting whatever you are getting your DHCP from.
Good luck