Forum Replies Created
-
Posts
-
Hi, “reset by peer” usually means an unexpected closure on the other side. Have you updated your Ubuntu server maybe or made some other change to the system? Can you send us the logs from the server side as well? The ones you attached are from the Player. You can extract them using the instructions here: https://kb.nomachine.com/DT07S00243
Send them to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email. Thanks!
Hi, can you try the suggestion provided by Kuba last time? Try opening NoMachine with a command (/usr/NX/bin/nxplayer) and then connect to your server and check if there’s sound during the session.
Can you try to open nxplayer via terminal (run /usr/NX/bin/nxplayer) and check if there is any sound device available in the sound settings when you connect to the same server?
Hi, that article you referenced is for earlier NoMachine versions (you had to manually install a display server like Xvfb) running on headless hosts. NoMachine now ships its own embedded X server to avoid that workaround. Virtual desktop is indeed a feature of the Terminal Server products, but the free edition on Linux allows you to create a virtual display when the x server is not detected (i.e the video card is turned off or NoMachine detects that the X server is not running). The article you should be looking at is this one https://kb.nomachine.com/AR03P00973.
You say that it no longer seems to work. Are you using the latest version 8 of NoMachine? Can you tell us the exact error you are seeing?
Hi,
when prompted to log in, you should use the username and password of your account on the remote PC. No empty passwords are allowed. What is the format you are using to login? On Windows, the following are accepted:
1) User Principal Name:
<username>@<domain>2) Down-Level Logon Name:
<domain>\<username>3) Short format name, just ‘username’, domain is implicit.
See this article for more information about username formats: https://kb.nomachine.com/AR03S01118
You say that it doesn’t work. A quick way to chec is to open a CMD and type the command prompt ‘whoami’. It should return the username of your Windows account. Are you using that?
Hi, it’s possibly the lossless refinement. NoMachine’s own default settings should be suitable for the majority of environments in order to obtain optimal performance. Nevertheless, in some environments and with particular applications it may be necessary to force specific settings for fine-tuning of the performance and display quality. Try adding this option to the node.cfg file on the server side.
DisplayServerExtraOptions "-refinement 0"Does that change anything?
Hi,
please gather logs from the fedora host, following the instructions here: https://kb.nomachine.com/DT07S00243
Send them to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email.
After that please run
sudo netstat -anlp | grep eglin a terminal and show us the output.Then run
sudo /usr/NX/bin/nxserver --eglcapture yesand reboot.Do you still get the grey screen?
NoMachine works out-of-the-box with headless machines. It does this by detecting that an x server is not running and creates its own. It’s possible that you get a black screen or white screen or frozen screen on Linux when the X server is running but it is not rendering because the system’s video card is turned off (e.g you detach the monitor). In this case NoMachine doesn’t use its own virtual display because it detects that the X server is still running. You should therefore disable the x server first, restart NoMachine server, and then connect with NoMachine.
More about headless Linux hosts here: https://kb.nomachine.com/AR03P00973
To disable the X server permanently for example:sudo systemctl set-default multi-user.targetTo enable it again:
sudo systemctl set-default graphical.targetAfter disabling or re-enabling always restart the nx service
sudo /etc/NX/nxserver --restartHi,
there is a Trouble Report open specifically for Windows 11 about screen-blanking but it affects set-ups where there is a secondary monitor attached, which you have unplugged, so we’d like to investigate further.
https://kb.nomachine.com/TR05T10545
Can you send us the logs of the computer on which you are trying to blank the screen? Please follow the instructions here: https://kb.nomachine.com/DT07S00243 (enabling debug, reproducing the issue, extracting the logs from the server side).
Send them to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email. Thanks!
Check the topic here which was related to Firewalld. Not specifically for Arch but it might help?
We are still investigating but so far the error appears to be caused by dbus not returning the proper connector name for the monitor when it’s locked and put into sleep status. This then causes the issue that you are encountering and the user is unable to connect. We’ll come back to you when we have further information.