A permanent fix to resolve the behavior described above is to set the value of TCPIPHostBindMode to 0 on the affected computers. Continue reading for more details...
The following registry key controls the behavior of the Symantec pcAnywhere Host Service with respect to how it binds to available network interfaces:
Key: HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\pcANYWHERE\CurrentVersion\System
Type: DWORD
Settings:
0 = Bind to default network adapter
1 = Bind to every network adapter
2 = Bind to specific network adapter defined by TCPIPHostAddressIndex
For more information about TCPIPHostAddressIndex, see the Related Articles section below for a link to an article entitled "How to have a pcAnywhere host wait on a particular TCP/IP address".
For the Symantec pcA agent, the default values are:
TCPIPHostBindMode = 1
TCPIPHostAddressIndex = 0
Set TCPIPHostBindMode to 0, rather than its default value of 1, to resolve this issue. It is not necessary to make these changes for all VPN client software. Therefore, Symantec has no plans to change the default values.
ref:
http://www.symantec.com/docs/TECH138227