Black screen but security team says PCOIP is not being blocked

[kappyninewood]

So when I connect to desktops, I get the black screen, but it doesn't time out like your normally see when PCOIP is being blocked instead it just sits there. When I change it from PCOIP to RDP  on the View client I'm able to get in.  The security team says PCOIP is not being blocked???  What else could it be??

[markbenson]

Is this with remote access through a View Security Server? Does it work when you connect internally?

If so, you'll be able to resolve this with the 3 steps here - http://communities.vmware.com/docs/DOC-14974

The security team might be right. The firewall rules part is just one of the 3 steps required. Check the other 2 steps as well as they are also required to avoid the PCoIP Black Screen problem.

Also, make sure the security team know the exact PCoIP rules required in case they have missed some of them.

Post again to let us know what it was.

Mark

[vmwaredirectory]

Check out the Troublshooting PCoIP articles. Let me know if it helped.

http://vmwaredirectory.com/index.php?option=com_mtree&task=listcats&cat_id=251&Itemid=469

Regards

Manfred

Http://Vmwaredirectory.com

[kappyninewood]

No it is not going through a security server. This is happening internal. I will try those steps and report back  What about the fact that we never get the disconnect, but instead it just sits there on the black screen?.

[vmwaredirectory]

I experienced the same issue many times with older versions of view.

You will find listings on my Website, like what ports are used or other tips to get your problem solved.

Just browse the view categories...

Hope it helps. It's an annoying problem. I had to switch to RDP several times.

Manfred

[BRumer0]

Just wanted to chime in here. You did check to make sure you installed VMWare tools first, then the View agent, right? Ive seen this black screen happen over PCOIP but not RDP because of the order the vm software is installed on the client...

[EHYates]

You need to go take a look at your display settings.  Make sure sleep is completely disabled, disable all power management, disable turn off display after, etc.

[kappyninewood]

Turns out it was caused by my AV scanning...long story.

[cmartin24]

I'd be interested in hearing the long story.

[vcpguy]

I am interested too. Need to know how you came to AV is a issue here.