VMware Horizon Community
mlaggis2
Contributor
Contributor

PCOIP Black Screen on LAN-Works on WAN

I have a strange thing occuring.  I currently have setup in my lab a View 5 environment.

* ESX 5

*vCenter 5

* Composer 2.7

* View Connection Broker- View 5, Server 2008R2

*View Security Server- View 5, Server 2008R2

*Windows 7 Golden Image- Hardware ver 8, Latest Win7 optimization script support Persona Management

When I try connecting to the internal view manager, I am able to log in and select my desktop.  I initiate a conncetion using PCOIP I get the Black screen and a message that my connection timed out rather quickly.  If I come from the WAN and hit the security server using PCOIP it works fine.  I have tried the following

Golden Image

* Removed agent, removed VMTools, Installed  VMTools then View agent multiple times.

* Verified that the windows firewall is turned off

*Built an entirerly new golden image with just windows patches, vmtools, and view agent.

Connection Broker

*Verified that windows firewall was turned off

*Applied all windows patches

I can connect from internal via RDP without a problem.  Any thoughts?

Tags (2)
0 Kudos
6 Replies
Linjo
Leadership
Leadership

What is your "PCoIP External URL" set to and can you resolve it properly when coming from the inside?

// Linjo

Best regards, Linjo Please follow me on twitter: @viewgeek If you find this information useful, please award points for "correct" or "helpful".
0 Kudos
mlaggis2
Contributor
Contributor

On the connection server it is set to the fqdn of the server

https://viewmgr01.domain.local:443

0 Kudos
markbenson
VMware Employee
VMware Employee

mlaggis2 wrote:

On the connection server it is set to the fqdn of the server

https://viewmgr01.domain.local:443

That can't be the case. The PCoIP External URL can only have an IP address not a name. The value you give here is probably the "External URL".

What is the "PCoIP External URL" set to? It should be set to the IP address of the Connection Server. It is better to use a different Connection Server for internal/external otherwise you unnecessarily gateway PCoIP for internal users.

A black screen with PCoIP to a virtual desktop that works in some cases and not others is caused by PCoIP protocol being blocked somewhere.

This article describes the setup for supporting internal and external PCoIP access. Others who have followed this have resolved black screen issues that you describe.

Check the thre setup steps and make sure you are running with Server 2008 R2 everywhere where you require PCoIP gatewaying.

Mark.

0 Kudos
mlaggis2
Contributor
Contributor

On my connection broker the Http(S) Secure tunnel is set to

https://viewmgr01.domain.local:443  (internal connections)

the PCOIP Secure Gateway is set to

ip_address:4172

On the security server configuration I am set to the following

External URL: https://mydomain.com:443

PCOIP Gateway:

ip_address:4172

yes I am using 2008 R2 SP1 on all view servers.  The strange thing is that through the security server I can connect via PCOIP.  On the LAN I get the black screen and quckly get connectioni timed out.

0 Kudos
markbenson
VMware Employee
VMware Employee

Thanks for the update. When you say ip_address:4172, is that the IP address of the Connection Server? Is there just one Connection Server in your setup?

Go through the referenced doc very carefully and if necessary use wireshark on your View client to see where/why PCoIP is being blocked or misrouted etc.

Let us know.

Mark.

0 Kudos
gunnarb
Expert
Expert

Can you do a quick Visio of your network with IPs in it?  One possibility is that you are NATing internally and, as Mark said, PCoIP is blocked.

ALso, in agreement with Mark, you really should have a second VCS for internal users so they aren't tunneled.

Gunnar

Gunnar Berger http://www.gunnarberger.com http://www.endusercomputing.com
0 Kudos