Forum Replies Created
-
Posts
-
We would need to see the logs again to investigate this new problem. We would need them from both server (https://knowledgebase.nomachine.com/DT11R00182) and client side (https://knowledgebase.nomachine.com/DT11R00181#2). Thanks!
Hi,
that is already possible. Please check this article on how to enable it:
Hi ToastyMarshmallow,
it looks like you have another service listening on port 4000, the same used by the NoMachine server by default, and that’s why the server can’t start up. To check what is the service that is keeping port 4000 busy, you could run:
sudo netstat -l -p | grep 4000You can then stop that service or change its port. Alternatively, you can change the port the NoMachine server is listening on. You can do that in the Server settings -> Ports panel.
That said, we noted that the problem is not reported clearly in the logs. We’ll have that fixed. Thanks!
Hi,
sorry for the huge delay in gettin back to you. Probably the left Windows key is intercepted by the local window manager, despite the fact you selected, as I assume, the ‘Grab the keyboard input’ option. This option enables the so-called ‘passive grab’ of the keyboard, but it is also possible to enable the ‘active grab’. In order to try this, please quit the NoMachine player application completely (you can do this from the NoMachine icon in the tray) and start it again from the terminal using the following command:
/usr/NX/bin/nxplayer --activegrabLet us know if this solves your problem.
Hi Vincent,
there is not a native build for M1 yet, but we are working on it and it is in testing phase.
In our labs, however, we can use both hardware and software H.264 decoding on M1 machines with the current packages, and there is no known problem with it, so it would be interesting to take a look at your logs (client and server side). You can find instructions in https://knowledgebase.nomachine.com/AR10K00697 and you can send them to forum@nomachine.com.
Hi,
what you describe is likely a driver issue. Just to exclude a possible culprit, please try to disable hardware encoding on the server (Server preferences -> Performance) and see if the issue persists.
If disabling hardware encoding doesn’t help, it would be nice to take a look at the logs. You can gather them following the instructions in https://knowledgebase.nomachine.com/DT11R00182 and send to forum@nomachine.com.
Hi Stefano,
I checked the logs. Both sides of the connection report the same thing: no data is received from the network, and eventually connection drops. It doesn’t look like a problem in the software, but rather a network issue.
Were you connecting successfully before updating the uuid?
In order to know what’s going on, we would need to see the server side logs. You can find instructions in https://knowledgebase.nomachine.com/DT11R00182. You can send collected logs to forum@nomachine.com, by referencing this thread.
From what you say in point 2, it’s very likely a problem with permissions, so I’m afraid you have to access physically that Mac Pro and grant them. Here you can find some further hint: https://knowledgebase.nomachine.com/AR09S01139. In some cases, after a OS update, it might be necessary to remove (uncheck) the permissions and grant again.
Hi Stefano,
can you send also server side logs? You can follow the instructions in https://knowledgebase.nomachine.com/DT11R00182. If you prefer, you can send them to forum@nomachine.com.
Hi,
since the two machines are clones, I assume that they share the same uuid. You should execute the following in one of them:
sudo /usr/NX/bin/nxserver --shutdown sudo rm -f /usr/NX/etc/uuid sudo /usr/NX/bin/nxserver --startupHi.
I can see it move over the login screen, but I can’t click in anywhere.
Do you mean that you can see the cursor moving on the actual MacBook’s display, when looking at it locally?
Can you try to disable and re-enable privacy permissions for ‘NoMachine’ and ‘nxnode’ in Security & Privacy -> Accessibility.
Does the issue persist if you reboot the MacBook?
Hi,
assuming you’re running a NoMachine virtual desktop, you can enable VirtualGL support. Please check this article:
Hi,
we got this problem before. We investigated and excluded it was a NoMachine issue, but it was rather an issue related to the RANDR X server extension. No Trouble Report exists for this problem and that was a mistake. This issue is annoying and a TR would have been useful as a reference for anyone reproducing it. When the lag occurs, do you experience the same lag on the local, physical machine?
From the investigations we found that applying a resize of the screen of the desktop, using the RANDR X extension, resolved the problem. I don’t remember if applying a resize with the same size the desktop already had made the trick, but you can try it yourself. To try this, open a terminal and use the xrandr command to list the available resolutions (‘xrandr -q’), then set one of them (‘xrandr -s WxH’). This should clear the lag. Another thing we could do is sending a fake input event at intervals to prevent the screen from going to sleep, but this can be obviously annoying, for the user, that would never get its screen into sleep.
BTW, are you using an NVidia graphic card? Are you using the NVidia proprietary graphic driver? Because also these two X driver’s bugs can apply:
https://askubuntu.com/questions/1053973/mouse-cursor-lags-behind-after-screen-lock-user-switching
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1757202