NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Dami346
Sep 11, 2026Follower
SSL/VPN handshake failure through RS300 confirmed router-side issue
I started having issues with connecting to my WFH on 9/6/2026. First it was my spouse that couldn’t log on to her work laptop device with a different client sign on. Mine was Omnissa Horizon Client I...
schumaku
Sep 12, 2026Guru - Experienced User
FrumpyGrandpa wrote:The first question is usually, "what changed?"
...something has changed, or why should the well known Omnissa Horizon Client (the good old VMware Horizon Client) - technically implemented on the Unified Access Gateways SSL VPNs - should now fail?
A possible background? Dami346's RS300 had been updated to RS300 Firmware Version 1.2.7.2 , released early June 2026 pushed with the common intended delay of several weeks by the Router Auto Firmware Update (the control is when I remeber right in >>> ADVANCED > Administration > Router Update). According to the version number change, this was and is bigger update.
Don't know the Netgear RS router update policy in detail. A possible approach would be to disable the automartic update, and install the earlier RS300 Firmware Version 1.0.6.16
Fingers crossed...
StephenB
Sep 12, 2026Guru - Experienced User
schumaku wrote:...something has changed, or why should the well known Omnissa Horizon Client (the good old VMware Horizon Client) - technically implemented on the Unified Access Gateways SSL VPNs - should now fail?
Agreed.
Reverting to 1.0.6.16 is a reasonable first step. If that doesn't change the behavior, I'd restore 1.2.7.2.