https://worldofeuc.com logo
Join Slack
Powered by
Anyone running into issues connecting externally u...
# omnissa-horizon
c
Anyone running into issues connecting externally using Horizon Client 2512? We get TLS errors on all platforms (Windows, Linux, macOS) when connecting remotely. Internal connections are fine. Downgrading resolves the issue.
s
Does this happen on both the Horizon 2512 and Horizon NEXT client or just one? Do the certs have the full chain in them?
c
Both 2512 and Horizon NEXT. The certs has the full chain in them as well.
This is apparently a known issue affecting multiple customers. There are currently working on a fix but until that time downgrading is the workaround (plus disabling automatic update on macOS devices)
j
Is there an associated KB that you can reference for this issue?
c
There is not. I talked with support yesterday and there is an active P1 with engineering to find the root of the issue. They said they would publish one when they had something to provide. Is this affecting you as well?
j
Not that I know of yet!! But I'm sure my BYOD users will be updating to the latest Horizon 2512 Client and expect to hear complaints.
c
Gotcha. I'm surprised that there is no chatter on the forums or various subreddits for this. It makes me think it's a smaller subset of customers with some specific configuration. The real issue for us is that the macOS automatic update has no way to defer or cancel the upgrade. Users can connect when the upgrade prompt is present but they can't cancel it. Most of them are just hitting next next next then finding they can't login.
Support provided this as a workaround: 1. create config.ini under C:\users\%username%\AppData\Roaming\Omnissa 2. add RemoteDisplay.enableBypassBlastServiceTcpProxy=FALSE It works as expected. I've asked about a workaround for macOS devices as well.
🙏 1
This is the same fix for macOS: Add - RemoteDisplay.enableBypassBlastServiceTcpProxy=FALSE in com.omnissa.horizon.plist file under /Library/Preferences/com.omnissa.horizon.plist system-wide settings affecting all users on the Mac. I don't have a device to test on at the moment.
s
Damn, this is on the client side? That's rough, assuming a new client needs to be issued? Anyone else see this?
c
Yes, unfortunately. I'm assuming they'll release a .1 to resolve, but we'll see. Support says multiple customers affected but I haven't seen anyone else talking about it.
j
Just curious - Are your users getting that error randomly, or is it consistently not working for them?
c
They get the error 100% of the time after upgrading to 2512
j
OK. Thank You for sharing your experience.
c
No problem! I'll write this up if there isn't a KB posted after the holiday.
s
I've got the 2512 client on my side and no issues connecting to my environment or customers. Does this happen when only the client is updated, or does it happen when both client/server are updated to 2512
c
Client to 2512, rest of environment is on 2503
This is from support "The cause of the TLS error with 2512, as per our engineering finding, is as below. 1. The proxy hop needs to be configured to allow all ALPN strings or stop inspecting the TLS ALPN extension altogether. 2. As part of one of the recent blast networking features, the 2512 client has been updated to include a new Blast-specific TLS ALPN extension by default. 3. The proxy hop between the client and the agent that’s inspecting TLS traffic is rejecting all TLS connections that have the newly introduced Blast ALPN. This is a fatal error, and the connection fails immediately, as reported. 4. Disabling the feature on the client does not cause the issue."
🙌 1
s
Interesting, thanks for keeping us updated on this!
j
If you don't mind me asking, what was the Proxy software that was performing the inspection?
c
The proxy they're referring to is something on the Horizon end, nothing that we've configured. The workarounds they've having us try are to disabling bypassing the Blast proxy, I believe.
👍 1
We got a registry key from support to apply to the agent side as a workaround today but it did not resolve the issue for us.
Horizon Client 2512.1 was released today for all platforms to resolve this issue. Someone goofed on the release notes for the Windows version, but we've confirmed that this resolves the issue for us. Omnissa Horizon Client for Windows Release Notes
🔥 1
Open in Slack
PreviousNext
Powered by