- CheckMates
- :
- Products
- :
- Quantum
- :
- Remote Access VPN
- :
- ATM VPN
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Are you a member of CheckMates?
×- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
ATM VPN
Hello,
I’m trying to configure a VPN between an ATM and a Security Gateway (SG). The VPN agent has already been installed on the ATM.
I’ve updated the `trac.config` file as required, but I am unable to find the Check Point icon to start or check the VPN status. Additionally, I can’t locate the file `C:\Program Files (x86)\CheckPoint\Endpoint Security\UIFramework\Bin\WUI\cptrayWUI.exe`.
Could you suggest troubleshooting steps or any other actions I should try to resolve this issue?
Regards,
- Tags:
- VPN ATM
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The exact steps will depend on the authentication requirements, but it should work more or less the same as doing it in a GUI.
Note that the CLI does not support SAML-based authentication, which requires a web browser (which is not appropriate for "headless" ATM usage).
But, in general, you will create a site first: https://sc1.checkpoint.com/documents/RemoteAccessClients_forWindows_AdminGuide/Content/Topics-RA-VPN...
If you're doing certificate-based authentication, you'll need to enroll a certificate with one of:
- CAPI: https://sc1.checkpoint.com/documents/RemoteAccessClients_forWindows_AdminGuide/Content/Topics-RA-VPN...
- p12 File: https://sc1.checkpoint.com/documents/RemoteAccessClients_forWindows_AdminGuide/Content/Topics-RA-VPN...
Then connect: https://sc1.checkpoint.com/documents/RemoteAccessClients_forWindows_AdminGuide/Content/Topics-RA-VPN...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The ATM version of the client is controlled entirely via CLI: https://sc1.checkpoint.com/documents/RemoteAccessClients_forWindows_AdminGuide/Content/Topics-RA-VPN...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thank you for your response. Would you be able to share an example of a configuration script or outline the steps to follow? This is my first time setting this up, and while I have reviewed the documentation, I suspect I may have missed something.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The exact steps will depend on the authentication requirements, but it should work more or less the same as doing it in a GUI.
Note that the CLI does not support SAML-based authentication, which requires a web browser (which is not appropriate for "headless" ATM usage).
But, in general, you will create a site first: https://sc1.checkpoint.com/documents/RemoteAccessClients_forWindows_AdminGuide/Content/Topics-RA-VPN...
If you're doing certificate-based authentication, you'll need to enroll a certificate with one of:
- CAPI: https://sc1.checkpoint.com/documents/RemoteAccessClients_forWindows_AdminGuide/Content/Topics-RA-VPN...
- p12 File: https://sc1.checkpoint.com/documents/RemoteAccessClients_forWindows_AdminGuide/Content/Topics-RA-VPN...
Then connect: https://sc1.checkpoint.com/documents/RemoteAccessClients_forWindows_AdminGuide/Content/Topics-RA-VPN...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I have a VPN established between an ATM and a Check Point firewall. The ATM operates with two user sessions: Administrator and Normal User. While the VPN functions correctly in the Administrator session, it requires manual reconnection every time when accessed by the Normal User. How can I resolve this issue to ensure the VPN remains active for the Normal User without requiring repeated manual reconnections?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Are you switching users on the same system?
The Remote Access connection is tied to the user, generally speaking.
Which means if you log out as one user and log in as a different one, the VPN connection will drop.
If you want the VPN to remain active regardless of user, use a Machine Certificate for authentication: https://sc1.checkpoint.com/documents/R81.20/WebAdminGuides/EN/CP_R81.20_RemoteAccessVPN_AdminGuide/C...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The configuration was set up in the Administrator account, and the VPN works perfectly. However, after rebooting the machine, the default user account cannot connect to the VPN automatically. If we reconnect manually, it works. How can this issue be resolved?
