when you are unable to connect to View desktops using PCoIP:
- Confirm that the virtual desktop has a network connection. For more information, see Increasing the number of ports assigned to a VMware View virtual switch (1026014).
- Confirm that the proper ports are open within the guest operating system. For more information, see Confirming that correct TCP/IP ports are open on a VMware Horizon View Virtual Desktop (1026766).
- Confirm that there are no disclaimers or login banners used when PCoIP is the display protocol. For more information, see Black View Client log in screen when using PCoIP (1016961).
- Confirm that an available desktop or desktop pool exists. For more information, see Confirming if a desktop pool exists (1026771).
- Confirm that the network in the virtual desktop's guest operating system is configured correctly. For more information, see Network configuration in VMware View desktops (1026498).
- Confirm that the virtual desktops are configured with enough video RAM to display the resolution required by the client. For more information, see Creating View desktops causes the vCenter Server error: The operation is not supported on the object (1017380).
- Confirm that VMware Tools and the VMware View agent are installed in the correct order. For more information, see Configuring PCoIP for use with View Manager (1018158).
- Confirm that the SmartCard authentication is configured and is functioning properly. For more information, see:
There are three
protocols used by clients for accessing virtual desktops. Those protocols
are:
·
HTTPS – HTTPS (port 443) is used by Horizon clients to handle user
authentication and the initial communications with the Connection or Security
server.
·
HTTP – HTTP(Port 80) is also used by Horizon clients to handle user
authentication and the initial communications with the Connection Server
·
PCoIP – PCoIP (port 4172) is the remote display protocol that is
used between the Horizon Client and the remote desktop.
·
Blast – Blast (port 8443) is the remote display protocol used by
HTML5-compatible web browsers.
Display Protocol or Black Screen Error will come when
there is firewall issues are there. You can check this by telnet 4172.
Once you have Verified in client side you able ping
connection server IP and FQDN and also able to Telnet Ports 80(http), 443(https),
4172(PCoIP). You need to verify in backend
Check status in Connection Server Web
Option 1
Protocol Failure
If you see Service VMware Blast is started. May be somewhere
port is blocking. Do a restart I will resolve this issue.
Option 2
User says not able to connect and in web console you see
as connected, some connection conflict is happening.
When I open Console I do see session as connected from VM console status
So I need to close session from Backend and open it again
from Front end.
Right Click on particular desktop and click on Disconnect
Session..
Click ok
Once it’s disconnected, ask user to connect
Connection should establish now, if it’s not working try last
option save session Doc and Excel and Logoff or Restart and then check in
connection server web status. Once it becomes available ask user to connect. It
will work.
Option 3
If you see display Protocol Error in Client and View web
console you see
When I open a console I see everything looks fine
Some time with any apps or system Explorer.exe will
become non responsive. In this case either you can login via user credentials and
open task managers and open New Task
Type explorer.exe
Click OK
Lock the screen and ask user to try again. If it’s not
working save session Doc and Excel and Logoff or Restart and then check in
connection server web status. Once it becomes available ask user to connect. It
will work.
Option 4
If user says I don’t have any Document or any other thing
that will not impact on reboot, you can do reset from web console or Restart
from vSphere Client
Reset from WEb Console Driectly
Restart Guest OS from vCenter
Comments
Post a Comment