Hi all! I'm having a problem with my wireless card, which is an Intel wireless wifi link 4965AGN in my Sony Vaio VGN NR31Z. Just yesterday the following problem started tormenting me: every time I awoke the computer from sleep mode, the wireless card was not working. The device manager continues to show the card as operative, even though it is not. For the card to work again, the laptop requires a restart, every time. Could you tell me what to do with this problem? Like I said, this problem just appeared out of nothing. But I suspect that the problem is linked to me restoring the computer (just yesterday) "to last known good setting" as a result of registry problems, which by the way still seem unsolved. Do you think this is a plausible cause for the wireless card failing? Thank you for your time and help. Leandro

When you "wake up" the laptop from this sleep mode and find the WiFi not connecting, before you restart the computer check the IPconfig of the 4965AGN, then check the IPconfig after the restart and see if it's the same. Since you say the device manager shows the device is operative, but it doesn't really work, then it might be the DHCP lease is being dropped by the computer or the router while in this "sleep mode" for some odd reason. When a computer is restarted, the DHCP lease is always renewed.

Pyrolitic, I put the computer into sleep mode, awoke it again, the wireless adapter still not working, so I checked on ipconfig. There the status of the wireless adapter was listed as "media disconnected", while in the device manager it still appeared as operational. Very strange indeed... You mentioned the DHCP lease being dropped by the computer or the router. I think it has to be the computer. Earlier today I experienced the same problem while attempting to connect to a public connection point in a library. Do you know of any way for resolving this problem? Also, I do believe something happened when I did a system restore, because the problems appeared right after that process was done. This is quite frustrating!

Sorry about not following up sooner, but I really did not have a good answer for you and thought maybe somebody else who has experienced this problem might come by. I have never seen this "media disconnected" listed in an ipconfig query, so I am not sure exactly what it means. It seems to imply that the IP software does not acknowledge the WiFi device even though the device manager does. I also don't understand how the system restore broke it. As you imply, it has been working since you've had the laptop and only started this behavior after you had the system restore return the laptop to it's "last known good setting". So, why would it return to a setting that wasn't good? Why would it change to a setting that had never been on the laptop before? It seems like this "system restore" feature has failed and you may need to go to the laptop and/or software support people to figure it out.

Hey Pyrolitic, no problem, I understand it's a very strange Issue my computer has. The DHCP lease failing that you mentioned is what's causing the connection not to work as soon as the computer exits sleep mode, which before I really wasn't quite aware of. So now it's about finding out what's causing the DHCP to fail while in sleep mode. I think I'll look on the Microsoft website for info, as well as on the Intel website. This problem is a real hassle, as I frequently put the computer into sleep mode (I'm a student, so in nearly every lecture I use my laptop). Just hope it can be solved without a complete start from zero..

Update: I have managed to resolve the problem. It seems that doing a system restore sufficed, yet I still do not know what could have caused the connection to fail when entering sleep mode. I still believe it has something to do with the previous restore i did when booting, selecting "last known good setting". At the time I had the intention of fixing a registry problem (still unsolved however) but somehow triggered this connection issue. It doesn't make much sense, as Pyrolitic said, but I couldn't think of anything else, unless the computer spontaneously caused the problem. Anyhow, it seems my problem is, at least temporarily, fixed.