#Nomachine nx password#

You might need to enable password login into SSH.

Sudo mv /usr/NX/home/nx/.ssh/authorized_keys2 /usr/NX/home/nx/.ssh/authorized_keys -Īdditional Potential Steps for Consideration Sudo chmod 0644 /usr/NX/home/nx/.ssh/authorized_keys2 With the default Ubuntu SSH setting this is not neccessary, but someone might have changed it to e.g.: authorized_keys Sudo cp /usr/NX/home/nx/.ssh/authorized_keys2.tmp /usr/NX/home/nx/.ssh/authorized_keys2Ĭheck that the name conforms to the filename given in the /etc/ssh/sshd_config file. Sudo rm /usr/NX/home/nx/.ssh/authorized_keys2 Sudo cp /usr/NX/home/nx/.ssh/authorized_keys2 /usr/NX/home/nx/.ssh/authorized_keys2.tmp Amazon ec2, then NX's hard link between authorized_keys2 and the default.id_dsa.key will create problems when bundling AMIs.

Change the owner of the nx user public key on the server sudo chown nx:root /usr/NX/home/nx/.ssh/authorized_keys2.

Regenerate new SSH key for NX user as the default is common for all others sudo /usr/NX/bin/nxserver -keygen.

First copy it, otherwise it will be deleted after the importation). WARNING: Don't directly import the file /usr/NX/etc/keys _dsa.pub.

Import localhost key sudo cp /usr/NX/etc/keys/_dsa.pub /tmp/_.

This is OK, but if you want added security, generate your own unique key as follows.Ĭaveat: You'll have to modify your NX client wherever you're connecting from to use the custom key.

#Nomachine nx install#

Install the packages all at the same time: client, node, server sudo dpkg -i nxnode_3.5.0-3_b nxserver_3.5.0-4_b nxclient_3.5.0-7_bīy default, the SSH key is a shared key amongst all NX clients.Launch Ubuntu desktop or the server edition and install ubuntu-desktop sudo aptitude install ubuntu-desktopĭownload the Nomachine NX packages for Ubuntu ( ) (versions as of ) wget.Setting up Nomachine NX packages on Ubuntu is now quite easy: Additional Potential Steps for Considerationīeware that the following packages are not free but if you're facing problems with the freeNX packages, it may be a good solution:.

#Nomachine nx drivers#

After setting up the Ubuntu system as similarly as possible to the Debian system and letting the proprietary nvidia drivers auto install, nomachine connected at the same resolution and worked perfectly, without the lag in small screen areas. In my specific case, I needed GUI access on the server at times so I couldn't use the above methods, and I could not remedy the problem with Debian, so I wiped the system and installed Ubuntu 20.04, which is more forgiving with graphics drivers and monitors. The solution to this exact problem would be to disable the GUI and force a virtual session, per (dummy dongles won't work because the laptop's main display is not a standard plug). The Debian X-server may have been confused as to whether it was headless or not and caused issues with nomachine (which tries to detect headless and start a virtual session).

The server machine is a laptop with a broken main screen (but with an HDMI external monitor plugged in).

An issue with the Debian install of the nvidia drivers.

(OP): Based on a night of troubleshooting, the issue seemed to be either:

#Nomachine nx update#

Is there a way to get nomachine to update all the screen all the time, or at least better refresh small areas like a terminal caret? Both machines are nicely spec'd (client has 16G / RTX2080, server has 32G / GTX1080) Yes I can make dragging a quarter-screen-sized terminal window smoother, but that doesn't help me follow the caret in vi/vim. Nothing seems to change this specific issue. I have tried changing speed vs quality slider, resolutions, swapping from h264 to VP8, etc. You inevitably miss a character or so or lose your place). If I edit a text file in vi and move up and down, the caret will only update visually every other line or so (verified on the physical screen it is moving correctly). I disabled caret blink (using universal access / accessibility settings) so the caret is a solid block in terminal / vi. I have a dedicated gigabit connection between the two machines with no other traffic on that line, so bandwidth is not an issue. The same issue is less noticeable with right click menus and other areas of 'visual updates in small screen space.' If this were another remote desktop vendor I would try to find the 'don't update just regions' setting to force the entire display to update regularly, but I can't find similar settings for nomachine. I do a ton of work in the terminal and when viewing desktop via nomachine, the terminal caret is randomly not visible.

#Nomachine nx windows 10#

Host machine: Debian 10 running NoMachine 7.2.3Ĭlient: Windows 10 running NoMachine 7.2.3įullScreen / Scale to Window / Desktop is currently 2560x1440 (reduced from native while testing this issue)