VMware Horizon Community
mekmiotek
Contributor
Contributor

Black screen of death over PCoIP

Hello,

We are in the process of deploying View 5 to a subset of users in our organization.

We have 2 security servers in the DMZ , RSA integration enabled.

Those 2 security servers are paired with 2 connection managers, dedicated to external users.

We have 2 more connection managers dedicated to internal users.

When users come in externally using the RDP proto, all is good.

When users come in internally using RDP proto, all is good.

When users come in internally using PCoIP proto, all is good.

When users come in externally using the PCoIP proto, .....not so good, this is where we get the black screen.

We have been chasing this for days now. We have opened a ticket with Vmware support, but I thought I would throw it out here also.

We believe we have all required ports open, screen reso is set to minimum on desktops, and external URL and pcoip settings are all in place on security and connection servers. I think I've read every KB and forum post relating to this problem ,and believe me there are ALOT!

SSL certs are installed.

Couple questions....If the Certs are wrong for some reason, can that cause the black screen specifically over pcoip?

Here is a snippet from the pcoip secure gateway log, this was when I tried to connect without using https:

[2011-Dec-15 13:01:55.937226]: PCOIP-SG/1.0
[2011-Dec-15 13:01:55.937226]: XML
[2011-Dec-15 13:01:55.937226]: FE2DE7CCD3B30AA4FB5C8AD88C0B4B38-0
[2011-Dec-15 13:01:55.937226]: 358
[2011-Dec-15 13:01:55.937226]: xml received 358 358
[2011-Dec-15 13:01:55.937226]: Received command: add-connection
[2011-Dec-15 13:01:55.937226]: Parameter: connection-id Value: FE2DE7CCD3B30AA4FB5C8AD88C0B4B38/port1
[2011-Dec-15 13:01:55.937226]: Parameter: ctag Value: SCS1d9u3/gKIjl6u9rXSLvEvpODGACQ6uXl651MJG4GrYSdd99HZ4Sy9rqnUIw8tuXCRSW4K0CA6VyoE7tzGaWS9z0jOfDmZz9futx/L
[2011-Dec-15 13:01:55.937226]: Parameter: ip-address Value: 172.16.13.187
[2011-Dec-15 13:01:55.937226]: Parameter: tcp-port Value: 4172
[2011-Dec-15 13:01:55.952851]: Connected to PCoIP server
[2011-Dec-15 13:01:56.946992]: SSL handshake completed with PCoIP client
[2011-Dec-15 13:01:56.970429]: Setup a PCoIP client to server UDP tunnel [2010569261-0]: 172.16.13.187:4172
[2011-Dec-15 13:01:56.970429]: Setup a PCoIP server to client UDP tunnel [211693589-0]: 0.0.0.0:4172
[2011-Dec-15 13:01:56.995820]: SSIG client connection error while reading SSIG APDU header: A request to send or receive data was disallowed because the socket had already been shut down in that direction with a previous shutdown call
[2011-Dec-15 13:01:57.924531]: Error reading SSIG header from PCoIP server: A request to send or receive data was disallowed because the socket had already been shut down in that direction with a previous shutdown call

[2011-Dec-15 13:02:23.409882]: header received
[2011-Dec-15 13:02:23.409882]: PCOIP-SG/1.0
[2011-Dec-15 13:02:23.409882]: XML
[2011-Dec-15 13:02:23.409882]: PSGC27-6
[2011-Dec-15 13:02:23.409882]: 93
[2011-Dec-15 13:02:23.409882]: xml received 93 93
[2011-Dec-15 13:02:23.409882]: Received command: get-counters
[2011-Dec-15 13:03:28.421601]: header received

Can anyone shed any light on those errors I highlighted?

Any help would be fantastic!!!

Regards,

MK

0 Kudos
3 Replies
Linjo
Leadership
Leadership

Have you done any changes to the encryption of PCoIP? For the Security Server to work you need to have AES enabled, it can not work with SALSA.

// 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
mekmiotek
Contributor
Contributor

No changes have been made to the encryption, AES is being used.

0 Kudos
mekmiotek
Contributor
Contributor

We found the problem. There was a mis-communication between some of the groups(data security and networking)..the external NAT was not setup  or setup correctly. They fixed that and everything is working great.

Regards,

0 Kudos