DHCP problems with Windows XP

[wessel]

A couple of days a go my internet connection suddenly stopped working. Initial investigation pointed out that DHCP did not work anymore as the default IP address became 169.xxx etc. and the following entry was found in the event log:

"Your computer was not able to renew its address from the network (from the DHCP Server) for the Network Card with network address 0004E20E3B00. The following error occurred:
The semaphore timeout period has expired. . Your computer will continue to try and obtain an address on its own from the network address (DHCP) server."

I have now entered a fixed IP address in the right domain (192.168.etc.) under 'alternate IP configuration' and everything works fine.

However, I'm still puzzled by the sudden failure of DHCP, which I've used without any problems on Windows ME for a year and on Windows XP Professional for a couple of weeks now. I've found related problems on various websites (including this one) and have tried some of the suggested solutions (to no avail):
-I've changed to encrypted communication (64 bit WEP) between access point and PC.
-I checked that I had SP1 installed (Microsoft suggestion)
-I've run WinsockXPfix
-I've reset router and AP to factory defaults
-De/re-installed wireless network card
-Disabled McAfee virusscanner


The fact that things work OK with a fixed IP address seem to suggest that all the hardware is OK(?).

Any suggestions would be much appreciated.

Thanks.

Wessel

 

[bcastner]

A firewall could easily lead to this result.

 

[bcastner]

There were several complaints here about McAfee antivirus. If you remove the program you can have problems with your Winsock service stacks.

You might try:

. Running the Winsock service stack repair tool now that you have made all of these changes:

http://members.shaw.ca/techcd/VB_Projects/WinsockFix.zip

I understand you have already tried this, but it is likely more important now.

. Make certain that 802.1x authentication is disabled on the client;

. Remove the Hotfix 815493 from the client if using XP. You can use control panel, add/remove programs to do this.

. Make certain your adapter settings are set to Auto and not a fixed rate

 

[wessel]

Thanks for reply, bcastner!

-I've disabled 802.1x authentication
-I've set adapter rate to 'Auto'
-I've complete de-installed McAfee
-I've re-applied WinsockFix

-I can't find Hotfix 815493????? There's a whole list of hotfixes, most of them have the "(SP2)" suffix (which I assumed included SP1).

Result is still the same (i.e. DHCP does not work). In addition, I can now no longer reach my AP with the Belkin Access Point manager (this is not a result of the changes above, but just happened). Everything still works though with fixed IP. Signal strength and quality is very good (>80%).

Any ideas?

Wessel

 

[bcastner]

For XP only, and it would have helped if I had not mis-typed the Hotfix. It is Hotfix #815485.

See this recent thread on the issue:

http://www.tek-tips.com/viewthread.cfm?spid=730&newpid=730&sqid=582449

You might review the adapter settings through Device Manager. Use the "Configure" button under the name of the adapter in its properties sheet. In particular look at the "Advanced" settings for the adapter. The Channel, SSID, WEP settings, etc. must match exactly the router settings.

These are quite often overwritten if you update the adapter driver.

 

[smah]

Hehe...food for thought...

I went throught this yesterday over the phone with a user without success. Tried all the fixes, hardware checks and system restore. Sometime last night the user even did a full restore from the manufacture's disaster recover cd's. Still nothing.

The user brought the laptop in today and I noticed one of the pins in the RJ-45 jack was bent. I fixed it as best I could with a pair of tweezers, plugged in an ethernet cable and the machine was as good as new. He suspects his son tried to plug the phone cord into the ethernet port.

 

[bcastner]

smah,

And this fixed DHCP problems on his wireless adapter????

Unbelievable.

Best,
Bill

 

[bcastner]

smah,

What is odd in this instance is that it looks as if the client is making the right request for DHCP services, just not getting a response back from the wireless router.

wessel,

Be sure to check the router settings so that everything is identical to that of the client settings. Some SSID's are case sensitive; most WEP keys in ASCII are case sensitive. So MYCOMPUTER and MyComputer are not the same key.

 

[smah]

Sorry, I missed the mention of wireless network card and access point. Disregarding that, I mentioned that for a for others reading the thread for possible troubleshooting of this type of problem. I certainly would never have guessed what I found.

 

[bcastner]

Nor I.

Thanks for the tip.

Bill

 

[wessel]

Thanks for all your suggestions!

SSID, WEP settings are all fine. Proven by the fact that everything does work as long as I use a fixed IP and not the DHCP.

I'll try and find that hotfix and remove it.

Wessel

 

[wessel]

Couldn't find that hotfix.

Upgraded firmware of router (Asus 6000EV) which worked! Still not quite sure why as things used to work with old firmware.

Thanks for all your responses.

Wessel