Software VPN is dropped when connected over RDP. How to fix?

You have a server with Win 2008 R2 x64. It created several users that connect via RDP (Remote App, but if you open just the desktop, the problem is the same). Installed on the server programm Bel VPN Client 4.1. The idea is vpn software. When starting asks to press the button to connect. So if someone connects via RDP, the vpn connection disconnects. How do I "share" the connection for remote users ? They are using this vpn must go to a certain website. I have to say if the properties of the network connection in the Access tab put a tick "Allow all users to use this connection", then vpn does not work (does not connect).
June 5th 19 at 21:16
3 answers
June 5th 19 at 21:18
Solution
The question was decided as follows: program Bel VPN Client 4.1 there is an option "Silent mode login" by default when another user breaks the connection. (Though for some reason cuts off and on a terminal server is not clear). In the registry HKEY_LOCAL_MACHINE\SOFTWARE\VPN Agent\NonInteractiveLogin to put 1 or HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\VPN
Agent\NonInteractiveLogin to put 1. RDP connection is no longer interrupted session.
June 5th 19 at 21:20
So if someone connects via RDP, the vpn connection disconnects.
It seems that the VPN client runs as a normal application launched by the user - changed user lost connection.

put a tick "Allow all users to use this connection
This checkbox simply enables routing - enables you to use computer as a router.

How do I "share" the connection for remote users ?
Likely to run this app under each user.
Well, users connect to a terminal server, the idea is the user is not changed and operates in parallel.

Likely to run this app under each user.

So as soon as another user connects, the connection breaks. But if say the user is already connected via RDP and run this vpn, then it works and accessible to all. - Austen11 commented on June 5th 19 at 21:23
June 5th 19 at 21:22
You need to run this client as a system service (with the launch, most likely on behalf of NT AUTHORITY\NETWORK SERVICE) then it should work regardless of connections over RDP.
Tried, but could not start service error 1067 - Austen11 commented on June 5th 19 at 21:25
Then enable logging on and to understand why dropping. - Austen11 commented on June 5th 19 at 21:28

Find more questions by tags Windows ServerVPNRDP