Forum Replies Created
-
Posts
-
If the patched package solves the problem and the connection problems you were experiencing are no longer there (I doubt these were caused by the package), then logs are no longer necessary.
Regarding the screen blanking on Wayland, D-Bus and PipeWire must be present and properly working on the system. You should follow the tips and instructions here:
Notes for connections to Linux physical desktops running Wayland
https://knowledgebase.nomachine.com/AR02P00969Please use this link to track the progress of this bug report:
Client ignores the local cursor theme
https://knowledgebase.nomachine.com/TR02T10472We were unable to reproduce this issue. If you encounter the problem again, we will need client and server side logs.
We noticed that the permissions of /proc/net/unix are set to 400. Default on Debian 10 is 444 – did you change this by yourself or can you determine if it has been changed by some application which you are using?
Setting again permissions to 444 should fix the problem.
This looks like a permissions problem. What desktop environment is this, I can’t tell from the screenshot? Check permissions and ownership of the home directory, $HOME/Documents/NoMachine and $HOME/.nx folders.
I also have to close all 4 or 5 of the initial setup windows
This could be helpful:
https://knowledgebase.nomachine.com/DT11R00186, chapter 2.3It could be a permissions problem because logs show NoMachine doesn’t have access. What’s the output of
ls -l /proc/net/unix? Are you connecting to a physical Linux machine or is it a virtualized machine of some kind?Renaming is not only a modification to the software which would not be allowed by NoMachine’s EULA, it could also break your installation.
Send the Linux logs over so we can check. The ones you got from the Windows client didn’t attach, so send them on as well.
On the server side what’s the output of
/etc/NX/nxserver --statusin a terminal? If it’s not “started”, can you restart it with--restart? Logs would be useful if restarting doesn’t help. For logs please check this article https://knowledgebase.nomachine.com/AR07K00677 . You can send them directly to forum[at]nomachine[dot]com. Please use the title of the topic in the subject of your email 🙂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.