DaviesJ
Contributor
Contributor

View 5 PCOIP Experiencing Black Screen

Jump to solution

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

[2011-Dec-28 12:36:03.771304]: Connected to PCoIP server
[2011-Dec-28 12:36:05.303531]: SSL handshake completed with PCoIP client
[2011-Dec-28 12:36:05.332828]: Setup a PCoIP client to server UDP tunnel [1903182396-0]: 10.10.50.50:4172
[2011-Dec-28 12:36:05.332828]: Setup a PCoIP server to client UDP tunnel [1218755094-0]: 0.0.0.0:4172
[2011-Dec-28 12:36:05.367007]: 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-28 12:36:06.336734]: 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-28 12:36:09.805484]: header received
[2011-Dec-28 12:36:09.805484]: PCOIP-SG/1.0
[2011-Dec-28 12:36:09.805484]: XML
[2011-Dec-28 12:36:09.805484]: PSGC27-1781
[2011-Dec-28 12:36:09.805484]: 93
[2011-Dec-28 12:36:09.805484]: xml received 93 93
[2011-Dec-28 12:36:09.805484]: Received command: get-counters

Justin

0 Kudos
1 Solution

Accepted Solutions
gunnarb
Expert
Expert

That's definately not the right display driver.

Have you tried the simple solution of uninstalling hte agent, unintsall Vmware tools, then reinstall Tools, then reinstall Agent.

In that exact order.  Based on your screenshot you could have just had a driver get stepped on by something else.

Gunnar

Gunnar Berger http://www.gunnarberger.com http://www.endusercomputing.com

View solution in original post

0 Kudos
21 Replies
lirick
VMware Employee
VMware Employee

Before futher discussion, can you please check if vRAM is set correctly to your pools?  please take below steps to see if the issue still exist:

1) From Admin UI, editing your pool and Change display settings, enlarge vRAM for 3D enabled pool, or change monitors and max resolution for 3D disabled pool.

2) Oberserve from vSphere console, after the desktop is reconfigured two times, check vRAM on video card

3) Power off then power on the desktop

4) Setup pcoip session again

admin
Immortal
Immortal

Hi,

          Check the following information http://communities.vmware.com/thread/336389

Hope this information.

__________________
Im a nobody.. nobodys perfect.. therefore IM PERFECT!!! http://imagicon.info/cat/5-59/vbulletin-smile.gif

0 Kudos
DaviesJ
Contributor
Contributor

Thanks Lirick,

I have made made those changes and observed the tasks running in vcenter. After powering off / on the vms and attempting the pcoip connection, I am still experiencing the same issues.

Memory changes made to the pool were reflected in the config of the virtual desktops.

Cheers

0 Kudos
DaviesJ
Contributor
Contributor

Thank 1qaz,

I have seen that post and it does not seem to be related to what I am experiencing. I am unable to even successfully load a desktop internally utilising pcoip.

To take any firewall issues out of the way, I have placed the connection server, vcenter and desktops on the same subnet (all whilst trying to access a desktop session from a vm on the same network via the view client)

0 Kudos
lirick
VMware Employee
VMware Employee

Have you tried by connecting Broker directly(not via security server in vLAN)?

0 Kudos
DaviesJ
Contributor
Contributor

Are you referring to uncheck the secure tunnel on the connection server and attempting an internal connection? if so, then yes, same issue...

I have attempted connections via the security server and also directly to the connection server.

Cheers

0 Kudos
vKim33
Contributor
Contributor

I am getting the exact same error.  Please post any resolution.

0 Kudos
rvversendaal
Contributor
Contributor

Hi All,

I'm also having the black screen on pcoip only and 10 seconds later it disconnects. (in view 4.6 on esx 4.1.) All my old clones work fine, but the recently updated snapshots with new windows updates are having this issue. Port 4172 isn't open on the new clones...

0 Kudos
DaviesJ
Contributor
Contributor

Still investigating this. Perhaps this issue is the video driver version. When I try to upgrade the driver to version 2 of the svga driver, I am unable to locate it. The driver currently in use is from 2006. Looking at other threads (http://communities.vmware.com/thread/272320) this should be a lot more recent.

This environment is on vSphere 5 with the latest tools and hardware version 8. Common Files\vmware]drivers only has the 3d drivers

Clipboard02.jpg

0 Kudos
briandatamatter
Contributor
Contributor

I am experiencing the exact same problem.

Anyone ?

0 Kudos
gunnarb
Expert
Expert

That's definately not the right display driver.

Have you tried the simple solution of uninstalling hte agent, unintsall Vmware tools, then reinstall Tools, then reinstall Agent.

In that exact order.  Based on your screenshot you could have just had a driver get stepped on by something else.

Gunnar

Gunnar Berger http://www.gunnarberger.com http://www.endusercomputing.com
0 Kudos
DaviesJ
Contributor
Contributor

Thanks Gunnar,

Problem solved. Appreceiate everyones assistance on this.

Justin

0 Kudos
gunnarb
Expert
Expert

what was the final solution?

Gunnar Berger http://www.gunnarberger.com http://www.endusercomputing.com
0 Kudos
DaviesJ
Contributor
Contributor

Sorry, it was your last suggestion to remove the agent, tools and reinstall Tools then agent

Cheers

Justin

0 Kudos
jwasden
Contributor
Contributor

I am seeing similar issues.

Win 7 desktops

loaded tools, rebooted, loaded 5.0 agent

Verified 3d video driver

We are using Cisco thin  clients. User logs into the session, see the desktop and clicks to  connect. After a series of blinks on the monitor and a black screen the  thin client goes back to the conenction server login screen. I also  found that if I go into vcenter and connect to the console of the VM and  click CTRL + ALT + DELETE for the user, they thin client logs in  without any issues. It is almost like the control + alt + delete is not  getting passed to the VM from the thin client.

On the same pool, I can connect using the View client  from a Windows host and it logs in with no issues without the CTRL +ALT +  DELETE "fix".

I am not exactly sure what is causing this but it seems to only cause issues with the thin clients.

JW

0 Kudos
gunnarb
Expert
Expert

Do you mean the Cisco Zero Clients? Chances are you do. If so make sure you are on the latest firmware currently 3.5. if you are please send me your pcoip server logs and the log from the zero client. It sounds like a svga driver reset issue.

Gunnar Berger http://www.gunnarberger.com http://www.endusercomputing.com
0 Kudos
jwasden
Contributor
Contributor

Yes, they are the 2211 series clients. I will check the firmware when I get back to the office. Is there a known issue with earlier versions or with the svga driver reset? Like I said, the weird thing is that if I send the CTRL +ALT + DELETE from the console and then have them login it works...

Thanks for the info.

Justin

0 Kudos
gunnarb
Expert
Expert

the svga driver reset has been an issue from day one. In each firmware release Teradici works to mask the issue. In each new version of View VMware works to improve the svga driver.

One thing that you need to do is make sure your are using a DVI cable all the way. No converters to VGA. This will help.

Gunnar

Gunnar Berger http://www.gunnarberger.com http://www.endusercomputing.com
0 Kudos
gunnarb
Expert
Expert

If you need more help with your Cisco issue can you open a new thread, this thread has been resolved and it helps googlers if the threads stay on subject.

Gunnar

Gunnar Berger http://www.gunnarberger.com http://www.endusercomputing.com
0 Kudos