Shrew Soft VPN Client Routes Traffic Incorrectly After Waking From Sleep

I recently needed to connect to an old Cisco IPSEC VPN from my Vista Ultimate x64 system, but the Cisco VPN client was a 32-bit program and would not install on a 64-bit system. I installed the free Shrew Soft VPN client instead, and it would work just fine on a fresh reboot. However, once I had put the computer to sleep once and woken it back up, it would fail to route traffic correctly. When the VPN client was in this state, I could connect successfully to the VPN, but attempts to ping a remote system would time out, and a tracert would result in “destination host unreachable”. After a bit of experimentation, I discovered a solution that would not require me to reboot my computer: Restart all 3 ShrewSoft Daemon services. This can be done through the Services MMC console snap-in, or by running the following commands from an elevated prompt:

net stop "ShrewSoft DNS Proxy Daemon"
net stop "ShrewSoft IKE Daemon"
net stop "ShrewSoft IPSEC Daemon"
net start "ShrewSoft DNS Proxy Daemon"
net start "ShrewSoft IKE Daemon"
net start "ShrewSoft IPSEC Daemon"

I hope this saves someone else some time.

comments powered by Disqus