Forum Replies Created
-
Posts
-
Hi Sean,
NoMachine will always use the same GPU used by Windows to render the desktop. To use the Nvidia GPU you should configure the system to do so. Similarly, NoMachine will offer the same resolutions made available by Windows (depending on the graphics card and drivers). In case the Windows machine you connect to is headless, that could be a reason why the set of resolutions is limited.
Hi,
please try to add the following key in the /Applications/NoMachine.app/Contents/Frameworks/etc/node.cfg file on the server machine:
DisplayServerExtraOptions "-oldeventapi 1"Restart NoMachine and see if anything changes.
Hi,
I assume the Mac with the 2 monitors is on the server side. Can you show a screenshot of the Display settings panel of the session menu (the one you can see here: https://www.nomachine.com/DT10O00158&dn=menu%20panel#5.7)?
Hi,
sorry for the delay. Did you also try to enable VirtualGL as suggested in one of the articles? More information about it here: https://www.nomachine.com/AR05P00982.
Can you send logs from both the server (https://www.nomachine.com/AR10K00697) and the client (https://www.nomachine.com/DT10O00163#2)? You can send them to forum[at]nomachine[dot]com.
Hi Steve,
there is no option to disable encryption. Also compression can’t be disabled completely, but I’d strongly recommend to use NX compression anyway, as it is aware of the type of content trasported and thus it is much more efficient (and effective) than a general purpose compressor.
Hi,
this is really strange even on a headless server. Please gather server side logs as explained in https://www.nomachine.com/AR10K00697. You can send them to forum[at]nomachine[dot]com.
Hi,
the display service on the server can’t start up because it cannot find any free TCP port in the given range. This range can be modified to avoid conflicts with other applications as explained at point 6 of the following article:
https://www.nomachine.com/AR11L00823
However the fact that all those ports are unavailable is abnormal and it should be checked if there is an application that is misbehaving. You can see yourself what are the busy ports in the nxserver.log file:
2020-09-28 11:40:57 903.811 29296 NXNODE TCP port '7002' is used by another application. 2020-09-28 11:40:57 905.853 29296 NXNODE TCP port '7003' is used by another application. [...] 2020-09-28 11:40:58 376.810 29296 NXNODE TCP port '12200' is used by another application.To check what application is keeping those ports busy you may try one of these methods:
Just to be sure that it is not related to a Cinnamon issue, can you tell us if restarting the NoMachine server only (without rebooting the machine) is enough to fix the problem? Also logs could be useful to understand better what is happening (https://www.nomachine.com/DT10O00163#1). You can send them to forum[at]nomachine[dot]com.
Hello,
should the problem happen again, please gather server side logs as explained in https://www.nomachine.com/AR10K00697. You can send them to forum[at]nomachine[dot]com.
Hi,
please collect the logs from the server (https://www.nomachine.com/AR10K00697) and the client (https://www.nomachine.com/DT10O00163#2). You can send them to forum[at]nomachine[dot]com.
Hi Karl-Peter,
do you have a high resolution monitor attached to the Pi (e.g. 4k) and you run the NoMachine player fullscreen or maximized? Does performance depend on the NoMachine window size (i.e. does it get significantly better if you reduce the player window to a smaller size)?
Hi,
in order to exclude any networking issue, can you try to lower Display quality to the minimum level (slide bar on the leftmost position) and uncheck ‘Disable multi-pass display encoding’? Then I would also try to disable UDP.
Is the server headless? If so, is there any chance you can attach a monitor there and see if anything changes?