Britgirl

[Britgirl]

We’re not aware of similar issues of not being able to open the app after waking the machine from sleep mode. Are you able to send us the .nx folder in the user’s home of the affected system? The steps are:

1) Reproduce the problem

2) Compress and send us the .nx folder from the user’s home. On Windows the .nx folder is hidden, so to find it write the following in the address bar or the file browser: %USERPROFILE%\.nx

3) Check the list of processes in the task manager and check how many Player processes are running, even if the UI is not visible. If there are multiple processes, can you take a screenshot and send us it together with the logs?

Send everything to forum[at]nomachine[dot]com using the title of this topic as the subject of your email. Thanks!

[Britgirl]

Hi, so you need to tell NoMachine to create its own display service (without the TV interfering), so what you could try is setting a different display in the node.cfg file of the NoMachine server host.  You can do it by editing the appropriate key, PhysicalDisplays.

In the node.cfg file (/usr/NX/etc/node.cfg) you can find:

For physical desktops, specify the physical display or range of X server displays which are made available to NoMachine connections. It is possible to specify a # single display by display number, e.g. :0, or by port, e.g. 6000.
The range of displays can be specified as a dash-separated list,  e.g. :0-:7 or, by port number, 6200-6204. By default all displays detected as running will be made available for users.

PhysicalDisplays :0

We suggest you set it to PhysicalDisplays :2.

Does that help?

[Britgirl]

Now it’s clear 🙂 I forgot to mention this article that have about headless hosts. You might find some useful information there as well: https://kb.nomachine.com/AR03P00973.

[Britgirl]

Hi, are you connecting to a Terminal Server product? We have reproduced in a custom rootless session (supported only in terminal server products)? We have not reproduced it connecting to the physical display. Please tell us what NoMachine product is running on the server side.

Update: 15/07/25 – please update to the latest version and open a new topic if you are still encountering the issue when connecting to the physical display.

[Britgirl]

Hi

On my side (server? – the machine I’m sitting at to remotely connect to the other computers – so clients?) there is no “Switch Monitor” icon. Both the NoMachine and real computers have two displays I can select from but they are not the same between the two.

First some clarification about server and client in the NoMachine model. The “server” is considered the computer that receives incoming connections, i.e the computer you are connecting to. Clients are the devices you are connecting from.

Is the server computer you are connecting to headless? In that case, NoMachine detects no physical display and so it starts a virtual desktop (which would be the correct behaviour). If the server is not headless, then NoMachine should not be starting a virtual display. In that case we need logs and with debug enabled, they will help us to understand why the server seems to be unable to detect the physical display. You can extract them using the instructions here: https://kb.nomachine.com/DT07S00243

Send them to forum[at]nomachine[dot]com or attach here. If you send them by email, please use the title of this topic as the subject. Thanks!

[Britgirl]

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!

[Britgirl]

Hi, can you try the suggestion provided by Kuba last time? Try opening NoMachine from the command line (/usr/NX/bin/nxplayer) and then connect to your server and check if there’s sound during the session.

[Britgirl]

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?

[Britgirl]

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.

[Britgirl]

We have received the logs and additional information, and will come back to you soon.

[Britgirl]

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?

[Britgirl]

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?

[Britgirl]

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 egl in a terminal and show us the output.

Then run sudo /usr/NX/bin/nxserver --eglcapture yes and reboot.

Do you still get the grey screen?

[Britgirl]

You can send everything to forum[at] like last time.

[Britgirl]

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.target

To enable it again:

sudo systemctl set-default graphical.target

After disabling or re-enabling always restart the nx service sudo /etc/NX/nxserver --restart

[Author]

Posts