I have one portal and 3 Gateways. I set up a preferred gateway at HIGHEST based on an active directory group so users connect to their home office. When using Pre-logon since the user is a shared account the connection on a reboot seems to always find the closest gateway. This is OK but when my users log in they stay on that gateway until we refresh the connection. After the manual refresh, the preferred gateway is found and if the user logs off they are still using preferred up until a reboot. The only way I can think to fix this is to have a new portal for each site that sets a preferred gateway for pre-logon. Any thoughts or suggestions?
I experienced the same issue. This post was helpful thank you for sharing. One other issue I am running into that I configured my Portal and Gateway with different Public IP addresses in the same subnet on the same LAG, the switch between pre-login and the named tunnels takes up to two minutes, it does work and but takes too long. If I change the config so that that external Portal and Gateway are on the same IP the change is very quick. This happens both for Log off and logon. The users notice is at logon because until the tunnel rename they are subject to pre-logon policy.
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!