When a managed computer (most likely a laptop) with the pcAnywhere Agent is moved to a location off of the corporate network, and then certain VPN client software is used to connect the computer to the corporate network, the pcAnywhere host will not accept remote control attempts from the corporate network.
After a VPN connection is established using some VPN client software, the pcAnywhere Host Service does not automatically bind to the new network interface which is created by the VPN connection. This behavior has been seen with Checkpoint’s SecureClient software, although it may occur with other VPN client software as well.
A temporary work-around is to restart the Symantec pcAnywhere Host Service once the VPN connection to the corporate network is established, and then the pcAnywhere host should accept a remote control attempt.
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:
0 = Bind to default network adapter
1 = Bind to every network adapter
2 = Bind to specific network adapter defined by TCPIPHostAddressIndex
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.
pcAnywhere Solution 12.5