I have a Vaio TR3 laptop running XPpro. I connect to the internet at home via WiFi and at work via LAN.
Prior to the past June/July, I was able to set my system to hibernate and then resume with full network functionality. Currently, if I transition from home to work or vice versa, I must reboot to have functional network access. Furthermore, if I hibernate at home and then resume, network functionality is OK. If I hibernate at work, a reboot is required to get to the network.
Curiously, a check of the network connections doesn’t reveal any obvious problem; even though there is no functionality, the wireless or LAN connections show that a connection exists.
Around the time that the problem developed, I had renewed my Symantec internet security subscription. From recent reading, I’ve learned that this is a troublesome bit of code so I removed it and installed AVG + firewall, but that didn’t solve the issue. I’ve also run ad-aware and antivirus scans with both Norton and AVG.
I use VPN to access my work network from home. I used it for 2 years without difficulty and no changes made to the software within this time period. I mention it, though, because when running, VPN causes my network to function peculiarly (e.g. I can’t see other systems on my home network with VPN running), though I doubt it is the source of the problem.
Possibly some change has been made to the monitoring protocols for the work network and it’s now logging you off if no activity is detected?
Might want to also check your setup BIOS power settings (not XP settings) and see what power defaults are set to and whether network port is being shut down…
The desktop computer I have access to at work does not have this diffculty on resume from hibernate.
I don’t think this is a powering issue because the network devices report that they are functioning and connected to the network while the problem is occurring.
Networking issues are difficult to resolve without actually having physical access to the machines, but see if the following helps at all…
Instead of rebooting, try:
a. Right click on the wireless icon in the tray, and select “Repair”
or
b. Disable and then re-enable the wireless adapter
or
c. Stop and re-start the Wireless Zero Config service:
Go to Start/Settings/Control Panel/Administrative Tools/Services/ and scroll down to “Wirless Zero Config” and stop and restart the service
My WAG is that option c. should allow you to re-connect without a reboot.
You could also prevent the computer from cutting of power to the network card, which can cause hibernation issues on the occassional computer.
Try this:
-Open your network connections window (by right-clicking on “My Network Places” and selecting ‘Properties’, for instance).
-Right click the offending adapter and select ‘Properties’
-Click ‘Configure’, and then the ‘Power Management’ tab
-Uncheck the first checkbox.
It could be something else, too - I had a fairly new HP laptop which wouldn’t stay connected with 802.11g for more than two minutes - it’d lose its mind and reconnect in about 30 seconds, about 9/10 of the time. Meaning that I’d have to restart the network manually every 5-15 minutes on average. It was driving me nuts. I eventually determined that my woes were caused by me accepting a new network driver from Microsoft’s Windows Update. Apparently the driver wasn’t quite right for the chipset as implemented by HP. Backed it out, and all was well.
Thanks for the suggestions. I’m at work today so I’m testing things out on the LAN (The wireless network is at home).
As I stated above, if I have network functionality via LAN then hibernate and resume, I reconnect to the LAN but lose functionality. The same result occurs after a standby–>resume.
I tried the network repair function and though it went through the motions, functionality was not restored. I tried to disable/enable the network card without restoration of functionality. I also tried to uninstall/reinstall the driver for the LAN card. However, the complete reinstall required a reboot (which restored function), but that’s no fair. An aside, on the reboot after reinstall, XP prompted me to note that the driver software was not WinXP approved or some such. Could this be the source of my woes?
Midget, I tried this for the LAN card and it didn’t help. My wireless card does not have software power control; instead there is an on/off switch on the outside of the laptop that generally remains in the on position.
Ambushbug, I am suspicious of the drivers but since neither the wireless nor the LAN device function properly after resume, it’s hard to imagine a single driver causing both issues. Nevertheless, I’m off to update and/or roll back the drivers.
I’m wondering if this might be something to do with the DHCP lease time on your work LAN; that not only is your machine temporarily backing off from the network (as it should when you hibernate), but that the router is timing out and giving up on the idea of you returning.
