Unable to get IP. No DHCP client

[WDAexodus]

Reference this thread:

http://www.sevenforums.com/network-sharing/27738-amazing-network-problem-3.html

Router: D-Link d-524 V4000
Ethernet: Nforce via mobo Gigabyte GM-A570SLIv2

I am having similar problems as with the linked thread. What happened with me was I needed to download drivers for my 2nd pc because the wireless had issues. So I unplugged my Cat-5 cable from my main pc that was working and then plugged it into my 2nd pc. I downlaoded the drivers and then reconnected the cable back into the main pc. That's when the problems began. My 2nd pc is the exact same setup as my main other than the processor is different and it works great. Things I have done:

1. Connected straight to DSL modem.
2. Reset both modem/router
3. IPconfig shows the 169 IP.
4. Pinged the NIC with no loss of packets.
5. Reloaded the drivers via mobo CD(Vista x64)
6. Started in safe mode w/networking
7. Restarted DHCP Client
8. Verified configuration matched the other pc.
9. Reinstalled Iv4 using c:/windows/inf
10. Bought a PCI adapter in case the mobo connection was bad. Didn't work either.

I can't even access the router or modem on the main pc. I tried a static IP but will try what was suggested in the linked thread when I get home today. If you need snipits I can do that once I get home. I'll provide anything you need. Most of the snipits in the link thread have the same info as mine would that's why I linked it. Thanks in advance for the help.

 

[Gazzasore]

Something you can do is download Tweak 7
& it has a button on iy to reset your internet settings and Nic back to default

This is about the only thing that works on Tweak 7 without registering it

Download it here Totalidea Software :: Home :: Tweak Windows 7 - Tweak Windows Vista - Tweak-7 - Tweak7 - TweakVI - Tweak-Vista - TweakVista - TweakXP - Tweak-XP - Tweak XP - TweakUI - Outlook Backup - Outlook Notes - FireTune

 

[WDAexodus]

Where do you go in Tweak-7 to reset your network settings to default

 

[Snufffed]

There is a simply way to reset the adapter. open the network and sharing
locate the adapter disable. wait about 1 min then enable it.
next
open cmd (run as admin) type
ipconfig /renew

wait till the popup shows. then you should see your internet come to life.

what you have done is
1. insured the adapter is working properly disabled and enabled
2. ipconfig /renew is totally reset the modem to get a new IP address for you.

Next if the above does not work.... shutdown the computer.
unplug your modem... wait 3 min... 3 min not 2min not 2.5min. 3 min to allow the modem-router to totally reset - when you plug it bak in it will then ask for and rec a new IP for you .... takes about 1 min....
Now restart your computer. total time about 4 min plus what ever your boot time is.

 

[WDAexodus]

Yeah, I did that as administrator. It gave me an error message saying that it couldn't connect to the DHCP server. Disregard what is says about the secondary connection. It's not being used (It has the same problem)

 

[Barman58]

One thing that may seem stupid but as the action that started your problems was removing the cable have you checked the integrity of the cable?

I have experience this myself - a slight damage to a pin when re-inserting and bang - no connection

 

[WDAexodus]

Yep, I am using the said cable for this connection. I've tried multiple cables with the same results. I also just formatted the drive and reloaded RC1 and it still doesn't work.

 

[WDAexodus]

.... shutdown the computer.
unplug your modem... wait 3 min... 3 min not 2min not 2.5min. 3 min to allow the modem-router to totally reset - when you plug it bak in it will then ask for and rec a new IP for you .... takes about 1 min....
Now restart your computer. total time about 4 min plus what ever your boot time is.

I did that also. No go.

 

[Snufffed]

can you ping the router?
have your set the router to allow more than one connection. via ip address?

 

[WDAexodus]

Nope I couldn't ping it. I reloaded XP on my pc in a dual boot config and I am also having the problem in XP. I believe somehow the mobo may be screwed. I did flash my bios about three weeks ago but ethernet worked perfectly up intill I unplugged the cable last week. I don't get how both my onboard adapter and the new PCI adapter both don't work. I did plug in my wireless(USB) and XP runs with it. Unfortunatley Windows 7 BSOD's when the wireless is connected to a network. I guess the drivers suck. I am going to revert back to the original bios and see if that works. I doubt it will but what's to lose. My pre-order will be delivered next week and I won't be able to take advantage of it. The only up side is I will be able to get free tech support instead of the 59.00 per day crap the MS is charging for XP.

 

[ultraplanet]

I have seen this before on DSL modems from Verizon. The modem gets stuck on a single mac address. There should be a reset button you have to push with a pencil somewhere on the modem.

 

[WDAexodus]

I reset the modem already. Had to restore all the settings to get the internet back.

 

[ultraplanet]

So you are back up and running?

 

[WDAexodus]

Well, no not on the ethernet. I plugged in my USB wireless from the other pc. It works but the ethernet is still down hard. I'm running on XP because 7 won't recognize the drivers for the wireless. What a wonderful pickle I am in.

 

[ultraplanet]

Is your wireless and wired router and modem all together in 1 unit?

 

[WDAexodus]

No. They are all separate. I have a Westell 6100 modem, D-Link DI-524 router, and a Belkin F5D5070 wireless adapter.

 

[alexku85]

Try this:

Check if the DHCP services is running at service.msc and rollback your network interface driver.

 

[WDAexodus]

I did that numerous times. No luck. Listen, and see if my logic is right. If my USB wireless is working doesn't that eliminate W7 from being the problem and it isolating it to a motherboard/BIOS issue?

 

[WDAexodus]

My problem is fixed. The BIOS version FhH was bugged. I updated to the FhK version and now my onboard works like a charm. Figured it was BIOS.