As context, when this error happens, a device has been configured to
automatically connect to the server and something in the environment changed that prevents the terminal from connecting. Examples of this can be, a change of IP address or a server replacement.
Prevention is the best medicine, where configurations are made in the terminal before are made in the environment. In the case of the IP address change, the terminal is configured with the information of the new IP location before the change happens, or is reverted to manual connection in order to have access to the firmware menus after the changes take place.
However being the fact that the issue has taken place and you have arrived at this article, still the best way to break the loop is through the vSpace console itself. In order to get the vSpace console to find the terminal you can do the following:
Invoke the vSpace Console and go to Devices then press the + symbol next to NETWORKS. Here you will enter the information of the old subnet IP address range where the terminal is located at.
At this point the console will scan that range of IP and should find the terminal. From there, you can click on the terminal in question and configure it to manual in order to update the information accordingly.
If this is not possible, then you may need to recreate the old environment again so the terminal can be found and configuration can be modified.
If none of this works, one more available option is cause a disruption to the loop at the actual device, so you can access the firmware and modify configurations.
1. Turn off the device and remove the network cable.
2. As you turn the device back on, start pressing the ESC key fast and repeatedly during boot until the terminal displays the firmware home screen. Form there, you can change configurations.
REV 10/2018
Related Articles
Automatic configurations on L Series and M Series devices.
You can set your NComputing device to Connect to your server, your Windows session or to a single program, automatically. The best way to understand the configuration process is to do it through the firmware of your terminal. Here are several ...
How To Recover the RX300 Firmware Image
Please note that this procedure is for the RX-300 (Black and Magenta chassis) thin client only. All other RX family devices (like the RX-RDP or RX-HDX) will not benefit from this procedure and you can void your warranty if the steps outlined in this ...
How To Recover the firmware Image for RX-RDP, RX-RDP+, RX-420(RDP) and RX-440(RDP)
Overview The following procedure will help you when you have a persistent issue with your device's firmware configuration or if you are in need of restoring the unit beyond a common factory settings reset. Below are the instructions on how to restore ...
L Series: Error: "This client's firmware is unsupported by the terminal server software"
Scope When attempting to connect to an L-series vSpace host on the network, the error appears, and the connection fails. If you use a L Series Legacy Device (L100, L110, L120, or L200) device, these are outdated, need to be upgraded and because of ...
Windows Server 2008 R2: Remote Desktop Licensing Server Configuration
About this article This will be a helpful guide to assist you with setting up your licensing server. When setting up a Microsoft Windows, Server Operating System, you will see the requirement of configuring an activate a Licensing Server within a ...