Not Receiving an IP Address

[Mike2002]

I was away from my computer for a few weeks and came back to find that it didn't have an internet connection. The computer is behind a router and i've confirmed that the router works perfectly and the cables are fine. The IP address that I am getting from the router is 169.xxx.xxx.xxx so I know that is wrong. I tried to repair the connection and that failed. I also went into the command prompt and tried to release and renew the IP address but it tells me that is can't do it because of something with the DNS server. So I have no idea what else to do now.

PS...I did a system restore and that didn't seem to fix anything.

 

[tweekah]

Did you powercycle the router? Disable any software firewalls?

try ipconfig /release and post the exact error here.

 

[Mike2002]

I've restarted the router a few times and there are no software firewalls installed. The computer will get rid of the IP address fine but it just won't renew it. Ipconfig /renew gives the error" An error occurred whiel renewing interface Local Area COnnection 3: unable to contact your DHCP server. Request has timed out."

 

[tweekah]

Make sure someone didn't swap the ISP connection into the LAN and placed your system in the WAN/Internet port. Or a kinked cable...must check physical layer before you move foward. Also a static ip configuration within your range may help you isolate the router's DHCP ability.

Would anyone have touched this environment or was it untouched the whole time?

 

[Mike2002]

I have the cable to my desktop run into the room with a long ethernet cable and i can plug my laptop into that cable and the laptop goes online perfectly but when i plug the desktop in with that same cable, i get these problems, so I'm assured that the cables and ports on the router work fine.

 

[Fullmetal Chocobo]

Turn the computer off, unplug the PSU, and turn the PSU off via the switch on the outside of the PSU. Then turn the switch back on, plug the power cable back in, and turn on the computer again, and see how that works.

 

[Mike2002]

Fullmetal Chocobo------>Wow that fixed the problem. Anyone know why that would fix it or what was wrong?

 

[Fullmetal Chocobo]

Originally posted by: Mike2002
Fullmetal Chocobo------>Wow that fixed the problem. Anyone know why that would fix it or what was wrong?

You happen to have an 680i or Nforce motherboard using the onboard NIC? Same thing happened to me--pissed me off like someone pissed in my cereal. Did a lot of research, and that ended up being it. I've only had to do it once, and it was while I was setting up the new computer.

EDIT: Apparenly it's an issue with the onboard NICs on the Nforce boards.

 

[Chapbass]

i would go to say its somewhat of a problem with ALL onboard nics....as its happened on my p4p800 a few times, and i never could figure out what was up with it.


now that you mention killing all power to the computer....that makes a lot of sense...since even when the power is off that network cable is still communicating (hence the ability to "wake up on lan")



learn somethin new every day here at AT