NoMachine Support

Your questions answered

Knowledge Base

Searching in: Articles & FAQs
Filter the search results
Applies to:
Last update:
Searching in: Articles & FAQs
ID: AR02D00349
Applies to: NoMachine Server
Added on: 2006-02-27
Last update: 2018-01-08
Using NoMachine Server for Linux to access Windows Terminal Server from the client machine

The enterprise-oriented products NoMachine Enterprise Terminal Server and Terminal Server, allow RDP-supported connections. By connecting through the NoMachine Server installed on a Linux box, to the Windows Terminal Server, you will be able to run your Windows applications remotely from your computer/device via web or via NoMachine client.

The resulting schema is as follows:

NoMachine Client  or browser ----> NoMachine Server ----> Windows Terminal Server

In this way the clients will be able to access the resources and the applications residing, in this case, on the Windows Terminal Server. In this kind of setup, NoMachine Server acts as a 'gateway' which will take care of forwarding the client' requests to the Windows server on the backend.

You will need to verify that you have:

  • A browser or NoMachine Client for your operating system client-side
  • NoMachine Enterprise Terminal Server (ETS) or NoMachine Terminal Server (TS) on your 'gateway' machine (Linux)
  • A suitable version of rdesktop is installed on the NoMachine server host

Users wishing to adopt any of the NoMachine servers (provided they support the RDP protocol) with a Windows Terminal Server installation should also read the following article:



Notes for enabling RDP support with NoMachine

Please follow instructions here: to setup the environment and enable RDP support with NoMachine.

In case of NoMachine multi-node environments (Enterprise Terminal Server + Terminal Server Nodein v. 6), it's necessary that a suitable version of rdesktop is installed on each of the Terminal Server Node machines. More about this is available here: