Pages

Wednesday, September 28, 2016

Attempting to connect to VMware Horizon View virtual desktop through the security server throws the error: “Unable to connect to desktop: There is no available gateway for the display protocol. Try again, or contact your administrator if this problem persists.”

Problem

You’ve noticed that the following error is thrown when you attempt to connect to a VMware Horizon View virtual desktop through the security server with the VMware Horizon Client:

Unable to connect to desktop: There is no available gateway for the display protocol. Try again, or contact your administrator if this problem persists.

imageimage

The following information is logged in the events:

Severity: Audit failure

Module: Connection Server

Message: Unable to launch from Pool <desktopPoolName> for user domain\username

More Information: Unable to launch from Pool <desktopPoolName> for user domain\username: No co-management availability for protocol PCoIP

image

Attempting to use the Blast protocol from the View client will present a black screen:

image

image

… then thrown the following error:

The connection to the remote computer ended

image

Attempting to use the browser to login:

image

… will briefly present a triangle and exclamation mark for the desktop:

image

Then display the following error:

An error has occurred: {"code":"ETIMEDOUT","errno":"ETIMEDOUT","syscall":"connect","address":"10.34.30.60","port":22443}

image

Solution

One of the reasons why these errors would be thrown is if the following ports are not opened between the Security servers to the virtual desktops:

  • TCP/UDP 4172
  • TCP 22443
  • TCP 32111
  • UDP 22443
  • TCP 9427

Verify the ports above and all other ports identified in the following KB:

VMware View ports and network connectivity requirements (1027217)
https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1027217

3 comments:

Unknown said...

What do you think if we have multiple pools and we only have the issue on one pool?

Sai said...

I'm having same issue with one particular pool. Rest of them are fine. Also the problematic pool is a dedicated pool and the issue doesn't happen when the user tries to login via RDP. PCOIP is flaky and BLAST never connects.

Michelle Richardson said...

I just have one VM in a Manual Desktop Pool with floating assignment that I have this issue with. There are a total of 6 in the pool and the other 5 are fine. I have uninstalled and reinstalled the view agent and vmware tools and also made sure the network metric bindings were correct. I know that I can blast the VM away and rebuild it, but this has happened on different random VM's in the past so I would like to know how to fix it rather than always having to delete and recreate.