External Load Balancer (PCoIP)

[JonathanMcDowel]

I have an external load balancer that is working fine for RDP session but not for PCoIP. I am gettting the typical black screen then that the session has ended. I had our external address point striaght to each security server and tested PCoIP and it worked fine. For the load balancer I am using http://vmtoday.com/2012/09/free-vmware-view-load-balancer-using-suse-studio-and-haproxy/. I was wondering if anything special has to be added to the haproxy.cfg file or some other change to the load balancer. Also the external URL for the SS and CS are shown below.

SS1 & SS2

External(For LB) URL:443

External(For LB) IP:4172

CS1 & CS2

External(For LB) URL:443

External(For LB) IP:4172

[npeter]

Hi Jonathan,

Welcome to community,

Please refer to this http://communities.vmware.com/docs/DOC-14974 "Setting up PCoIP Remote Access with View 4.6 and Newer"

[espi3030]

I was experiencing the same issue and it was very frustrating.  My resolution was to edit the Virtual Machine's settings, under Video Card > Number of displays 4 (or 2) and Total video memory to 128MB.  Lo and behold my black screen and session disconnect was fixed.  Now I only had this problem when connecting vie PCoIP and not RDP.

Hope this helps.

[markbenson]

No. This problem won't be caused by lack of video memory on the VM. If that was the case, PCoIP wouldn't have worked even when the PCoIP External URL was set to point to each Security Server (as JonathanMcDow… said).

If it was lack of video memory, you'd get a PCoIP black screen in all cases.

External URLs must not be load balanced. These URLs are used by the View Clients to connect to the particular View server (Security Server or Connection Server). This is explained in http://communities.vmware.com/docs/DOC-14974 As has been suggested, following the 3 steps in this article will solve this problem.

Mark