webRDP cannot connect to new Windows 10 workstations / Windows Server 2016 servers

webRDP cannot connect to new Windows 10 workstations / Windows Server 2016 servers

Issue

The HTML5 webRDP client will not connect to new Windows 10 workstations, but will connect to Windows 7 or Windows 8 workstations.

Possible Errors:

Received an error connecting to: <CN_OF_WEBAPP>


Solution

Clean installations of Windows 10 now require SSL for RDP to connect.  Therefore the webApp must be updated to use SSL security.

  1. Open webAdmin Dashboard.
  2. Expand Applications Admin.
  3. Select the RDP webApp.
  4. Select the webApp's Options tab.
  5. In the webRDP HTML5 Client Parameter field click the green plus to add a new parameter.
    sec=ssl
  6. Click the Save button.
  7. Click the Reload button to reload the webApp on the relay, with the updated settings, prior to testing.

*In the case of the Personal RDP webApp, it may be necessary to duplicate the webApp, calling it something like Personal RDP (Windows 10) to differentiate it for users that are required to have the SSL parameter added.  Once the SSL parameter is added, the webApp may not connect to workstations that do not require the SSL parameter.

**You will also need to disable the NLA setting on the workstation, if it is still enabled, as that will also result in the same error message if enabled: Disabled Network Level Authentication requirement for Remote Desktop.

***Windows Server 2016 behaves the same way, requiring the sec=ssl parameter.


Alternate Solution to use NLA

If you would like to take advantage of using NLA the webApp must be configured to submit credentials.
  • The webApp's Authentication tab must have valid credentials or Stoneware Variables entered for the Username/Password fields.
  • The webApp's Authentication tab must have the Domain field filled in.
  • In the webRDP HTML5 Client Parameter field click add a new parameter.
  • sec=nla (instead of sec=ssl)

    Can't find the KB

    Unable to find the KB to address your issue ?  

      • Recent Articles

      • Lenovo Unified Workspace 7.0.2.5 Released

        Highlights of Unified Workspace 7.0.2.5 Before you install: Please view the installation notes here. 7.0.2.5 requires a 7.0 license file. Below is a list of enhancements and fixes for Unified Workspace 7.0.1.41 Fixed external storage providers oauth ...

      • Lenovo Unified Workspace 7.0.1.41 Released

        Highlights of Unified Workspace 7.0.1.41 Before you install: Please view the installation notes here. 7.0.1.41 requires a 7.0 license file. Below is a list of enhancements and fixes for Unified Workspace 7.0.1.41 Updated Log4j Updated Java Updated ...

      • Alternative Product for Unified Workspace

        Unfortunately, Lenovo Software does not have an alternative product in which to migrate. To our knowledge, there just isn't any other single product out there that can do all that Lenovo Unified Workspace (LUW) was able to do. In searching for ...

      • Retiring Unified Workspace

        Lenovo and Stoneware are committed to providing the highest quality products and services to our customers. As part of our continued focus on innovation, we will be retiring Unified Workspace (formerly Stoneware webNetwork), effective January 31, ...

      • Assigned tiles not showing due to missing back-link

        Question We have several staff members that can't see a specific assigned tile/link. The tile has many group assignments the user is a member of, but when I view User Access and look at the assigned Link Sources, the tile/link is not listed. Issue ...

      • Related Articles

      • webRDP cannot connect to workstations due to NLA

        Issue ActiveX and WebRDP clients cannot connect to Windows workstations. Possible Errors: The remote computer has ended the connection. The server reset the connection. Parameter(s) you provided caused an error. The server requires that the client ...

      • Error connecting to Terminal Server 127.0.0.1

        Customer getting Error connecting to the terminal server: 127.0.0.1 after he updated the RDP client on his Windows XP and Vista machines. The customer was running 5.2.0.2 and needs to update to 5.2.0.4 or higher. The certificate used to code sign the ...

      • VBScript error connecting to Terminal Server VPN connection

        Getting message error connecting to terminal server:127.0.0.1 This means that the users machine is unable to connect to the backend server.  This can happen for a variety of reasons  Some things to check:  1) Make sure your workstation is fully ...

      • SSLVPN Terminal Server webapps through Safari on Mac with Java 1.7 not connecting

        Customer is trying to launch a SSLVPN Terminal Server webapp using Safari on their Mac. The are receiving the following error:  "Received and error connecting to 127.0.0.1"  Webapp connects fine using Firefox.  Customer is using the latest version of ...

      • Windows server tuning

        Question Are there any suggested TCP parameters that should be changed on a Windows server running webNetwork. Windows Server OS out of the box should function properly with webNetwork. However, some customers have had to follow this information from ...