Attempting to connect to a VMware Horizon View online desktop computer from outside throws the error: “The display screen protocol for this desktop is presently not easily accessible. Please contact your mechanism administrator.”


Problem

You attempt to affix to a virtual desktop from the internet via the VMware View Horizon Client which passes the traffic to VMware Horizon View Security server which then contacts the View Connection server which then attempts to develop a connection to the VDI however falls short with the complying with message:

The screen protocol for this desktop is currently not obtainable. Please contact your mechanism administrator.

You are watching: The display protocol for this desktop is currently not available

*

Solution

While tbelow are assorted factors why this error would be thrown, among them is if your View Connection server has a stale DNS entry to the digital desktop computer. A client newly contacted me to troubleshoot this error message and also what the problem ended as much as be was that the digital desktops were changed to another port group and also while the DNS entries were updated on the domain controllers in the very same Active Directory site, the View Connection servers were using DNS servers from a different Active Directory Site so the alters to the DNS entries were not instantly available leading to this error to be thrown.


Posted byTerence Lukat3:09 PM
*

*

Chinnasassist...

Dear Luk, We have correct DNS record on all DC's, yet still getting the exact same. Could you please carry out the all the common scenarios to cause this worry. Also i desire to upday one thing is, we have enabled 2 various ports from firewall to access the VDI's from Web. From this minute we started receiving this kind of situations.I'm not certain whether this configuration causing the concern or not, if yes please imply how can we deal with it. Thanks in breakthrough.

May 11, 2020 at 7:00 AM
*

Anonymoussassist...

See more: Why Does My Youtube Look Weird, Youtube Looks Weird In Chrome

Restart Deskpeak fixed the trouble for me.