Cisco VPN problem

Unfortunately we don't support in RDM to have the status. There is no easy way for us to detect an open VPN.

We will add this if we can find a solution or a workaround.

no problem. possible idea is to add an option to constantly ping something on the network that shows whats connected in a separate window.

Could it be possible to check the Windows Registry for an open VPN? At least in case with the Cisco VPN client. The documentation for the Cisco VPN Client (http://www.cisco.com/en/US/products/sw/secursw/ps2308/products_qanda_item09186a00801c2dbe.shtml#mis) says the following:

Q. How can I tell if a VPN client is connected to the VPN concentrator?
A. Check the registry key named HKLM\Software\Cisco Systems\VPN Client\TunnelEstablished. If a tunnel is active, the value is 1. If no tunnel is present, the value is 0.

Very interesting. I was not aware of this. Does it make a difference if you have multiple cisco VPN configured in RDM. Do we mark them all to running?

I would guess that only connected VPN tunnels should be marked as running in RDM. But I am not sure I completely understood the question. I think in the case with the Cisco VPN client it should be possible to use the command line options to print the current running profile (connection entry) with for example "vpnclient.exe stat tunnel".

To be able to maintain a correct running status in RDM for VPN tunnels perhaps some type of functionality is needed that can be scheduled to periodically run some sort of configurable script or command per VPN entry in RDM to report back the tunnel status to RDM. Such scripts or commands could for example: run ping commands, check existing routes, check network adapters, or whatever that can tell status for specific VPN tunnels.

I will see what we can do but it seems to be more tricky than expected. We don't want to generate a performance problem with a ping or an schedule task.