Forum Replies Created
-
Posts
-
It could be that port 4000 is already taken. The Network Server (nxd) listens by default on port 4000. If you have another application using port 4000, you can change it for NoMachine in server.cfg.
More about default ports that NoMachine uses is here:
https://knowledgebase.nomachine.com/AR01L00770How to solve port conflicts with other applications
https://knowledgebase.nomachine.com/AR11L00823Here I can see in the log excerpt that you are using an nx derivative which could be interfering with NoMachine. Uninstall it and then try using NoMachine. If you reproduce the same issue, we can continue this thread, with fresh logs being submitted.
Update: user confirmed that on the remote host there is no NoMachine package installed. This topic is therefore closed.
Further reference:
Supporting earlier versions of NoMachine and NX
https://knowledgebase.nomachine.com/AR07O00933Restarting the nxserver would mean you lose the logs. You would need to reproduce the problem again, and send in a new set.
It’s not clear what you want to hide from users 🙂 Do you want to disable certain services so that users cannot, for example, use file-transfer? Or do you want to not show the !M in the system tray? Or do you want to rename some nx processes?
We need logs from the server side to understand why the server is not running and therefore why you cannot enable ‘Desktop shared’. Please see here for instructions on how to extract them. https://knowledgebase.nomachine.com/AR10K00697
Send them directly to forum[at]nomachine[dot]com making sure you put the title of this topic as the subject of your email.
Also a screenshot of the Server Status. Open NoMachine, go to Settings, select Server, then Status. Thanks.
Can you show me a screenshot of the path that you are selecting in the RDM GUI? You should be selecting ‘NoMachine’ and not ‘NX Client’. An image of what you see would help to understand what you are choosing. NoMachine on the client-side starts the session with nxplayer and not nxclient.
Is it possible that you were using Plasma (Xorg) before the reset of the Linux server and now that it has been “reset” it has gone back to Plasma (Wayland)?
Disable Wayland and use x.org instead.
1. Logout from the desktop
2. Log in as Plasma (Xorg)
3. Check that you can connectIf you can’t attach them here because there are too big, you can send them to forum[at]nomachine[dot]com. Please use the title of your topic as the subject of your email. Thanks.
So it would seem a separate issue (when you are connected to the remote host and not when opening the UI), but logs will help us to understand what’s happening. Can you send the logs from the Enterprise Client host, this time following the instructions here: https://knowledgebase.nomachine.com/DT11R00181#2?
Hi, can you send us the logs of the M- directories from the affected hosts (typically you can find them in /var/NX/nx/.nx/M-* ) ?
Attach them here or send direct to forum[at]nomachine[dot]com.
Hi LorenDB, we would like to send you a link for a new package to install, and you tell us if the fix helps. Please check your inbox for direct emails from us.
We’re still not able to reproduce the problem described in this topic. We will open an internal TR so that we can track the problems that were reported. It would be interesting to know if you encounter the same behaviour with the latest 7.8.2, just for the record.
You must insert an administrator user and password to allow the update to proceed. Just like when you installed the NoMachine software, which asks for admin user and password in order to proceed with the installation, it’s the same with updating. For information about updating the software, you can check the installation guide for the product you are using (Go to nomachine.com/all-documents).
This article might also be of help to you.
How do I update NoMachine software?
https://knowledgebase.nomachine.com/AR10K00698If this doesn’t help, please tell us what you would like to know and we can check how to improve our documentation accordingly 🙂
Hi, as far as we are aware, Devolutions Remote Desktop Manager supports NoMachine sessions, including the latest version. We checked just to make sure.
Confirm what you are using with regards to NoMachine software (both client and server) and the RDM product version as well.
Additionally, please tell us the steps you are following in order to the produce the error you receive.If you are using an old version of NoMachine software, I advise you to update to the latest version. We can only provide help here for currently supported versions.