Encryption and Authentication Algorithm.Remote ID for the router (which is the routers IP address).Remote Endpoint - both connect to the same router.The clients share the following settings (they actually don't share those because as I said before these are different policies, but have the same settings configured): different Local-IDs when viewed from the VPN client). To mititgate this problem I made sure that both users are using discrete VPN policies with different Remote-ID values as seen by the router (resp.

Therefore I believe, that it isn't really the RDP session that is dropping but it is the VPN dying and the RDP session is timing out. I could observe that the RDP session does not drop immediately but after a couple of minutes while the roadwarrior told us he lost the connection immediately after my customers connection was established. While I was having a look at the connected RDP users (roadwarrior is connected) my customer established a VPN connection. If Client-B (customer in homeoffice) connects to the VPN, the RDP session to CLIENT-A drops.Connection is stable and works without issues.Client-A (roadwarrior) establishes a VPN connection and RDP session to the server.The roadwarriors (and my customer in his homeoffice) use the VPN Client to connect to his company network and use a RDP session to a terminalserver in the office to work with our applications. He (and a couple of his employees) also use the ShrewSoft VPN software client to connect to the office while on the road. My customer is using a NETGEAR FVS338 for internet access and s2s-connectivity for his two locations, which works flawlessly.

Check point vpn client dropping