Meyner22: Thanks for responding. At first, I performed an in-place upgrade of the View Agent in my Parent Virtual Machine from 4.6.0 to 5.2.0. When that failed (externally, internal PCoIP works) I build a brand new Windows 7 PVM with a fresh install of the View 5.2.0 Agent. I tried having the Windows Firewall Service started with profiles disabled, as well as the Windows Firewall Service started with profiles enabled, before installing the View 5.2.0 Agent. I then skipped all Windows 7 optimization scripts and put the new pool in a new Active Directory OU with no Group Policies. No luck. External/WAN PCoIP connections fail. If I downgrade to the View 5.1.3 Agent (uninstall, reboot, install), external/WAN PCoIP connections work.
Markbenson: Thanks for sticking with me.
I agree. If external/WAN PCoIP connections work to desktops with the 5.1.3 Agent, then my DMZ/firewall rules, Security to Connection Server pairing, SSL Certs, and even Windows Firewall rules should all be correct. My test desktop pools are in the same VLANs/subnets as my production desktop pools. I even recomposed my production virtual machine (just my machine, not the entire department’s pool) to the View 5.2.0 Agent. Same result. I can connect internally but not externally.
I have only one Security Server to Connection Server pairing, so all tests are going through the same servers and network paths.
Regarding the PCoIP black screen, I don’t quite make it to a black screen. I get the dark gray remote desktop border with a hollow/transparent inside (it’s not filled with black and instead shows my desktop) for 1 second before the connection is closed. I am certain that the last thing that I install on my PVMs is the View Agent, but thank you for reminding everyone that the Agent must be installed after Tools.
For display resolution, here’s how I have things configured.
- vSphere > PVM > Edit Settings > Hardware > Video Card > Auto-detect video settings
- View Admin > Inventory > Pools > Test 5.2.0 pool > Edit > Pool Settings > Max number of monitors = 2 AND Max resolution = 1920x1200
Most of my external testing has been done via a Windows 8 x64 virtual machine I have at home. When I perform the test I select “Windows – Small” for the display. I’ve also tested externally via my iPad and iPhone, both with the newest VMware View Client. My iPad is able to connect internally to a 5.2.0 desktop at work but not externally from home.
I have provided VMware Support eight Wireshark packet captures:
- Security Server > External Client to a 5.1.3 Agent
- Security Server > External Client to a 5.2.0 Agent
- Virtual Desktop with 5.2.0 Agent > Internal connection via a 5.2.0 Client
- Virtual Desktop with 5.2.0 Agent > External connection via a 5.2.0 Client
- Work Laptop/Client > Internal connection to a 5.1.3 Agent
- Work Laptop/Client > Internal connection to a 5.2.0 Agent
- Home Lab/Client > External connection to a 5.1.3 Agent
- Home Lab/Client > External connection to a 5.2.0 Agent
What we find is no UDP traffic for external attempts to the 5.2.0 Agents. VMware Support is still reviewing this data.
I appreciate everyone’s ideas. If you have any more, I’ll be happy to test. In the meantime, I’ll continue to work with VMware Support. Thank you.