Create a Post
Showing results for 
Search instead for 
Did you mean: 

How to Have Remote Access VPN Tunnel Before User is Logged In

This question has come up on the community previously about how to have a Remote Access VPN configured so the tunnel is "always up" before the user is logged in.

The answer is to use Machine Authentication, which provides a certificate-based authentication mechanism not tied to a specific user.
This requires R80.40 and above.

To have a user-specific tunnel when a user is logged into the same machine, you have to configure multiple authentication schemes (Machine and User Authentication).
The user-specific VPN will replace the machine-specific VPN tunnel when the user is logged in. 
Refer to: 


1 Reply

There is one important part missing. Machine certificate authentication required some changes on the gateway side that are not mentioned in the Client Admin Guide. The referenced SK (valid for EOL versions only) in the Client Admin Guide refers to some registry changes on the CLI which are not necessary as they are condfigured in SmoartConsole now. TAC pointed me into the right direction:

It is especially important to have the machine_certificate realm configured. I did this using GuiDBedit as described on step 6. It also requires a rule with an access role for the machines to get access the required ressources for domain login (DNS, AD, etc).

What I also noticed: the tunnel is disconnected as soon as the user entered his windows credentials and pressed the Enter button. There is no VPN connection until the user starts the VPN client and logs in there. Any logon scripts that are loaded after Windows logon will probably not even be fetched. A delay would be nice to allow such scripts to execute before the machine tunnel being disconnected. 

0 Kudos


Epsum factorial non deposit quid pro quo hic escorol.

Upcoming Events

    CheckMates Events