VMware Horizon Community
7 Replies
chrischay
Contributor
Contributor

Hi RLillicrap_SA,

Did you get an answer on this, or were you able to resolved it? Can you please share how you fix it?

I'm getting the same issues.

Thanks,

smoustaquim
Contributor
Contributor

hello

any update, i have the same prob with internal and external user only with web client.

horizon view client "Your session has expired. Please re-connect the server" 

i change global session settings in horiozon console but no change.

Reply
0 Kudos
cerbadmins
Contributor
Contributor

We are experiencing the same problem, seems to only happen when trying to authenticate to the loadbalancer VIP url of Horizon web console.  

Reply
0 Kudos
SurajRoy
Enthusiast
Enthusiast

This issue can be seen mostly if the initial connection is going through Load Balancer to VIP.

If the connection is made directly to the Connection server IP / FQDN or UAG IP, it work fine.

Lets understand:

  • The client sent "Last User Activity" parodically to the connection sever after specific set of time.
  • Assume the LB as session timeout of 15 mins and Connection server or UAGs are being Load balanced.
  • Client made Connection VIP and request goes to UAG1 or Connection Server1.
  • After 15 mins, LB session timeout happened.
  • At 25th min client send last user activity or heart beat to VIP. This time VIP re-route to Connection server2.
  • Connection server 2 is not aware of the initial session and say, session expired.


Please give kudos if it help
https://www.surajroy.com/

 

Reply
0 Kudos
garfield51
Contributor
Contributor

We had this issue on our html websessions.  This impacted both internal and external users.   The fix for us was setting a Persistence Timeout of 8-12 hours, and additionally using the Horizon GPO bundle and setting the session timeout for 8-12 hours to match.   Hope this helps someone.  We also researched using XFF headers to keep the communication to the host Horizon server clean so the traffic didn't go to the wrong server.   See the yellow note at the top of this article- Dashboard alerts for unrecognized requests for XML Api protocol connection in Horizon 2209 (8.7) (90...

That issue happens with load balancers on ANY version of Horizon, not just 2209-2212.

 

For later versions of Horizon be sure to set the Locked.Properties file to your load balancer and server name using portalHost entry.

Reply
0 Kudos
kennyvz
Enthusiast
Enthusiast

Hi @garfield51, would you mind clarifying which settings you mean please?

"The fix for us was setting a Persistence Timeout of 8-12 hours"

Is that Horizon Admin Console -> Settings -> Global Settings -> Forcibly Disconnect Users setting?

"and additionally using the Horizon GPO bundle and setting the session timeout for 8-12 hours to match"

Is this a GPO set on the VM and the setting: Computer Configuration -> Administrative Templates -> VMware View Agent Configuration/Agent Configuration -> Idle Time Until Disconnect (VDI) or something else?

Much appreciated!

Reply
0 Kudos