I have a scenario whereby I need to offer an on-demand VPN solution to untrusted endpoints as well as an always-on solution for my trusted endpoints. Running through guides I have been able to run a pre-logon VPN that has successfully allowed me to authenticate the workstation then make use of User-ID to identify and allow users into the network based on various rules however I need to also offer an on-demand function that will allow staff using untrusted endpoints to connect to the network and access a very restricted set of resources.
If anyone has done this or knows the methodology then please do let me know
Thanks - the issue that I have will be the endpoint that the user connects from rather than the users themselves. they should be able to connect pre-logon from their corporate laptop but if they work from home on a non-corp device they should be able to use GP on-demand to gain access to a second restricted network that only permits them access to an RDS server
I'm trying to make a similar configuration but I haven't been able, I tried HULK method but the problem is that for the config I need, the same user should have the ability to have an always on connection for the internal gateway and an on-demand connection for external gateways. No luck so far ... Any advice?
You may create another portal and GW and allow users changing portal address on their GP agents. To avoid certificate issues, I would deploy this new portal using the same address but a different TCP port than default (443). To do this, a loopback interface can be used to support the GP portal and a NAT policy should be implemented to redirect traffic to the loopback interface on port 443.
Regarding internal trusted computers and external untrusted computers:
You may be able to use DNS to help if your internal DNS is separate from your Internet facing DNS.
Have two gateways with different IP's. One is prelogin (.1 for this example) and the other on-demand (.2)
Use one name in the client (ex. connect.xyz.com)
Internal DNS resolves connect.xyz.com to the .1 IP and users connect prelogon.
External untrusted users:
External DNS resolves connect.xyz.com to the .2 IP and users connect on demand. (assuming this doesn't use certificates for authentication)
Or, have a totally separate name and IP for external users to connect to.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!