http stops after 10 minutes but not https

September 11, 2010 at 11:34:49
Specs: Windows XP
no matter what connection type, no matter what browser, http stops working exactly 10 minutes after a reboot, while I can still navigate to https and ftp URLs, and it affects only one laptop using the same DSL or WLAN. At the office, if I set a web proxy for the LAN on port 8080 the problem does not occur... it is not a firewall issue, nor a winsock issue, already tried netsh winsock reset and netsh int ip reset reset.log.

See More: http stops after 10 minutes but not https

Report •


#1
September 11, 2010 at 16:32:54
Look at the event viewer.

How do you know when a politician is lying? His mouth is moving.


Report •

#2
September 11, 2010 at 18:20:27
The only System Event log entry I could see and that could somehow be related to this is from the Service Control Manager, Event ID 7023, "The Windows Firewall/Internet Connection Sharing (ICS) Service terminated with the following error: The class is configured to run as a security id different from the caller."

But this happened only once, not at every reboot (nor 10 minutes later).

There are no related Application Event Log entries at all.
The Internet Explorer Event log is empty.


Report •

#3
September 11, 2010 at 22:15:19
I searched Google & besides seeing that you didn't get an answer in the tech support forum either, I found two solutions. One user said:

"I resolved this problem by restoring my system to a point 10 days ago before the problem began. I looked over changes that had been done in that timeframe and they included a Cisco VPN reinstall (which may have been to solve the problem earlier) and, more suspect, installing Windows Live Update. I removed that earlier in any case. I think that is suspect. Also, the Cisco may have been an issue but I cannot be sure at this point."

The second solution, is in the second post at:

http://www.windowskb.com/Uwe/Forum....

Let me know if either of them worked or not.

How do you know when a politician is lying? His mouth is moving.


Report •

Related Solutions

#4
September 12, 2010 at 01:21:24
I had seen the first article in the link above, but not the second, which actually led me to the root cause. Cisco VPN client does use ZoneAlarm firewall portions. I use Cisco and Nortel VPN clients from the same PC, and in order to avoid any conflict, I had set the Cisco VPN service to manual startup. This alone however was not causing the issue. The issue started only after a Windows XP repair some weeks ago.

In the meantime I've found the solution in another thread from 2007, giving HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\vsdatant\start a value of 3 (instead of 2) I was able to set the Cisco VPN client service to manual again without re-creating the problem. Had it been the Windows Repair that set this to the wrong value or whatever, I don't know.

Courtesy of Ralph Whitbeck.
http://ralphwhitbeck.com/2007/07/10...

It's amazing how many people must have rebuilt their PC in despair while this is just a simple registry setting, once you know where...

Thanks anyway.


Report •

#5
September 12, 2010 at 06:33:08
That registry key doesn't exist unless Cisco VPN is installed. Apparently, the problem can be caused by Cisco VPN &/or Zone Alarm. Not everyone with that problem was using Cisco. If someone just has Zone Alarm installed, then the second solution I posted would work. I book marked both of those pages.

How do you know when a politician is lying? His mouth is moving.


Report •

#6
September 12, 2010 at 14:26:17
Intrigued by all this I decided to dig further. I decided to rename vsdatant.sys to vsdatant.old and rebooted. Nothing serious happened. I then proceeded to delete all vsdatant related registry entries, where I found really strange stuff like class IDs that pointed to C?\\WINDOWS\\system32\\vsdatant.sys (questionmark instead of colon after the drive letter!).

At some point in time it started to generate TrueVector Service errors in the application event log like crazy. I suspected the Stateful Firewall in Cisco VPN client to be the cause but no, I can perfectly use Cisco VPN client v5.0.00.0340 with Stateful Firewall off or on and the event log does not show any further errors of this type.


Report •

#7
September 13, 2010 at 05:47:23
I wonder why the question mark is there. I searched my registry for C?. It wasn't there. I would expect a $ first. Cisco must do some strange things.

How do you know when a politician is lying? His mouth is moving.


Report •

Ask Question