knowledgebase.nomachine.com Open in urlscan Pro
80.92.89.72 Public Scan

Back to summary

Submitted URL:
http://knowledgebase.nomachine.com/DT11R00196
Effective URL:
https://knowledgebase.nomachine.com/DT11R00196
Submission Tags: falconsandbox
Submission: On April 08 via api (April 8th 2022, 7:46:20 am UTC) from US — Scanned from DE

Form analysis
3 forms found in the DOM

Name: userloginformlayer — POST https://www.nomachine.com/support&destination=knowledgebase

<form class="form-inlineCust" action="https://www.nomachine.com/support&amp;destination=knowledgebase" accept-charset="UTF-8" method="post" id="userloginformlayer" name="userloginformlayer">
  <div id="nav-input-group" class="input-group mb-2 mr-sm-2 mb-sm-0">
    <div class="col-md-3 ">
      <label for="inputSupportLayer">Customer ID</label>
      <input size="20" name="name" id="inputSupportLayer" class="form-control nm-input-nav">
    </div>
    <div class="col-md-3 ">
      <label for="inputPassLayer">Password</label>
      <input size="20" name="pass" id="inputPassLayer" type="password" class="form-control nm-input-nav" autocomplete="off">
    </div>
    <a id="btn-submit" class="btn LoginLayer">
							</a>
  </div>
  <input name="form_id" id="edit-user-login-block" value="user_login_block" type="hidden">
</form>

GET https://nomachine.com/search/searchcontent/

<form role="search" id="nav-search" autocomplete="off" method="get" class="search-form-z" action="https://nomachine.com/search/searchcontent/">
  <input id="search-box" type="text" class="nm-input-nav-search ui-autocomplete-input" placeholder="SEARCH" value="" name="keys" autocomplete="off">
</form>

GET https://knowledgebase.nomachine.com//documents

<form method="get" id="searchform" role="search" action="https://knowledgebase.nomachine.com//documents">
  <input type="text" name="s" onblur="on_blur_background_icon(this.id)" onclick="background_icon(this.id)" class="kb-index-graphic" id="form_input" value=""
    style="background: url(https://assets.nomachine.com/img/kb/customercenter-search-icon.png) 5px 9px no-repeat scroll transparent; padding-left: 29px;  margin: 0px; border:1px solid #bebebe; ">
</form>

Text Content

NoMachine - Setting up remote access to Linux virtual desktops – Knowledge Base
 * 


 * EVERYBODY
   * NoMachine for Everybody
   * Show me how to start
 * ENTERPRISE
   * NoMachine for the Enterprise
   * NoMachine Cloud Server Products
     * NoMachine Cloud Server
     * NoMachine Enterprise Desktop
   * NoMachine Enterprise Desktop Products
     * NoMachine Enterprise Desktop
   * NoMachine Terminal Server Products
     * NoMachine Workstation
     * NoMachine Small Business Server
     * NoMachine Terminal Server
     * NoMachine Enterprise Terminal Server
     * Feature Comparison
 * DOWNLOAD
   * Download the Software
     * NoMachine for Windows
     * NoMachine for Mac
     * NoMachine for Linux
     * NoMachine for iOS
     * NoMachine for Android
     * NoMachine for Raspberry
     * NoMachine for ARM
     * NoMachine Enterprise Products Evaluation
 * SUPPORT
   * Get Support
   * Forums
   * Documents & Tutorials
   * Frequently Asked Questions
   * Knowledge Base
   * Customer Center
   * Report an issue
 * PARTNERS
   * Find a Partner
   * Technology Partners
   * Solution Providers
   * Become a partner
 * STORE
   * Buy Online
 * LOGIN
   * Customer ID
     Password
     Forgot your password?
 * * QUICK LINKS
      * Features
      * Price & availability
      * Article & FAQs
      * Software updates
     
      * Forums
      * Installation guides
      * Feature Requests
      * Trouble reports
     
      * About us
      * Contact us
      * Become a partner
      * News


NOMACHINE SUPPORT

Your questions answered

Home / Support / Knowledge Base / Documents / Setting up remote access to Linux
virtual desktops

Skip to content
Knowledge Base

All KB
Documents DT
Articles & FAQs AR
Trouble Reports TR
Feature Requests FR
Software Updates SU

Searching in : Documents
ID: DT11R00196
Version: NoMachine 7
Added on: 2020-12-16
Last Update: 2021-09-14

Print this article
PDF version


SETTING UP REMOTE ACCESS TO LINUX VIRTUAL DESKTOPS

This document is intended to provide general guidelines for understanding which
NoMachine products and licenses are necessary to provide remote access to
virtual desktops and single applications running on a single Linux host
(Terminal Services). The remote computer can be your own physical or virtual
machine either on-premises or hosted in a cloud .

Definitions

To create virtual desktops on the remote computer, NoMachine Workstation or
Small Business Server or Terminal Server needs to be installed on that computer.

A NoMachine virtual desktop is an individual instance of the remote desktop,
i.e. each user can have his/her personal desktop. Instead of running a virtual
instance of the whole remote desktop, it's also possible to execute single
applications. These two functionalities are available only with NoMachine
servers on Linux ('NoMachine Terminal Server' family).

A schematic diagram



This solution is suitable for small/medium business.

Pre-requisite to providing access to the remote Linux machine are to install (i)
a desktop environment (even in case of headless machines) and (ii) any of the
NoMachine servers from the 'Terminal Server' family.

Licensing

1 NoMachine Workstation license if you plan to have up to four virtual desktops

or 1 NoMachine Small Business Server license for up to ten concurrent virtual
desktops

or 1 NoMachine Terminal Server license for more than ten concurrent virtual
desktops (unlimited).

On the end-user's computer install NoMachine Enterprise Client (which is free to
use) or connect by the web via browser. All of the above-mentioned products
include access via the browser.

Minimum requirements

This scenario typically has installed:

1 NoMachine Workstation or Small Business Server or Terminal Server on a Linux
host.

Typical use cases

The following diagram shows a general infrastructure built on top of a
virtualized O.S. as the server host. A similar infrastructure can be set-up also
for a physical server host machine. Note that client-server connections can be
over the internet or on a private network (LAN). Users can connect by NoMachine
client via the secure native NoMachine NX protocol, the SSH protocol or by
browser (web sessions) via HTTPS. Password and key-based authentication methods,
as well as Kerberos tickets and two-factor authentication are supported.



Scalability

This solution provides individual instances of the remote desktops (virtual
desktops) and applications hosted on a single Linux computer. Workstation allows
4 virtual desktop sessions, Small Business Server allows 10 and Terminal Server
provides an unlimited number. In the case of a larger number of users, you may
consider setting up a multi-host environment with NoMachine Enterprise Terminal
Server to distribute virtual desktops and applications among Terminal Server
Node hosts. This solution allows load-balancing of sessions among multiple
hosts. High-availability of virtual desktops is also possible by setting-up a
failover cluster between two NoMachine Enterprise Terminal Server hosts.

TIPS

The NoMachine host can be either a physical computer or a virtual machine.
Multiple NoMachine Workstation or Terminal Server or Small Business Servers,
even in different geographical locations, can be federated under a Cloud Server,
which provides a single point of access to different subsystems.



--------------------------------------------------------------------------------


SETTING UP REMOTE ACCESS TO LINUX VIRTUAL DESKTOPS

Version: NoMachine 7

Last Modified: 2021-09-14

--------------------------------------------------------------------------------

This document is intended to provide general guidelines for understanding which
NoMachine products and licenses are necessary to provide remote access to
virtual desktops and single applications running on a single Linux host
(Terminal Services). The remote computer can be your own physical or virtual
machine either on-premises or hosted in a cloud .

Definitions

To create virtual desktops on the remote computer, NoMachine Workstation or
Small Business Server or Terminal Server needs to be installed on that computer.

A NoMachine virtual desktop is an individual instance of the remote desktop,
i.e. each user can have his/her personal desktop. Instead of running a virtual
instance of the whole remote desktop, it's also possible to execute single
applications. These two functionalities are available only with NoMachine
servers on Linux ('NoMachine Terminal Server' family).

A schematic diagram



This solution is suitable for small/medium business.

Pre-requisite to providing access to the remote Linux machine are to install (i)
a desktop environment (even in case of headless machines) and (ii) any of the
NoMachine servers from the 'Terminal Server' family.

Licensing

1 NoMachine Workstation license if you plan to have up to four virtual desktops

or 1 NoMachine Small Business Server license for up to ten concurrent virtual
desktops

or 1 NoMachine Terminal Server license for more than ten concurrent virtual
desktops (unlimited).

On the end-user's computer install NoMachine Enterprise Client (which is free to
use) or connect by the web via browser. All of the above-mentioned products
include access via the browser.

Minimum requirements

This scenario typically has installed:

1 NoMachine Workstation or Small Business Server or Terminal Server on a Linux
host.

Typical use cases

The following diagram shows a general infrastructure built on top of a
virtualized O.S. as the server host. A similar infrastructure can be set-up also
for a physical server host machine. Note that client-server connections can be
over the internet or on a private network (LAN). Users can connect by NoMachine
client via the secure native NoMachine NX protocol, the SSH protocol or by
browser (web sessions) via HTTPS. Password and key-based authentication methods,
as well as Kerberos tickets and two-factor authentication are supported.



Scalability

This solution provides individual instances of the remote desktops (virtual
desktops) and applications hosted on a single Linux computer. Workstation allows
4 virtual desktop sessions, Small Business Server allows 10 and Terminal Server
provides an unlimited number. In the case of a larger number of users, you may
consider setting up a multi-host environment with NoMachine Enterprise Terminal
Server to distribute virtual desktops and applications among Terminal Server
Node hosts. This solution allows load-balancing of sessions among multiple
hosts. High-availability of virtual desktops is also possible by setting-up a
failover cluster between two NoMachine Enterprise Terminal Server hosts.

TIPS

The NoMachine host can be either a physical computer or a virtual machine.
Multiple NoMachine Workstation or Terminal Server or Small Business Servers,
even in different geographical locations, can be federated under a Cloud Server,
which provides a single point of access to different subsystems.

FOLLOW US

 * RSS
   
 * Facebook
   
 * Twitter
   


Home
+
 * Download
 * Enterprise
 * Support
 * Partners

Learn more
+
 * Features
 * Price & availability
 * Article & FAQs
 * Software updates

Resources
+
 * Forums
 * Installation guides
 * Feature requests
 * Trouble reports

Company
+
 * About us
 * Contact us
 * Become a partner
 * News

Copyright 2002-2022, NoMachine S.à r.l. - VAT LU25935711