When connecting RDP, the VPN connection is disabled. How to fix it?

Question

VPN

The question is the following. When connecting to the server via RDP, the VPN connection on the Virtual Machine is abruptly terminated. I go to the local administrator, and from another PC I go to the domain administrator via RDP. And after the domain administrator has logged in, the VPN abruptly stops its activity, and, consequently, the RDP connection is also interrupted, because. VPN connection is disabled. How to be in this case? Maybe someone faced such a problem? The firewall was turned off, to no avail.

Answer 1

VPN connected by local administrator?
If so, then most likely when a new user connects, the previous one simply throws out and, accordingly, everything that was launched by the local admin ends, incl. and the VPN connection is broken.
To solve the problem, you need to transfer the VPN connection to some kind of offline mode so that you do not need to keep a logged in user for it to work.
Another option - apparently RDS services are not licensed on your server, and in this mode Win Server allows a maximum of 2 users to work simultaneously, if I'm not mistaken. Perhaps you have disconnected sessions of two admins, at the next login one of the sessions is killed with the corresponding consequences.
In this case, you need to control the connected users, if the session is not needed, then "log out" and not disconnect. Configure for all users, except for the one under which the VPN is connected, automatic logout when inactive.
Or license Terminal Services for more users.

Answer 2

I apologize for necroposting, but I still found a solution, despite the limitations of Windows. Partly I write for myself, as a note, for everyone.
0. Create a VPN connection, check the box "Allow all users to use". Default Gateway - Disable. Here to whom as.
1. In the scheduler, create a task to start the connection - %SystemRoot%\System32\rasdial.exe <connection_name> login password
2. Run the task every minute on behalf of SYSTEM with the highest rights.
3. If you did not set the Main Gateway, we register the route to our LAN. The connection comes from the SYSTEM, so the route must be registered from the same user:
3.1. Run the shell - PsExec -i -s powershell
3.2. We check under whom it works - whoami, it must be a system
3.3. We register the route - netsh interface ipv4 add route 192.168.33.0/24 <connection_name>
3.4. We reconnect, it may not work right away.
Ready.