Connecting to VDI using PCoIP shows a black screen and the disconnect the session

[djfersa]

Hello all,

We are deploying a Horizon View 6.0 solution with Connection and Security Server using an F5 to load balance the services. As to this point of the implementation, pretty everything works except PCoIP connections over WAN, the F5 is working fine with everything so I don't think the issue is there, and the firewalls have rules to permit port 4172 both TCP and UDP. The connection behaviour is like thisÑ

HTML (blast) internal -> WORKS

HTML (blast) external (over wan) -> WORKS

PCoIP (VMware Horizon Client) internal -> WORKS

RDP (VMware Horizon Client) internal -> WORKS

RDP (VMware Horizon Client) external (over wan)-> WORKS

PCoIP (VMware Horizon Client) external (over wan)-> doesn't WORK, show a black screen adn after a minute shows the following message: PCoIP connection failed with error 'The connection to the remote computer ended.'.

I have checked everything and I don't know what else I can do. If someone of you have been througth this I really appreciate your guiadance!

Thanks!

[Linjo]

What is your "external URL" and "PCoIP External URL" set to?

These need to correspond to whatever dns-name and IP the client is using.

Usually this means that you need to setup two connection-brokers, one for internal users and one for external.

// Linjo

[cH1LL1]

I tested exactly the same setup  and had the same issue, - eventually we found we needed the Latest View client installed. then it worked.

The other thing you need to answer is what the F5 is doing with Pcoip traffic from outbound.? offloading at the appliance or forwarding it on ?

-cHiLLi-

[djfersa]

The external URL is remote.mydomain.com and internally resolve as 192.168.1.5 and in internet resolve to a public address we have. On internet via Web (blast) it works pretty smooth, but when I used the client, it only works internally.

I made captures both client and F5 and I'm not seeing any 4172 traffic coming from the internet nor generated in the client, it only opens a black scree that last for almost five seconds and the show an error saying that the remote desktop stops responding.

We already verified teh connections throught the firewallls and all ports are opened, and when I try a telnet in port 4172 to the URL it got connected.

[markbenson]

djfersa wrote:

The external URL is remote.mydomain.com and internally resolve as 192.168.1.5 and in internet resolve to a public address we have. On internet via Web (blast) it works pretty smooth, but when I used the client, it only works internally.

I made captures both client and F5 and I'm not seeing any 4172 traffic coming from the internet nor generated in the client, it only opens a black scree that last for almost five seconds and the show an error saying that the remote desktop stops responding.

We already verified teh connections throught the firewallls and all ports are opened, and when I try a telnet in port 4172 to the URL it got connected.

That's the "External URL", but as Linjo asked - what is the "PCoIP External URL" set to?

This is a common problem - many people have solved with this information. View PCoIP Remote Access Setup. Make sure all 3 steps are done accurately.

Mark

[djfersa]

Hello guys,

I found the issue, it was that the ip address that should be on the PCoIP line in the security server is the public ip address instead of the VIP ip address. This is causing that we will need to set up a new platform for internal access, which I think is a failure in the Horizon View architecture.

Thank you very much for you help!

[markbenson]

Yes, that's the "PCoIP External URL" and it must be set to a value where the IP address is usable by the client (on the Internet) to get to the Security Server or Connection Server. The default value is the internal address of the server and so for remote access, always needs to be changed. That is step 2 in the article (linked above).

Glad you have it working and thanks for posting. Others will benefit too!