NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

Dami346's avatar
Dami346
Follower
Sep 11, 2026

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 kept getting error: an SSL error has occurred, the server connection error followed. All other device on my home network works just fine. With download speed at 2247.17 while upload speed 296.68. Called my network provider all seems fine. I took the device to work it work brought it back home, use my mobile personal hotspot i was able to log on but whenever I am on the ethernet cable connected to my router I receive those errors. Then I connect directly to my CM300 modem port I was able to log on. Which brings me to why the sudden change on the router. What could be blocking my Horizon handshake. 

direct-to-modem works, RS300 in the path breaks SSL handshake. Now looking to purchase a new router 

4 Replies

  • schumaku's avatar
    schumaku
    Guru - 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's avatar
      StephenB
      Guru - 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.

  • The first question is usually, "what changed?"

    Are Netgear features such as Armor or Smart Parental Controls enabled on this router?