• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Wireless network stuck at "acquiring network address"

F

Fresh Daemon

Senior member
I'm completely stuck here. I have an Asus M6Ne laptop with an Intel 2200BG wireless adapter. This thing worked just fine wirelessly until yesterday, when I had to reinstall Windows, ever since that it won't get an IP address from my router (Belkin F5D7230-4).

My roommate's laptop is connected wirelessly just fine.

Security is WPA-PSK with TKIP, but I have tried turning that off, it makes no difference.

The laptop can detect the network (and other networks in the area) no problem.

If I specify a manual IP, it "connects", but then doesn't actually have any network access - no Internet, no shared folders, no other computers on the network, nada.

I have tried all channels between 1 and 11. I don't have MAC filtering on, DHCP is enabled, IP pool has plenty of spare addresses.

I've tried running the network setup wizard and wireless setup wizard, but that did nothing. I'm running XP SP2.

I know there's a lot of people in this forum who know a sight more about networking than I - can you help? Thanks!
 
No, I didn't. First, I've tried that half-a-dozen times already. Secondly, I have disabled encryption, and thirdly, I also tried WEP instead, and exactly the same thing happens. Therefore, it's not a key problem.
 
Reading comprehension ftl....

sorry, I didn't see the "tried without encryption" bit. When it fails to get DHCP, 99% of the time it's a mistyped key. I would turn encryption off, make sure SSID broadcast is on, and that MAC filtering is disabled. I would also use the Intel Proset utility, as it has some features that WZC doesn't, such as logging and troubleshooting. See if you can get that to work, then layer security back onto the AP a step at a time.
 
Make sure you don't have wireless zero config service running and the intel proset utility as well.

Agree that windows gives you no information, disable the service and try the client utility.
 
The proset did it... I disabled the WZC, installed proset, tried to connect, same problem. Then I disabled the security, and it connected. So I re-enabled WPA-PSK, and it connected as well. Weird, but it works now, so whatever! 🙂

Thanks for your help, guys! I really appreciate it.
 
Originally posted by: Fresh Daemon
The proset did it... I disabled the WZC, installed proset, tried to connect, same problem. Then I disabled the security, and it connected. So I re-enabled WPA-PSK, and it connected as well. Weird, but it works now, so whatever! 🙂

Thanks for your help, guys! I really appreciate it.
Click to expand...

You're welcome.

I cannot stand WZC. For others - these are the big causes of wireless trouble:

1) mismatched authentication/encryption (this is why you remove any and all encryption/authentication to troubleshoot) Most always a bad key is the problem.

2) repeat step number 1

3) if encryption/auth is off on the AP then it's an OS or interferrence problem or see #4

4) windows zero config service is running and fighting with client utility. Hence it's #3 problem.

Many can disagree - but always use the utility included with your wireless card.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top