Although a thin client can be scanned from the console, it cannot be registered on the server. One of the following error messages will appear in the UMS console:

  • Cannot connect to remote management server
  • Protocol state invalid


This may be caused by

  • the server's firewall blocking the process.
  • an already existing UMS certificate on the thin client.
  • some database service hanging.
  • network transfer delays or losses affecting the registration process.


Solving the firewall problem:

  1. On your system running the UMS console and server add the following port to the Windows firewall as an exception:
    • Name = IGEL RMGUIServer
    • TCP Port = 30001

    If you have changed the standard port 30001 in the UMS administrator, open the firewall accordingly for this port.
  2. Make sure no other firewall within the network is blocking ports 30001 and 30005.
  3. Try to import the thin client again.

Solving the certificate problem:

Reset the thin client to factory defaults and try to import the thin client again.

Solving the database problem:

In UMS Administrator disable the currently active data source and re-activate it again. Try to import the thin client again.

Checking the network:

Check if the network is fine by sending pings from the thin client console to your UMS server:
ping -s -c 10 -M do
Start with SIZE =1500 and decrease the size of packages until all packages got transferred without fragmentation or package loss. 1440 / 1400 / 1350 / 1300 are good values to test with.

On a thin client with IGEL Linux you can use the built-in network tools as well for "pinging" the server (Starter for Sessions > System > Network Tools).

See also IGEL UMS Communication Ports.