Forum Discussion

aschaef_137607's avatar
aschaef_137607
Icon for Nimbostratus rankNimbostratus
May 12, 2014

I currently have all boxes unchecked on both view connection servers.

 

I am trying the following tests to make sure the view machines are reachable both internally and externally with PCoIP and HTML5.

 

Internal PCoIP test using View Client - works great Internal HTML5 test using https://desktop.domain.com successfully authenticates and then brings me to the following URL where I get a security certificate warning "https://10.0.0.10:22443/d/499849BA-A092-44AB-8D7E-330903764E73/?vauth=tbQ5v%2FXNaAyQnXL0FRZbCJ%2BL" If I accept to continue then the desktop loads (my only issue is the certificate warning)

 

External PCoIP test using iPhone - works great External HTML5 test using iPhone - works with Chrome, but not Safari browser

 

External PCoIP test using domain laptop (not on VPN) - Successfully authenticate using the View Client but it sits and spins on "The Connection Server is preparing the desktop..." I then tried going to https://desktop.domain.com and choosing VMware View Client. The behavior is the same where the client sits and says "The connection server is preparing the desktop..." External HTML5 test using domain laptop (not on VPN) - works great.

 

  • Greg_Crosby_319's avatar
    Greg_Crosby_319
    Historic F5 Account
    May 12, 2014
    In this setup there is not a proxy handling certificates, which means you are going to connect to the desktop on port 22443 and use the default certificate installed when you installed the blast desktop agent onto the virtual desktop. The default certificate is self signed, so your client is not going to recognize the certificate as being issued by a trusted CA. This document discusses how to replace the default "blast" certificate with a trusted root CA:http://www.vmware.com/pdf/horizon-view/horizon-view-52-feature-pack-document.pdf. For "The connection server is preparing the desktop..." issue, I would confirm APM has the required ports open to the desktop pool, udp 4172, and that you are running View 5.2 or newer. You could run tcpdump on APM and filter for udp 4172 to see where PCoIP connections are destined. Maybe something like tcpdump -i 0.0 port 4172. If you see a connection attempt to a valid virtual desktop ip address but no response, then you might have something in the middle blocking udp 4172.