Community

Hi again!

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?

Brgs,

Hi!

I'll collect logs from the remote machine next time I have the chance.

In previous logs, posted here, it looks like it can't reach the servers. But this particular time the user reported that they had full access after the VPN came up. I also verified this by asking them to do a restart* and first connect VPN and then start/restart the Agent. Then I had no problem connecting with the Internet-ID again.

*Last encounter with this problem the users at the remote machine was not very techsavy. I asked for a restart of the Agent, but the whole machine was restarted instead This is the same machine I'll try to get hold of the logs from.

Brgs,

You probably mean Host, not Agent?

Yes, I the remote side, the client.

So am I right assuming that without restarting the remote Host you can't get to the remote PC after it switched to the VPN?

Correct.