Forum Replies Created
-
Posts
-
Out of interest, are you able to physically set the resolution as you want it in KDE? I.e not by connecting with NoMachine?
Nothing has changed in NoMachine that would change how resolution is handled.
NoMachine client configuration let me choose several different resolutions and now it doesn’t.
Were you maybe using NoMachine Workstation in the past? This would allow different resolutions (being virtual NoMachine desktops). A note from the article I mentioned earlier: The supported resolution for virtual NoMachine desktop sessions (Terminal Server for Linux products) doesn’t depend on the remote hardware and thus the remote screen can be resized to whichever resolution is supported by the user’s local monitor.
It’s not supported. We are evaluating whether to make the ProxyJump setting possible for a future version.
Hi, when you searched the forums, did you also find the article about how to connect over the Internet? And did you follow the tips there?
How to connect over the internet to NoMachine behind a NAT router
https://kb.nomachine.com/AR10R01099“Failed to map the port on gateway” suggests that the port you used in the port-forwarding rule on your router could already already be in use. Go back to your router and change the external port number to, for example, 24222, the restart the nxserver (NoMachine settings -> Server -> Status -> Restart) or you can do it from the commandline. For safe measure also restart UPnP.
Open CMD as administrator and execute:
c:\ProgramData\NoMachine\nxserver\nxserver.exe --restart c:\ProgramData\NoMachine\nxserver\nxserver.exe --upnpmapIs it possible there is a double NAT in place? If so, you will need to map the ports on both routers. So Router A must map to Router B and Router B to the computer you want to access.
Hi, we can’t reproduce this on Ubuntu 22.04.
However, we found this which would would suggest it’s an Ubuntu bug.How to resolve no sound problem on Ubuntu 22.04
https://zcom.tech/ubuntu-no-sound.htmlMaybe this is your case?
The player window, once you’ve resized it to the size you want, should keep the same dimensions next time you start that session (using the same .nxs file).
Can you give some more details about what you are trying to achieve? You say “but I only can resize client window by mouse move,” what do you mean exactly?
Whilst we take a closer look at what possible options are available to you, I’ll explain what nxhtd is. This is the NoMachine Web Player (our web server) component which permits NoMachine server to accept incoming remote desktop connections from a browser. This is only available in the enterprise-oriented range.
I’d also like to add a note about resolution since this is what the topic was originally about. Arch and PAM problems aside 🙂 the resolution of the physical desktop depends directly on the system settings and what your graphics card supports and not NoMachine. This means that when you are connecting to the physical display, NoMachine can show you the display according to the resolution sizes available with the graphics card installed and these will show in the Display settings of the Connection Menu. In a physical desktop session, the resolution on the client cannot be changed to one that is not supported by the remote GPU. More about this is explained here:
Some tips about resize and scaling options for NoMachine remote desktop software
https://kb.nomachine.com/AR02M00835There was a similar problem with Arch and Pam a while back (desktop not showing) and there was a solution. Arch is not amongst our supported Linux, but we will do our best to provide as much help as possible to allow users to install and use NoMachine. This is the earlier topic: https://forums.nomachine.com/topic/connection-fails-on-headless-client#post-21783
Anyway, we checked on the fly to see if something had changed since then, which it has.
1. Create a backup of nx PAM configuration (sudo cp -a /etc/pam.d/nx /etc/pam.d/nx.original). Then change /etc/pam.d/nx in this way:
auth include system-login account include system-login password include system-login session include system-login2. Change DefaultDesktopCommand in /usr/NX/etc/node.cfg in order to have this on KDE case:
DefaultDesktopCommand "/usr/bin/dbus-launch --sh-syntax --exit-with-session /usr/bin/startplasma-x11"3. Stop display manager:
sudo systemctl stop display-manager4. Restart NoMachine:
sudo /etc/NX/nxserver --restartThis worked for us.
Hi, the name of the product can be obtained either by running from command line
nxserver --versionor from the /etc folder which contains the server.lic file (which will show you the name of the installed product).It was working in the morning & early afternoon and suddenly stopped working.
Please update to the latest version and if the issue reoccurs, submit the logs from the NoMachine server side. Send them to forum[at]nomachine[dot]com.
We were able to reproduce similar behaviour and have opened an internal Trouble Report for the moment. The problem appears on Squid3 configuration on newer systems (reproduced on Squid configured on Ubuntu 20.04 and Redhat 8) and can be reproduced with both NX and SSH protocols. Settings without username and password authetication work fine. The exact same Squid3 proxy with password configuration set on Ubuntu 12.04 works fine with NoMachine. The fix will be made available in the upcoming v8.