Picking up this thread again.
When I need to help the remote side with a install or repair of a VPN connection. This is where the reconnection problems begin i believe.
I use Internet-ID to get in touch with the remote machine.
When the remote client establish a VPN the remote side obviously gets a new IP and in my case often a new default route, all traffic pushed through the tunnel.
After the above scenario I can't reconnect with the client. Have waited extended period of time for the Internet-ID to be updated with the new IP/Connection info, but nothing happens.
A competitive product of your seems to register the alias/Internet-ID after it detects a change in the network config (as in a VPN being established) and I can after a short while use the "alias"/Internet-ID to get remote connection again.
So, as I see it (novice of course on the technology behind) the core of the "not being able to reconnect" is that the Internet-ID and connection info is not re-registered as it should after a network change on the remote client. Maybe this also is the case when problems occur after some restarts?