Super6VCA
Expert
Expert

MAC Client Issue

Have a Macbook with latest OS and when we try to install the Mac Client and add a server we get an error that says  "Alert  Error:  Couldn't connect to server"  I am able to get to the server via the web and even when i try the IP address i get the same message.  Will not let me add server?   i tried different versions of the client with no luck.   Anyone have any thoughts??

Thanks

Perry

Thank you, Perry
0 Kudos
7 Replies
sjesse
Leadership
Leadership

Whats all the versions of software your using, I think older versions have a tls issue with newer mac, and if you look in the log from the horizon client their may be ssl errors.

Horizon Client for Mac Logs

0 Kudos
Super6VCA
Expert
Expert

latest mac OS and i tried version 5.0 of the horizon client and version 5.2.1

Thank you, Perry
0 Kudos
sjesse
Leadership
Leadership

I mean horizon agent, connection server, uag if your using it.

0 Kudos
Super6VCA
Expert
Expert

not even getting that far.  As soon as i try to add a server on the client i get the error immediately.  I can't even find any VMware folder in the /Library/Logs folder. 

Thank you, Perry
0 Kudos
larstr
Champion
Champion

Perry,

If the server side is much older or newer than the client version you will have problems. We know you've tried both 5.0 and 5.2 of the client, but you should also check if the server side is among the supported versions:

VMware Product Interoperability Matrices

Lars

0 Kudos
Super6VCA
Expert
Expert

Lars,

We are running Horizon 7.7 on ESXi 6.5.  We have plenty of other Macs that connect just fine but this one seems to be the headache.  One of the odd things is that there is no place to change preferences in the Mac client so i think there could be a macbook issue.  More to come.   Thanks

Thank you, Perry
0 Kudos
larstr
Champion
Champion

Super6VCA,

Horizon 7.7 on ESXi 6.5 and 5.0 or 5.2 client should be perfectly fine. From Help / About in your Horizon client it will tell you where the session log is and you could try to see if you find anything there. Other than that you could try to call VMware Support and check if they have had a similar issue reported before.

Lars

0 Kudos