wifi won't stop 'acquiring network address'

[tayabi]

Hello,

I have an nLited XP on my dell mini 9. Clearly I've buggered something. All of my drivers seem to have installed fine because my WiFi is recognized, I type in the correct password and it starts to acquire network address. Unfortunately, it never stops acquiring and actually connecting.

Upon checking the DHCP service in services.msc, I noticed that I can't start the service as it just gives me this error:

Error: Could not start the DHCP Client Service on local computer

Error 1068: The dependency service or group failed to start.

I've done a bit of googling and have the 3 necessary sys drivers (afd, tcpip and netbios). However, I'm unable to start up the netbios.sys (the other two are already running), but there is no option to start netbios, nor does it start on boot.

Any ideas what I can do or what I might be missing?

Thanks kindly

[GrofLuigi]

Search the forum some more, I remember there were similar questions about this issue.

What you can do right now:

In REGEDIT, go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Dhcp

Delete netbios from DependOnService. Carefully! (or is it netbt, I have deleted it on mine ; just make sure there are Tcpip Afd in there)

or

Go to device manager (once there, set "show hidden devices" from the menu), go to "non plug and play drivers", it's there -> "netbios over tcp". Invoke its properties and on the "Driver" tab check if it's started; start type is "System" on mine.

If you have nlited it away, first solution should work; second not. If you have any problems, report.

GL

[tayabi]

Thank you for your help GroftLuigi. I'm not sure what worked, but something did.

I tried the regedit change first, rebooted. Didn't seem to help. Tried the second change, rebooted, didn't seem to help. But then I rebooted again later and suddenly things were working. Perhaps I didn't give it enough time after one of the reboots.

Based on these findings, do you have any what I might've removed from my XP install that caused this to happen? It would be useful to know in the event that I nLite again and don't have to go through the process of fixing it.

Thanks very much!

[GrofLuigi]

You're quite welcome.

There are several things you could have done, maybe changed the Start type of some service, removed drivers and/or Windows features and/or hardware support, but...

Most probably it's by design.

GL

*EDIT: by design of Windows!

Edited March 27, 2009 by GrofLuigi