- This topic has 3 replies, 2 voices, and was last updated 5 years, 4 months ago by
.
-
Posts
-
Hello,
I want to know if it’s possible from NoMachine client set up on Linux host to run multiple connections to multiple different servers :
– one on Linux , the second on Windows for example, even a third connection.
If it’s possible, how to do that ?
Now, when I run one connection to a server with my client, I can’t run a second connection. I can’t access to the menu, I must close my previous connection, in order to run a new connection.
Best regards.
I’m not sure what your scenario is 🙂 Do you want to connect multiple users to the same desktop? Or do you want to run multiple desktops on the same host?
You can have as many connections running from a client as you want. It is the server-side product which counts the connections in the case of physical desktop access to Mac, Linux, Windows & Raspberry, and the number of ‘virtual desktops’ for Terminal Server products (Linux only). Let me explain using the free-to-download NoMachine package as an example.
Installing the free version of NoMachine on the computer to be accessed means one connection is allowed to that computer at a time. If you want to connect different users to the same server computer, you should try the evaluation of Enterprise Desktop. This will allow unlimited connections to the same physical display of the machine you are accessing (users will see the same desktop).
Accessing multiple user accounts running on the same host is available on Linux, and not on Mac or Windows. This functionality is called Terminal Services, you provide a virtual desktop for each user and they work separately, even at the same time. To be connected multiple times from the same client to the Terminal Server host, you should use different user names. By default NoMachine enables the automatic migration feature: when a user connects to a server where the same user is already connected, NoMachine migrates the running application to the new connection. Terminal Services is exclusive to Linux and is not available on Windows or Mac.
Some useful information is here:
Differences between NoMachine Enterprise Desktop and the free to download NoMachine package
https://www.nomachine.com/AR07L00808Differences between NoMachine for Linux and NoMachine Workstation for Linux
https://www.nomachine.com/AR10K00702What is the difference between physical desktop and virtual desktop?
https://www.nomachine.com/AR10K00700In my case, I’ve got multiple clients with their own system (any OS). Users want to connect on the same Windows server host with their own login.
If i understand, it’s not possible ?
NoMachine does not let you run multiple Windows desktops on the same host. What you want to achieve is something that used to be called Windows Terminal Services and is now called Remote Desktop Services.
If multiple users connect with their own login to the remote Windows host where you have installed NoMachine, they will all share/view the same physical desktop.
If you’re looking for a replacement of a Windows Terminal Server, I’ll answer something similar to what I wrote here: https://forums.nomachine.com/topic/windows-terminal-server-replacement-options#post-13496.
Our software can’t completely replace a Windows Terminal Server computer or make any Windows computer become a Terminal Server. Technical considerations apart, this would be in violation of the Windows licensing terms.
There are two ways for different users to get access to multiple Windows desktop environments on the same Windows server and all the applications available on them. You can either create multiple Windows instances virtualized on top of popular hypervisors like KVM, VirtualBox or VMware etc, then install NoMachine or NoMachine Enterprise Desktop on each instance. This will give each user access to their own account.
Alternatively, many of our customers which have mixed environments (i.e they want Linux applications as well as Windows) take advantage of the support for RDP which is available in Terminal Server for Linux. You can keep your RDS backend (you will still need the MS CALs in place) and the NoMachine Terminal Server acts as a ‘gateway’ which will take care of forwarding the client’ requests to the Windows server on the backend. The RDP sessions are essentially encapsulated inside NoMachine virtual Linux sessions. If this might interest you, see here: https://www.nomachine.com/AR02D00349 and https://www.nomachine.com/AR07J00645 for more information.
This topic was marked as solved, you can't post.