Wireless Connection works, but takes a minute...

[NYJimbo]

Have you verified that it is persistant ?

[FoolishTech]

I'll know for sure monday when I get home from work (I mentioned it only happened if my last connected network was different than my home network.)

[FoolishTech]

Well no.......... back to the same problem again, must have been a fluke on Friday.

[YOCS]

Originally Posted by FoolishTech

Well no.......... back to the same problem again, must have been a fluke on Friday.

My first thought was there must be something in D7 that can fix this (there isn't right? )

I'm not sure if this will help but, I had a similar problem only the laptop wouldn't connect at all at the work location but, had no problem connecting at the users home.

This registry entry resolved the issue.
HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Param eters create a new “DWORD Value” named “ArpRetryCount” with the value set to zero. Reboot.

[datagnostic]

- Can you verify that the following option is disabled in your device management?


(just a random pic from google search)

- What security method are you using? WEP, WPA or WPA2?
- Probably using a preshared key?
- For WPA/WPA2: what encryption in use? TKIP or AES/CCMP?

Might be worth comparing the security/encryption methods between two sites.
Intel's wireless chipsets, for example, do not always play nicely with the TKIP standard. You can google "tkip countermeasures intel centrino" for an example

[FoolishTech]

I do have it set to allow device to be turned off to save power - I'll disable that option, and also try the reg value. We'll see what happens when I get home today...

Both networks are WPA2 AES, the only differences are the SSID and password of course, and that the home network where the issue occurs is N and the work network is G.

[datagnostic]

I was just thinking, as you mentioned it connects immediately you can pretty much rule out the security settings because it's already associated -hence, past the authentication phase- at that point.

Anything in the eventvwr? Something from the tcpip or dhcp instance?

Do you have the same IP ranges on both networks? Because it could be that it associates to the SSID immediately after waking, but it needs some time to release and renew it's DHCP lease.

If you have the same scope on both networks, it would probably try to do a dhcp REQUEST for the address it previously had. You could probably get a better view with Wireshark or Aeropeek if this was the case.