Sunday, March 18, 2012

Connecting to a VMware View 5.0 virtual desktop through a Security Server displays a black screen and terminates with the message: “The connection to the remote computer ended.”

Problem

You’ve successfully deployed a new VMware View 5.0 Security Server in your DMZ and published it for remote users to access but connecting to it through the internet displays a black screen for a few seconds:

image

… and the session terminates with the message:

VMware View Client

The connection to the remote computer ended.

image

Solution

I’ve experienced this behavior in the following 2 cases:

Case #1

The PCoIP ports between your Security Server which sits in the DMZ and your internal trusted network where the Connection Server and View Desktops are or the internet where the remote users are connecting from.  Ensure that you have the PCoIP ports opened between the DMZ and internal trusted network and the DMZ and the internet.  See the following KB for more information about the ports that are required to be opened:

Network connectivity requirements for VMware View Manager 4.5 and later
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1027217

**Note: Make sure you scroll down when viewing the KB article as the formatting was displayed with quite a bit of empty white space between the tables.

Case #2

Depending on your topology (i.e. there is only 1 View Connection server), you may need to check the Use PCoIP Secure Gateway for PCoIP connections to desktop:

image

image

More information about why you need to enable settings can be found in the following link:

Setting up PCoIP Remote Access with View 5.0 and 4.6
http://communities.vmware.com/docs/DOC-14974

4 comments:

Anonymous said...

Thanks a lot, this was really really helpful! Could't find this using the VMware site!

Anonymous said...

Also, check the system clock on the client and match it to the server. That's what caused this error for me.

AJun said...

Thankyou very much for your post. it's very helpfull.

i don't find any clue for this issue in KB vmview.

Andrew Morgan said...

Extremely useful, thanks.