Forum Replies Created
-
Posts
-
🙂 thanks for showing us your appreciation. Our developers added significant performance improvements for high bandwidth networks, specifically in the adaptive frame rate algorithms – you can see the list of implementations here: https://www.nomachine.com/SU10P00200.
The best thing to do would be to update to the latest version, 6.4.6. You are using a much earlier version which in theory is only available to customers with subscriptions from their customer area which makes me think you would be better opening a support ticket if you can.
If neither of those options are possible, send the logs directly to forum[at]nomachine[com].
Hi, If computers are in the same LAN, NoMachine will discover them automatically and show them in the Connection GUI on the connecting client.
If the IP addresses of the computers being accessed are constantly changing, then what you are going to need is NoMachine Network. This is an upcoming functionality, you can read more about it here: https://www.nomachine.com/FR07J02731
If you can explain better what you need to do exactly, we can point you to the right place on our website 🙂
Besides the NoMachine compression protocol, which is not public anymore, since version 4, there is not a single NoMachine API, but many different pieces: NoMachine server, the node, the player, which interact with each other using the NoMachine libnx core.
Additionally, the server offers a “pluggable scripts” interface which lets programmers add their own extensions to the server, so that their custom functions are executed before, during and after each session startup and shutdown.
This server interface is described in the document “NoMachine Enterprise Products – Server Guide”, which you can find here: https://www.nomachine.com/DT07M00090, in section 9.
It’s also possible to run the nxplayer from the command line and customize the session file (NXS configuration). More about this is here: https://www.nomachine.com/AR04O00923
If this documentation is not enough, don’t hesitate to explain what you’d like to achieve.
We were able to reproduce the issue you’re encountering and have opened a Trouble Report. There is a workaround available. Please sign up to receive notification of a fix when it becomes available. https://www.nomachine.com/TR12P09044
NoMachine doesn’t install video drivers and doesn’t mess with frameworks. At the most, it could have triggered a problem by changing desktop resolution. But this is done using standard system APIs in a conventional way. That said, we have not been able to reproduce this very unusual behaviour with the latest version so far (both sides).
There is a Trouble Report open for this particular issue. You can follow it here: https://www.nomachine.com/TR12P09040.
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.
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/AR10K00700Here 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 🙂
Instead of editing
/etc/NX/server/localhost/server.cfg, you should be editing/usr/NX/etc/server.cfg. Try that and let us know.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
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.