Delay in connecting to wireless network while resuming from Hibernate or Sleep

I have a Dell Studio XPS 1647 with Intel 6250 Wireless-N w/WiMAX.

When the laptop is turned on (after it is Shut Down), it connects to my home wireless netork by the time I see the desktop. But when it resumes from Hibernate or Sleep, it takes about a minute or more (after I see the desktop) to connect to the wireless network. When I contacted Dell regarding this, they said that this is normal. I doubt this.

I used to have a Dell Inspiron 17" laptop and I've never noticed any delay in connecting to the wireless network when it resumes from Hibernate or Sleep.

Do you guys think it is normal for the laptop to take so much time to connect to the wireless network when it resumes from Hibernate or Sleep?

 

It's not normal. You should be connected within a few seconds of powering on. I've never seen a laptop not already connected by the time I log in after sleep or hibernate (besides the obvious exceptions of the radio being off, not being in range of the router, ect.).

 

i had the same problem before. i could connect to wireless once i turned on the laptop, but when I plug in an physical cable connected to router, then unplug it... it wouldn't connect again. As well as your problem with sleep/hibernating.

Fixed it by reinstalling some drivers.

yeah so my only suggestion is make sure you have the correct driver installed from the dell website. otherwise, i hope there are some techies can give you some pointers.

 

You guys are awesome. I un-installed the drivers and re-installed them from Dell's website. The laptop now connects to the wireless network almost instantaneously when it resumes from Hibernate or Sleep.

Earlier, when I contacted Dell support regarding this issue, they did some troubleshooting, but nothing worked. They asked me to go for the paid support because they thought the issue was caused by some software installed on my laptop. How ridiculous? When I told them that it's been like this from the beginning, they asked me to restore the laptop to the factory settings and check if the issue exists. I'm glad I didn't go that route.