VMware Horizon Community
solgaeDK
VMware Employee
VMware Employee
Jump to solution

VMware Blast - Safari 7 does not work since 5.3

Hello everyone,

Not sure if anyone else is experiencing the same problem, but I'm having issues with Safari 7 from OS X Mavericks trying to connect to the View Desktop thru Blast protocol. Whenever I log in thru the VMware Blast portal, and then double-click on the desktop pool to connect to it, I get the message: "Your desktop has been disconnected. Attempting to reconnect to desktop...". Using other browser (Firefox, Chrome) lets me connect to the desktop thru Blast without any issues. This issue is happening even in recent release of Horizon 6.

Anyone else having this issues and know any solution/workaround without resorting into using alternate browser? Safari 7 did work with Horizon 5.2 HTML access as far as I remember. Downgrading Safari is not an option since Mavericks come with Safari 7.

Reply
0 Kudos
1 Solution

Accepted Solutions
Jon_Holloway
VMware Employee
VMware Employee
Jump to solution

Do you have a CA signed certificate installed on your connection server?  If not, then I think this is the cause of your problem, and you can work around it by trusting the cert through Safari/Keychain.

Thanks

Jon

View solution in original post

Reply
0 Kudos
4 Replies
HendersonD
Hot Shot
Hot Shot
Jump to solution

I am using 10.9.3 and Safari 7.0.4 and connect just fine to my View 5.3 desktop. I am connecting on campus through a broker, have not tried it from off campus through our security server

Reply
0 Kudos
solgaeDK
VMware Employee
VMware Employee
Jump to solution

The issue happens regardless of tunneled connection or not.

Reply
0 Kudos
Jon_Holloway
VMware Employee
VMware Employee
Jump to solution

Do you have a CA signed certificate installed on your connection server?  If not, then I think this is the cause of your problem, and you can work around it by trusting the cert through Safari/Keychain.

Thanks

Jon

Reply
0 Kudos
solgaeDK
VMware Employee
VMware Employee
Jump to solution

That was it! I was using self-signed since it was our lab instance. I set it to trust always, and now Safari 7 works like a charm. Thank you!

Reply
0 Kudos