VMware Horizon Community
shayrulah
Enthusiast
Enthusiast

Horizon Client 5.4 not connecting

After last update of horizon client to 5.4 on android device and MAC device is not possible to connect to connection server. It works fine with WEB and Windows client.

pastedImage_0.jpgpastedImage_1.jpg

18 Replies
SysteembeheerNS
Contributor
Contributor

I got the same problem!

Downgrading to 5.3 works.

Natestack
Enthusiast
Enthusiast

we just updated on windows and sure enough cant access desktop pools anymore that are blast protocol

Change it to PCOIP and all is working.

uninstalled and reverted back to 5.3 happy days.

Any ideas 

sjesse
Leadership
Leadership

What version of horizon are you trying to connect to?

Reply
0 Kudos
Mickeybyte2
Hot Shot
Hot Shot

I've upgraded my own laptop (Surface, Win10) from 5.3 to 5.4 yesterday and have no issues connecting BLAST or PCoIP.

Our setup: Horizon 7.9, connection through UAG3.6, wildcard certificate

(One thing I noticed, but still need to confirm by returning to 5.3 is that mouse scrolling is only working while the mouse is moving...)

Regards, Michiel.
Reply
0 Kudos
Natestack
Enthusiast
Enthusiast

Connecting to multiple versions

7.7 ,7.10 to 7.11

Just get error

Error The connection to the remote computer ended

Change to PCOIP works fine downgrade to 5.3 both protocols work as normal.

nothing has changed other than the version of horizon client.

Reply
0 Kudos
sjesse
Leadership
Leadership

yeah based on everything I see make sure if your seeing this to open a SR so VMware knows if you haven't, I currently haven't seen this yet.

Reply
0 Kudos
shayrulah
Enthusiast
Enthusiast

Just to note that with Windows client 5.4  works just fine  issue is related with Android horizon client 5.4 and MAC OS horizon client 5.4

Reply
0 Kudos
feelfreetoblame
Contributor
Contributor

Similar issues noted in this post: Re: Error: "invalid Server Address is specified" with VMware Horizon Version 5.4.0

Seems someone also saw the error on ChromeOS.

Reply
0 Kudos
kdenike
VMware Employee
VMware Employee

We believe that we have narrowed this problem down to some older versions of UAG (3.2 and 3.3.1) and the Windows, Mac, Android and iOS clients. We're working on a fix. In the meantime, reverting to 5.3 works (except for iOS which won't allow it). Apologies to those hitting this problem!

feelfreetoblame
Contributor
Contributor

Thank you. For what it's worth, our UAGs are on version 3.4.

Reply
0 Kudos
shayrulah
Enthusiast
Enthusiast

In my case UAG is v3.5

Reply
0 Kudos
JohnTwilley
Hot Shot
Hot Shot

We are running on UAG 3.6 and have no reported (or tested) issues so far.

Reply
0 Kudos
yqowen
VMware Employee
VMware Employee

Yes, UAG 3.6 or later didn't encounter the issue.

Reply
0 Kudos
kdenike
VMware Employee
VMware Employee

I have an update:

  • This is all caused by an incompatibility between the new clients and older UAG, we do not have the problem with UAG 3.8 or 3.9.
  • The 5.4.1 update is available in the Google Play store!
  • The Windows clients 5.3 and 5.4 only have this problem if you install them in dual IPv4/IPv6 mode which is not the default install option.
  • The Mac client 5.4 also has this problem.
  • We will are working to post updates to the Windows and Mac client next week. Until then you can revert to the 5.3 Horizon Client, upgrade your UAG or reinstall your Windows client with IPv4 only.

The Android client also runs on a Chromebook in ARC++ mode.

agong
VMware Employee
VMware Employee

Could you please enable debug log level log, reproduce the issue and send logs to us for analysis? Thanks.

Refer VMware Knowledge Base for how to enable debug log and collect log bundle.

Reply
0 Kudos
StoddardE
Contributor
Contributor

Is there a timeline on when the Chrome Web Store App will be upgraded as well?

Reply
0 Kudos
shayrulah
Enthusiast
Enthusiast

There is new release for Andorid Horizon CLient 5.4.1 and issue is resolved.

feelfreetoblame
Contributor
Contributor

I see a new release for Mac clients now, will test to see if the issue is resolved.

Edit: One user has reported success so far, I believe we may be good. Thanks.

Reply
0 Kudos