Another "Cannot contact DHCP server -Windows XP"

Similar problems on XP laptop

Newt, I have a problem similar to Kiran's, but different than almost every other reference to these symptoms I have seen.

I get BOTH the IP symptoms you refer to -- if the computer has been shut down, the LAN connection defaults to 'Invalid IP Address' and 0.0.0.0 address/netmask. If I use 'ipconfig /release/renew' or the right-click 'Repair' command, it complains it can't renew the IP or 'flush the ARP cahe', and it goes to the Automatic Private 169.x.x.x address. After that, ipconfig complains it can't find the DHCP server. This problem is the same whether I'm using the Ethernet cable, or a new Linksys 'G' wireless card.

This is while trying to connect to my new DSL modem/router, which my Win98 PC and old Power Macintosh have had no trouble connecting to. I have been through a dozen tech support calls to Verizon, Dell and Microsoft, and the best they can offer is that my NIC is bad and needs replacing. That wouldn't be so bad if that didn't inolve replacing the motherboard out of warranty. For almost the same price I could buy my wife a new laptop.

My problem is so similar to the Winsock corruption and other problems I have seen posted that I haven't given up on a software solution yet. The hardware doesn't seem to be malfunctioning -- problems are consistent and persistent, yet no harware diagnostic can find a problem. I have lights on both the modem/router and the Ethernet port, so connectivity is there. The DSL modem's maintenance pages even report that there are packets moving on the line.

I have tried pretty much every solution I could find for this, and some have been promising, but none have fixed it. If enough people (besides phone tech support guys) tell me that my NIC is bad, I'll have to get over my denial. I am pretty technical, but I am not an IT pro. So I'm looking for some consultation. From anyone!

Thanks!

JohnM

 

Hi JohnM and welcome. I split your post into a new thread since we do better with tech issues if each thread is for a single problem system. Otherwise things can get confusing.

If you have the same issue with both wired and wireless NICs then I'd say the tech support folks are wrong about the cause.

Three fairly easy things to try that may get you running again - and if the first works, you don't need to do the second or third.

Download and run LSPFix. Some spyware and some spyware removal can damage your winsock stack and prevent connection when all else is fine.

From start => run key in

Code:

sfc /scannow

and click OK. The system file checker will spot any damaged or missing system files and replace them with a good version. It runs silently in most cases and usually pretty fast so you may think it did nothing. A check of your event logs (start => run => eventvwr.msc and OK will allow you to look for the information event that gives details.

start => run => cmd and OK to open a cmd window then

Code:

netsh int ip reset resetlog.txt

Note that this one will put your network pieces back to the defaults so you'll need to set things up again. If you aren't sure of the correct settings, write them down before you do the reset.

 

Thanks, Newt, for your kind attention.

I tried all the steps you outlined. Here are the results. Not surprisingly to me, they made no apparent difference.

I already had LSPFix, but ran it again, with similar results as previously. It doesn't seem to find any missing or damaged files, so nothing gets moved to the right-hand column. I didn't try the "I know what I'm doing" checkbox, because I don't, really. I hit Finish and LSPFix reports zero files changed. I assume I did that right?

So, I went and ran the SFC command, which was new to me. I almost balked when it demanded the XP Pro CD --I run XP Home-- but the Home CD satisfied it. It actually took quite a while, but the Event Viewer reported that it did something to TCP/IP. I think.

So I went to run netsh, which I have tried previously. It didn't seem to make much difference. The Address Type of the LAN connection is now set to 'assigned by DHCP', which I don't believe I've seen before, so maybe that's one step in the right direction. But the IP is still the Automatic Private 169.x.x.x address.

Then I realized I should restart, so I did a full shutdown and powered back up. After that, the LAN connection is back to Address Type: Automatic Private Address. Doing 'Repair' comes back with 'renewing the IP address failed'. Which has been my problem from the start.

I hope my step-by-step will shed some light, at least on what the problem is NOT. And I thank you again for your attention!

JohnM

 

I have had one or two that really stumped me after removing some spyware and LSP Fix found nothing.

Winsockfix.exe took care of the problem.

 

What does lspfix fix that winsockfix does not fix? (peter pipper pizza...) Anyways, it sounds to me that if the TCP/IP protocol is corrupted from whatever reason, a complete rebuilt of it should fix it. Therefore, why does one use lspfix instead of winsockfix?

 

Still nothing, new questions...

Thanks for the advice, Scott, but I had already tried Winsockfix previously. But on your advice, I tried it again. In fact, I tried the original Winsockfix and Winsockxpfix v1.2. Both had no effect, I still have the Automatic Private Address and can't renew the IP. (And BTW Scott, your Winsockfix download page only works if you attend UVA.)

After that, however, I was rooting around in the menus in the Network Connections window, and I noticed a couple of things. In "Advanced > Optional Networking Components..." I came upon a list of add-ons I haven't seen before. The names sounded promising, so I thought I'd ask and see if my system is misconfigured somehow.

Under 'Windows Optional Networking Components Wizard' I only have "Networking Services" installed. Here is a screenshot of that window.

If I go to the 'Details' of "Neworking Services ", I find that I only have one of its components installed, and the others look like they might be helpful. Here is a shot of that window.

My question is, do I need to install any of that stuff? Some of the descriptions sound like they might be helpful or even necessary, but I am pretty desperate. Thanks for any advice.

JohnM

 

Sorry,
Wrong link.
http://www.tacktech.com/display.cfm?ttid=257

It isnt the same as LSP Fix.
The machines that I worked on LSPFix didnt find anything wrong.

Can you ping that 169. address?

Sure sounds like a cable or bad nic.

 

Rule that out buy either throwing in another NIC or trying a USB NIC.

 

Well, "throwing in another NIC" means changing out the entire motherboard of this Dell Inspiron. I am trying to avoid that, because I can just as well buy my wife a new laptop for what that would cost (~$700). Like I said, I'm not an IT pro and I don't have a bunch of hardware lying around.

As for a USB NIC, do you mean the little USB adapters that take RJ-45 plugs, like this one?

If that would isolate a problem with the onboard NIC, wouldn't a wireless card do the same thing? I have a Linksys Wireless-G card I just got, brand-new, and it produces the same problems as the cabled connection. Do all of those devices use some hardware component that could be faulty?

I'll try pinging the 169 address, and using another cable (although this would be bad cable #3). Thanks for the continued attention.

JohnM

 

Yep, or This One

The wireless could be a seperate issue.

 

Uh, new information!!

Okay, this should shed some light on my problem, although I don't know where that light is shining. (Staff of Ra, anyone?)

I am posting this reply from the problem computer. Somehow I got to thinking about cable swapping. So, on a whim, I yanked the Ethernet plug out of my Power Mac (which has no problems connecting), and swapped it out with the cable that was plugged into the problem Dell laptop.

Guess what? The Dell LAN connection suddenly contacted the DHCP server and got its own IP address. I got Google and everything. And WindowsBBS, as you can see.

But wait, it's a little weirder than that. Just to see if it was going to cooperate, I hit the 'Repair' button, and got the same problem results, "Could not renew the IP address ". Even though the IP address had just been renewed. And the IP stayed set to the valid one.

Okay, so since that worked, I tried again, with yet another cable that I knew had worked previously. This time, the Dell was back on its own Ethernet plug going to the router/modem, not the Mac's. The problem was back, no DHCP contact. I tried switching router connectors. Nope. But now I'm back on the Mac's cable and doing fine.

It seems as though the router/modem will talk to the Dell, if the Dell is connected over a cable that has had a previously good connection, and yet the computer gets its own valid IP address. Does this appear to be a router/modem problem?

I haven't tested all the possibilities yet, cables and connector combinations and such, but I will report back with any further results. This is getting too weird for my know-how, so any more help will be just as appreciated.

JohnM

 

Use a known good cable.

Go into the settings for the network card and set it for a speed of 10Mbps and half-duplex (depending on the card this may be two settings or may be a combined setting). See how it works then and let us know.

 

10Mbps and half-duplex
Man, ill bet thats it too. That would explain the hardwired connection problem. nice shot.

That still doesnt explain why the wireless card isnt tracking. Wonder if hes got a rig that isnt liking the autoconfig.

Open Network Connections.
Right-click Wireless Network Connection, and then click Properties.
On the Wireless Networks tab, clear the Use Windows to configure my wireless network settings check box.

Has this wireless card ever worked? Can you haul that machine over to a friend or neighbor to test it on a different router? We've got a lot of single failure points of data, im just trying to whittle away the possibilities.

 

More info

All righty then. "Joy ".

After my last post, I realized that the wireless card, which I had uninstalled, would work after all. Since I could get an IP on the cable, no matter how dodgy, I figured the wireless would work. Turns out, I hadn't had the router fully set up the last time, so now when I installed the wireless card, I got on the wireless connection with no hitches. I have a wireless internet connection on the Dell laptop now, connected instantly with the DHCP, valid IP, no apparent problems. I even installed XP SP2 with it. So yeah, Ben, the wireless works, and thank you.

Newt, my 'connection revelation' was with a known good cable. I had been using what I thought was a good cable, brand new and all, and I thought it was a 'straight' connection cable. Now, I'm not so sure. Can you get a valid connection and no good data if you're using a crossover cable by mistake? I have a number of home-made cables which are doing quite well on the other two machines, and I will do some more testing with those to try and resolve that.

Also, yes, switching to '10Mb Full' was one of the first solutions I found, because the connection kept switching back and forth fron 'unplugged' to 'connected', approximately every 10-20 seconds. Does that sound familiar?

Again, thanks for everyone's help and attention.

JohnM

 

Unless you have some hardware that can auto-sense the type of cable (regular or crossover) and compensate, you MUST be using the proper type. Note that some switches have a toggle switch that can change a port from regular to crossover very easily so one type of cable can do all your connections. Some (usually more expensive) lack the manual switch but will examine a connection and set themselves automatically so you have a connection. Don't bet on having either variety though.

General rule of thumb is that like devices (PC-PC, switch-switch) require crossover where Tx at one end goes to Rx at the other. Unlike devices (PC-switch) requires regular (pin1-pin1, pin2-pin2, etc). The wrong wired cable should not work at all.

Easy enough to check since the wires are color coded. Hold the two ends together and look. A regular cable should be an exact match at both ends. Crossover should have a pair of wires 'crossed' to different pins.