cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
4166
Views
5
Helpful
3
Replies

VDI - Horizon Client access through 5525x

dmooregfb
Level 5
Level 5

We have updated our UCS equipment and bringing VDI online with the new VMware Horizon 6.0. In the firewall (ASA 5525x) buildout I have run into a stumbling block and am unable to render the desktop. Just get a black screen. 

There is a HTTPs type connection called Blaster Desktop. It is working correctly.

So when using the thick client, Horizon Client 3.x, we are unable to get a desktop to render. With a HTTPs connection running, I can log on with the thick client and watch as it grabs the Blaster desktop. Just unable to render the desktop.

If anyone has experience in this scenarios, please help! Attached is a diagram with the connection and ports defined.

Note: I am still able to use the thick client to connect to our old UCS. But in VMView 5.2 changes were made to how the SSL piece is handled and the firewall is not playing very well...

Thanks,

Dave

1 Accepted Solution

Accepted Solutions

dmooregfb
Level 5
Level 5

after running a second set of traces to provide TAC with additional information, we saw a problem with the configuration. The traces showed the view desktop was attempting to directly setup on the client. This was not suppose to be the case, as the client is outside and PCoIP was to be handling the connection between the Secure Gateway servers and the thick client.

Reviewing the connection and gateway servers configuration it was determined that PCoIP was configured but not enabled. After enabling, all thick clients were able to connect properly.

Thanks,

Dave

View solution in original post

3 Replies 3

keglass
Level 7
Level 7

David,

I recommend you also post this to the Cisco Support Community for additional feedback and information (Cisco Support Community).

Also, you can try searching here for related posts in the Support Community.

https://supportforums.cisco.com/search/site/Cisco%20ASA%205525-X%20Adaptive%20Security%20Appliance&resultTypes=document

Hope this helps.

Kelli Glass

Moderator for Cisco Customer Communities

Nilo Noguera
Level 5
Level 5

Hi David Moore,

You can reach out to our Cisco Technical Assistance Center (TAC) for help with the issue you have reported. Please check if you have a Cisco contract such as SMARTnet or Cisco Software Application Support (SAS) Service is required to be able to be covered by TAC.

You can contact the Cisco Technical Assistance Center (TAC) in one of the following ways:

•Online: http://www.cisco.com/tac/

•E-mail: tac@cisco.com

•Phone: North America 800-553-2447 | Australia 1-800-805-227 | Europe 32-2-704-5555  | Asia-Pacific 61-2-8446-7411 | UK 0800-404-7778

Please see the following URL for other contact numbers:

http://www.cisco.com/en/US/support/tsd_cisco_worldwide_contacts.html

If you don't have a Cisco contract such as SMARTnet or Cisco Software Application Support (SAS) Service to be able to be covered by TAC, you can post your question to the Cisco Support Community website (https://supportforums.cisco.com/) and somebody will assist you with your questions.

I appreciate this opportunity to assist you and I do hope the information I sent you pointed you to the right direction.

Best regards,

"Nilz"

Nilo Noguera

.:|:.:|:. Specialist, Cisco Global Virtual Engineering - Cisco Partner Help

http://www.cisco.com/web/partners/tools/ph.html

"niLz" Nilo Noguera Jr. | Specialist, Virtual Engineering - Partner Helpline Organization together we are the human network

dmooregfb
Level 5
Level 5

after running a second set of traces to provide TAC with additional information, we saw a problem with the configuration. The traces showed the view desktop was attempting to directly setup on the client. This was not suppose to be the case, as the client is outside and PCoIP was to be handling the connection between the Secure Gateway servers and the thick client.

Reviewing the connection and gateway servers configuration it was determined that PCoIP was configured but not enabled. After enabling, all thick clients were able to connect properly.

Thanks,

Dave