Super6VCA Posted October 17 Share Posted October 17 Recently upgraded to 2312.1 and a few of my new pools are getting the error when launching. I can get in fine with HTML and if i connect via the UAG. Any thoughts??? Thank you, Perry Link to comment Share on other sites More sharing options...
Sean Massey-1 Posted October 17 Share Posted October 17 What protocol are you using? Are users on your internal network or external and connecting through a UAG? Sean Massey Independent Consultant/Analyst/Blogger | VCDX-EUC 247 Vice Chairman of the Board - World of EUC Blog: thevirtualhorizon.com Mastodon: @seanpmassey@vmst.io Instagram/Thread: @seanpmassey LI: https://www.linkedin.com/in/seanpmassey/ Link to comment Share on other sites More sharing options...
Super6VCA Posted October 18 Author Share Posted October 18 Tried them all but all the testing is don't internal and not thru UAG. However when i tried thru UAG i get the same error. Just not thru HTML. Thanks for the reply Thank you, Perry Link to comment Share on other sites More sharing options...
Niels Geursen Posted October 18 Share Posted October 18 I have seen the same issue. Our case was that UDP was blocked on the external facing firewall. - are your servers behind a load balancer? - Are all network ports opened in the firewall? Double-check if the UDP port 8443 is not blocked by the firewall. Link to comment Share on other sites More sharing options...
Sean Massey-1 Posted October 18 Share Posted October 18 I agree with @Niels Geursen. This sounds like a network port isn't opened between the client and agent. Is this only happening with the new pools? Or is this happening with existing pools? If it's just new pools, has anything changed in your network architecture such as adding a new subnet for the new desktops? 1 Sean Massey Independent Consultant/Analyst/Blogger | VCDX-EUC 247 Vice Chairman of the Board - World of EUC Blog: thevirtualhorizon.com Mastodon: @seanpmassey@vmst.io Instagram/Thread: @seanpmassey LI: https://www.linkedin.com/in/seanpmassey/ Link to comment Share on other sites More sharing options...
Employee Victor León Posted October 18 Employee Share Posted October 18 Hello, What are your Connection Server settings? Is Blast Secure Gateway enabled? If HTML works but fails with client, I suspect that you enabled 'Blast Secure Gateway for HTML access only' in the CS settings. Therefore the connection flow is different. with client it is: Client > 22443 > Agent with HTML it is Client> 8443 > Connection Server > 22443 > Agent. It is very likely that you are missing a firewall rule between client-Agent. Source: 'any' or client endpoint IP range. Destination: VDI desktop (agent) Port: 22443 Link to comment Share on other sites More sharing options...
Employee Graeme Gordon Posted October 21 Employee Share Posted October 21 As @Victor León says, i would check the config on your Connection Servers to make sure Blast Secure Gateway is not enabled. I normally default to using the Enable the Blast Secure Gateway for HTML Access option. See https://techzone.omnissa.com/resource/understand-and-troubleshoot-horizon-connections#configuration for more information on this. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now