Forum Replies Created
-
Posts
-
NM 5 Enterprise Server allows only 1 concurrent connection to Windows server, since NM provides access to *physical* desktop ?
It supports unlimited connections to the same physical desktop. Enterprise Desktop for Windows also has the same functionality. Enterprise Server offers node support, HA and other functionality which you can compare here: https://www.nomachine.com/feature_comparison
AFAIK, Windows Server allows several concurrent connections (RDP) , natively, on the server. Is this not available in NM 5 Enterprise Server
Enterprise Server supports RDP as you will see in the features table I just linked. It would make sense to have Enterprise Server for Linux or even Terminal Server, which via RDP, will connect you to your Windows nodes. If you want to set up RDP, please see here:
Using NoMachine Server for Linux to access Windows Terminal Server from the client machine
https://www.nomachine.com/AR02D00349 and https://www.nomachine.com/AR07J00645.Does it make any sense to create a NM5 cluster, with only Windows server ? If yes, then this will only allows as many concurrent connections as declared servers in the cluster ( e.g. a cluster with 4 Windows NM5 “nodes” will allows only 4 concurrent connections on cluster ).
If it’s acceptable to you that one Windows node is one desktop, the ES for Windows can be used as the entry point to broker connections to the nodes (each node being one Windows desktop). If you need assistance with pricing and setting up the server, please contact our sales team using the Contact Us link in the footer of the website.
After many attempts, we’ve finally been able to reproduce it. It would appear to be more of a problem with KDE 5, not NoMachine. Whilst we investigate further, it might be better to use an alternative desktop environment until we’ve identified a workaround. When we have some more info we’ll post it here.
Just to clarify, the ‘gateway’ is the NoMachine Terminal Server for Linux on which you’ve enabled RDP and also checked that rdesktop is running (see article instructions). Any Windows CALS (whether per device or per user) remain unaffected. NoMachine licensing, which is per server and in the case of our two products mentioned you get unlimited sessions, cannot replace MS CALS in any way.
DefaultDesktopCommand “/usr/bin/startxfce4” is the correct format and works. We checked this and don’t have any issues with LXQt or XFCE in Arch. So I can only assume that there is something wrong with your configuration of LXQt or XFCE not with NoMachine. What about trying re-installing Arch?
For pricing you should contact our sales team via the Contact Us form (see footer below). They will be able to help with that.
NoMachine 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 to get access to Windows desktop environments and all the applications available on it. You can either create multiple Windows instances virtualized on top of popular hypervisors like KVM or VMware, install NoMachine Enterprise Desktop on each instance (this will give you access to the display) and add the Enterprise Desktop to a NoMachine Cloud Server which will function as the entry point and where you can configure access, user profiles etc.
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 WTS backend (you will still need the MS CALs in place) and use RDP to connect to Windows desktop sessions. You can read more about this here:
Running RDP sessions with NoMachine 4 or later
https://www.nomachine.com/AR07J00645Other similar posts which you may find useful:
https://www.nomachine.com/forums/topic/deliver-windows-applications-over-nomachine
https://www.nomachine.com/forums/topic/can-i-publish-my-windows-application-on-web
Looks like you are installing the 32 bit package on a 64 bit system without 32 compatibility libs installed.
Take a look at the article here: https://www.nomachine.com/AR02J00623
The Trouble Report is available here: https://www.nomachine.com/TR01O07470
Please sign up to the ‘notify me’ tool to know when a fix has been made available.
Thanks for reporting. We’ve reproduced it and opened a Trouble Report: https://www.nomachine.com/TR01O07476
Please use the ‘notify me’ check box to know when it has been fixed.
Fail2ban support is on our roadmap. You can view the Feature Request here:
I don’t understand what you mean? Are you talking about multi-monitors? Can you describe what you’d like to achieve with more details?
If you want to start from the first pane (see attachment tutorial_3.jpg), you can write nx://11.111.111.11:22222 and click ‘Connect’.
What happens? Do you connect?
If, on the other hand, you are using the connection wizard to create your connection (see attachment tutorial_13.jpg) you must write the hostname and then in the box next to it, you write the port number eg: Host is 11.111.111.11, so you enter 11.111.111.11. Port is 22222, so you enter 22222.
What happens? Do you connect?
These images are available in the tutorial here: https://www.nomachine.com/getting-started-with-nomachine#internet
Attachments:
You wrote that disabling hardware acceleration (decoding) on the client, the performance improves. It would seem that the HW is to blame, not really NoMachine.
You could try using H.264 software encoding, you can follow the instructions here: https://www.nomachine.com/AR10K00706. This should help diminish the use of the CPU.
In its current design NoMachine sends the content of all the remote monitors even though you may be viewing the content of one of the displays only client-side. This is to ensure a smoother experience in visualizing the content when you’re switching among monitors.
This behaviour is becoming less convenient nowadays what with monitor resolutions getting larger. We are already working on improving how NoMachine handles the encoding of multi-monitors, so that each monitor is encoded separately and content is transmitted separately to the client.
Other ways that you could further improve CPU usage is by disabling “client side image post-processing”. This applies a filter to improve the quality of the image, but consumes more CPU. This is one feature which I am sure other remote access products don’t have.
