Hi All,
I am experiencing the much discussed Black screen while trying to access a desktop session via PCOIP. RDP connections work fine. I have followed ( I believe) the document referring to the 3 steps to rectify this issue with no luck. I am unable to get connections via PCOIP working correctly via the connection server (internal) or security server (external)
Any assistance would be appreciated. Setup is as follows
1 VC (vsphere 5)
1 Connection server - view 5 install (windows firewall disabled)
1 Security Server - View 5 install (windows firewall disabled)
Windows 7 virtual desktops (windows firewalls disabled)
Connection Server Config
HTTPS Secure Tunnel is configured with the URL for the Connection server with the connection to desktop enabled
PCOIP Gateway is configured with the Connecting Server IP address with this Use secure gateway for pcoip desktop connections checked
Security Server Config
HTTPS Secure Tunnel is configured with the externally connectable URL
PCOIP External Gateway is configured with the Externally connectable IP Address (same IP as what the url for the above secure tunnel resolves to)
While trying to connect to pcoip session from the LAN, receive a black screen for approximately 10 seconds then a disconnect with no error.
While trying to connect via external., the same behavior occurs.
To assist with the trouble-shooting of this issue, I have allowed all traffic between subnets. I am not seeing any packets being dropped via the firewalls.
Cheers
Log on the security server (PCOIP Secure Gateway logs) have the following entry
Justin
The problem I experienced had to do with the PCoIP protocol that needed to be manually defined on our firewalls. Once the source port for 4172 UDP/TCP was set to dynamic 1 to 65535 we were able to connect via PCoIP.
Hopefully this will save you hours of troubleshooting.
Thanks for posting. In general it is very dangerous to restrict connections based on source port as in most cases source ports are dynamically allocated.
Most causes of PCoIP black screen are because the firewall has been setup to block it. That was your case too.
Mark