Thanks to my shitty job, I've been forced to work nights/weekends a LOT lately. In theory, I should be able to work at home using VPN...except that every time I access the VPN, my computer reboots within minutes, or even seconds. If I don't get this fixed, I'm going to lose my fucking mind, since it means that I have to come into the office for even trivial tasks like checking email after hours...and I don't have a choice at the moment.
THE CONFIGURATION:
Compaq Evo 800c laptop computer
Windows 2000 Service Pack 3 (5.00.2195)
Cisco VPN Client version 4.6.00.0045
Netgear WG511 wireless PCMCIA card (802.11b/g)
Netgear WGR614v5 wireless router (802.11b/g; 128-bit WEP enabled)
Zone Alarm (free version)
ADSL 768/128 through Verizon (static IP)
THE PROBLEM:
Getting started: Boot the laptop, insert the wireless card, and wait for it to recognize the network. At this point, the situation is perfectly stable -- I can surf the web all I want, and the connection will persist with no problem...but when I access the work network, I always get the same failure: Start the Cisco VPN software, choose an access site, provide username/PIN/SecurID token, and I get onto the VPN successfully. However, within a few minutes -- sometimes under a minute -- I will get a pop-up message indicating that lsass.exe has failed with code 128, and that the system will reboot in 60 seconds. This happens 100% of the time when I try to access the VPN from my home network. The same configuration has successfully accessed the VPN with a connection that was stable for hours from various hotels and other access points while I was on travel, although this same error would occasionally (1 time out of 10?) happen even at other locations.
THE STEPS I'VE ALREADY TRIED:
1) Upgraded Cisco VPN client from version 4.0.4 to version 4.6.00.0045 -- NO DIFFERENCE
2) Upgraded router firmware from v1.0.3 to 1.0.7 -- NO DIFFERENCE
3) Connected my laptop to my router using an Ethernet cable, rather than the wireless card -- NO DIFFERENCE
4) Forced the wireless connection to operate as 802.11b rather than 802.11g -- NO DIFFERENCE
5) Ran a full antivirus scan -- NO PROBLEMS
The one thing I wasn't able to do was test the VPN connection as a "bare wire" to the DSL modem since I couldn't get my computer to see the connection, even when I changed it from DHCP to static IP using the correct IP/subnet mask/gateway/DNS values. However, I'm increasingly skeptical that it's a router issue, and my father (an IT manager) shows my particular wireless router as one of three preferred types for the VPN at his company. It's also interesting to note that the VPN connection seems to be relatively stable until something (Lotus Notes, Firefox, etc.) starts accessing the network, though I didn't let it sit there for a long time to run a thorough test.
Any ideas? The Google results for lsass.exe with error code 128 are dominated by the Sasser worm, but that is NOT the case here. The laptop is perfectly stable until I access the VPN from home (and rarely from the road) -- if it was Sasser, the computer would never operate without the error/reboot cycle.
Thanks for any help -- I'm going nuts here, and this office SUCKS on weekends.
THE CONFIGURATION:
Compaq Evo 800c laptop computer
Windows 2000 Service Pack 3 (5.00.2195)
Cisco VPN Client version 4.6.00.0045
Netgear WG511 wireless PCMCIA card (802.11b/g)
Netgear WGR614v5 wireless router (802.11b/g; 128-bit WEP enabled)
Zone Alarm (free version)
ADSL 768/128 through Verizon (static IP)
THE PROBLEM:
Getting started: Boot the laptop, insert the wireless card, and wait for it to recognize the network. At this point, the situation is perfectly stable -- I can surf the web all I want, and the connection will persist with no problem...but when I access the work network, I always get the same failure: Start the Cisco VPN software, choose an access site, provide username/PIN/SecurID token, and I get onto the VPN successfully. However, within a few minutes -- sometimes under a minute -- I will get a pop-up message indicating that lsass.exe has failed with code 128, and that the system will reboot in 60 seconds. This happens 100% of the time when I try to access the VPN from my home network. The same configuration has successfully accessed the VPN with a connection that was stable for hours from various hotels and other access points while I was on travel, although this same error would occasionally (1 time out of 10?) happen even at other locations.
THE STEPS I'VE ALREADY TRIED:
1) Upgraded Cisco VPN client from version 4.0.4 to version 4.6.00.0045 -- NO DIFFERENCE
2) Upgraded router firmware from v1.0.3 to 1.0.7 -- NO DIFFERENCE
3) Connected my laptop to my router using an Ethernet cable, rather than the wireless card -- NO DIFFERENCE
4) Forced the wireless connection to operate as 802.11b rather than 802.11g -- NO DIFFERENCE
5) Ran a full antivirus scan -- NO PROBLEMS
The one thing I wasn't able to do was test the VPN connection as a "bare wire" to the DSL modem since I couldn't get my computer to see the connection, even when I changed it from DHCP to static IP using the correct IP/subnet mask/gateway/DNS values. However, I'm increasingly skeptical that it's a router issue, and my father (an IT manager) shows my particular wireless router as one of three preferred types for the VPN at his company. It's also interesting to note that the VPN connection seems to be relatively stable until something (Lotus Notes, Firefox, etc.) starts accessing the network, though I didn't let it sit there for a long time to run a thorough test.
Any ideas? The Google results for lsass.exe with error code 128 are dominated by the Sasser worm, but that is NOT the case here. The laptop is perfectly stable until I access the VPN from home (and rarely from the road) -- if it was Sasser, the computer would never operate without the error/reboot cycle.
Thanks for any help -- I'm going nuts here, and this office SUCKS on weekends.
