Britgirl

[Britgirl]

There is a Trouble Report open for this particular issue. You can follow it here: https://www.nomachine.com/TR12P09040.

[Britgirl]

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.

 

[Britgirl]

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/AR07L00808

Differences between NoMachine for Linux and NoMachine Workstation for Linux
https://www.nomachine.com/AR10K00702

What is the difference between physical desktop and virtual desktop?
https://www.nomachine.com/AR10K00700

[Britgirl]

Here is the Feature Request that we opened based on your feedback. Please use the ‘notify me’ service to receive an email when it has been implemented 🙂

https://www.nomachine.com/FR11P03739

[Britgirl]

Instead of editing/etc/NX/server/localhost/server.cfg, you should be editing /usr/NX/etc/server.cfg. Try that and let us know.

[Britgirl]

Also if this is an open source project, then why does it require enabling proprietary repositories in Linux

Just to clarify. NoMachine’s core technology is not released under an open source license agreement. Maybe you are getting confused with an open source derivative that is shipped with the Linux distribution you are using (which we have no control of).

If you are interested, you can see the list of open source components we release to the community in the download section: https://www.nomachine.com/opensource

[Britgirl]

Thanks for reporting. We were able to reproduce it and opened a Trouble Report which you can see here:

https://www.nomachine.com/TR12P09035.

Please use the ‘notify me’ service to receive an email when a fix has been released.

[Britgirl]

Hi Gabriele,

we’ll use the logs file you submitted directly to us. Thanks!

[Britgirl]

You’ve successfully logged in. You say it’s unresponsive, but from the logs it appears to be a network connection issue. The automatic reconnect kicks in when the network connection is lost for whatever reason. It could be a network issue on the client side. Are you able to ping IP_server-host from the connecting client when it happens?

It could also be a network problem on the server side. Ideally, we would need server side logs to see what is happening and they would also confirm whether it’s being caused by the connection being lost or some other issue.

Logs can be sent directly to forum[at]nomachine.com[dot]com. Instructions to extract them are here: https://www.nomachine.com/AR10K00697

[Britgirl]

@alfa111, sorry for the delay in getting back to you. We’re still investigating and will update the topic soon.

[Britgirl]

Ok 🙂 Thanks for letting us know.

[Britgirl]

Hi, when prompted to log in, you should use the username and password of your account on the remote PC (fig.7 here https://www.nomachine.com/getting-started-with-nomachine)

No empty passwords are allowed by the way (see this article for more information about that: https://www.nomachine.com/AR05L00802)

You say that it doesn’t work. Can you tell me what message you are getting (a screenshot would be useful)?

[Britgirl]

Here is the associated Trouble Report. By clicking on ‘Notify me’ you can sign up to receive notification of when a fix has been released.

https://www.nomachine.com/TR12P09027

[Britgirl]

See Kroy’s earlier reply to you from November. The document explains how to enable debug and extract the logs.

If the problem is still there, enable debug, reproduce again and send logs from the server side (instruction how to collect logs you can find there: https://www.nomachine.com/DT10O00163

Thanks!

[Britgirl]

So you don’t even reach the login prompt (username and password pane)? We’ve gone through the instructions again just to make sure they are correct, which they are. Have you checked whether there IP address has changed? If you are using a previous session file, try creating a new connection from scratch. Does that help?

[Author]

Posts