Client software is unable to connect to 127.0.0.2

 On Windows XP SP2 the Windows Terminal Client is unable to connect to 127.0.0.2. If the system is unable to connect to 127.0.0.2 it will use 127.0.0.1.

 No Terminal-Server Client installed.

 A Terminal-Client installation is mandatory. Take a look at our FAQs for more information and download-link.

 Session crashes unexpectedly or does not respond for some seconds

 Some proxy servers, (Microsoft ISA Server™ e.g.) have a built-in Denial-Of-Service prevention. If the web proxy detects numerous requests to the same ressource, all subsequent connections will be rejected. This incident is covered by the Secure Terminal Services Client but takes time for reconnect. In order to avoid this incident, you may increase Client Deceleration. This will reduce the frequency of web requests.

 A Connection cannot be established

 Check your web-proxy settings try to re-connect for 2-5 times by restarting the client (some connections problems may occur) Check if your TerminalServer is up and running or try to connect to the TerminalServer at securetunnel.LMIS.de and check if you get a connection. Use the "Import IE Settings" if not sure.

   Click here to check testserver status!   (opens in new window)

 Terminal Services via Secure Terminal Server Gateway are slow when using the test gateway

 Please note that the current version is using a gateway server provided by LMIS AG at gateway.LMIS.de routing the traffic to your Terminal Server. The final Secure Terminal Server Gateway architecture suggest the installation of the Secure Terminal Server Gateway Server Endpoint on an Internet Information Server that is located near (in terms of network latency) to your target TerminalServer to increase connection performance.