Forum Replies Created
-
AuthorPosts
-
Britgirl
KeymasterWe can reproduce the problem, so we’ve opened a Trouble Report https://www.nomachine.com/TR01O07489. Please use the notify me facility to know when a fix has been released.
Britgirl
KeymasterWe aren’t able to reproduce it, so need to ask you for logs from both sides, client and server. Follow the instructions here, making sure you reproduce the error once you’ve enabled debug on the server side. Send them as attachments to forum [at] nomachine [dot] com.
Britgirl
KeymasterYes, the proper path is not being received (but this is just the tip of the iceberg) We’ll update the topic once we’ve got some more info.
Britgirl
KeymasterCan you update the player version and see whether you have the same issue? I ask because whereas we are aware of issues with files sometimes being corrupt during transfer, we aren’t able to reproduce your exact same problem..
Britgirl
KeymasterThanks for letting us know.
Britgirl
KeymasterHi, no quite the opposite π
The patch that we prepared didn’t make the release we have scheduled end of this month or February. We’re happy to send you a patched 5.1.62 for you to try like we suggested last month. Let us know.
Britgirl
KeymasterNM 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.
Britgirl
KeymasterAfter 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.
Britgirl
KeymasterJust 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.
Britgirl
KeymasterDefaultDesktopCommand β/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?
Britgirl
KeymasterFor 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
Britgirl
KeymasterLooks 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
Britgirl
KeymasterOK, we’ve received them now π
Britgirl
KeymasterThe 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.
Britgirl
KeymasterThanks 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.
-
AuthorPosts