VMware View 5 PCoIP get black screen over WAN

[freddieeichmann]

Hello Community,

i got a VMware View 5 Infrastructure with a vCenter Server, a View connectionserver and some clients as VMs.

Internally everything is working fine - PCoIP and RDP connections do their job very well.

Know we want to publish the vDesktops to the WAN. Users should connect to the VMs from their notebooks or iPads (or iPhones) from home. So we configured our firewall to open everything from the WAN-IP (194.209.166.xy) to the internal-IP (192.168.199.xy). A DNS-Entry for view.xy.com is showing to the WAN-IP. So the connection from WAN to the view-infrastructure over RDP is working - but PCoIP connections will show a black screen after 10-30 seconds after logon. We never see a Windows interuption oder interaction. The screen is black after the logoninformations in view client.

We configured the view connectionserver settings as described in some articles here ...7

HTTPS external url: https://view.xy.com

checkbox activ: user secure tunnel connection to desktop

PCoIP external url: 194.209.166.xy:4172

checkbox activ: use pcoip secure gateway for pcoip connections to desktop

Does we forgot to do some settings or is there an other workaround to work with PCoIP over the WAN?

Regards,

Freddie

[Sreejesh_D]

welcome to this community!!

here's a KB from VMware which discuss common root causes on black screen issue with PCoIP.

http://kb.vmware.com/kb/1028332

[Sreejesh_D]

go through this KB as well, though it addresses only 4.0.x.

http://kb.vmware.com/kb/1016753

[markbenson]

freddieeichmann wrote:

Did we forget to do some settings or is there an other workaround to work with PCoIP over the WAN?

Regards,

Freddie

This is a common problem and others who experience this fix it by carefully following the three steps here http://communities.vmware.com/docs/DOC-14974

If any of the steps are missed, then with PCoIP over the WAN you'll just get a black screen for a few seconds and the connection will drop.

Mark

[freddieeichmann]

Thank you for the response...

is it possible to setup the connection wihtout a security server or is it essential to have a security server?

[markbenson]

Security Server is optional, but recommended for remote access.

See http://communities.vmware.com/docs/DOC-14974

Mark

[freddieeichmann]

Thank you Mark for your response. Know I've installed a security-server in the dmz. Does I publish the Security-Server for connecting to the view-Infrastructure from WAN?

[markbenson · Accepted solution]

Go through the video linked from the above article. It describes exactly the setup you are working on. If you then have any questions about this, let us know and someone on this forum will help you out.

Mark.

[freddieeichmann]

Dear Mark,

got still some issues with PCoIP over WAN. My Lab looks like this:

194.209.x.y is the WAN-IP for view.company.ch

194.209.x.y is NAT to 10.0.2.60 (all Ports i.e. 443, 4172 (TCP, UDP) are opened)

10.0.2.60 is the IP from the VMware View Securityserver.

10.0.2.3 is the IP from the TMG-Server (outside interface).

192.168.199.2 is the IP from the TMG-Server (inside interface).

192.168.199.60 is the IP from the VMware View Connectionserver.

On the TMG-Server I got a firewallpolicy that enables the connection from 10.0.2.0/24 to 192.168.199.0/24 (all outgoing Ports). A Ping from View Securityserver to View Connectionserver is ok.

If I connect from WAN to view.company.ch over View Client through RDP everything is working fine.

If i connect from WAN to view.company.ch over View Client through PCoIP I got a blackscreen.

I don't know wheres the issue - all firewalls are correct configured - I think so.

Is it possible theres a configurationfailure at the 'PCoIP External URL' or the 'PCoIP Secure Gateway' Setting?

Regards,

Freddie

[freddieeichmann]

Hello Mark,

thank you a lot for the blogentry and the fantastic video....got found the issue....it was the dns entry on the view security server.

regards

freddie

[markbenson]

I'm glad it was simple and you got it up and running. Thanks for posting back what it was. It helps others.

Mark.