Britgirl

[Britgirl]

Hi, before you updated the nvidia driver to the latest, with the previously installed version you were also getting the black screen, but only recently? Did something else change in your set-up since you last connected without any problem? Was the other product already installed or did you install it recently?

Can you go back to your original settings on both client and server and try again? Then take logs from the Mac client (on the client go to Settings > Security > Take logs) and the Windows server (on the server host, go to Settings > Security > scroll down and take logs) and send them to us? You can submit them here or if you prefer send via email to forum[at]nomachine[dot]com.

[Britgirl]

Glad to hear you can now connect. Thanks for letting us know 🙂

[Britgirl]

Are all these computers on the same local network or are you connecting to them from external network? We understand that connections are like this:

Win (iMac) to Main PC (Win) – not working, giving timeout error
Win (iMac) to Linux (MacAir) – ok
Linux (MacAir) to Win (iMac) – ok
Linux (MacAir) to Main PC (Win) – ?
MainPC to Win (iMac) – ok
MainPC to Linux (MacAir) – ?

It seems the problematic machine is the Windows MainPC and it’s not clear if you can connect to this machine from any of the others. Is it possible that on the MainPC there is a firewall blocking incoming connection? If you briefly disable it and then try to connect, can you?

Can you show a screenshot of the Edit panel of the connection to the MainPC?

[Britgirl]

Hi, we’ll wait for your logs. In the meantime, can you tell us if the xrandr --verbose output was captured with screenblanking enabled and during an active connection? If it was, please also submit xrandr --verbose when blanking is disabled (or when nomachine is not connected). Sorry for not specifying this earlier.

[Britgirl]

Please see my answer here: https://forum.nomachine.com/topic/screen-blanking-for-physical-desktop-but-not-virtual-2#post-55633. Virtual desktop running in the background is available in Terminal Server products.

[Britgirl]

Can you open a terminal and run the ‘xrandr --verbose‘ command on the XFCE host? Please send us this output.

Can you also send us the logs where reproduce the same issue on Ubuntu 24.04 and Wayland? That way we can compare. Send them to forum@ email address like last time. Thanks!

[Britgirl]

Thanks for letting us know 🙂

Just to clarify a question you asked:

is it necessary for me to be logged into the “nomachine” account on my computer or the computer I’m connecting to in order to be able to turn off the screen of computer “B”?

If you are referring to NoMachine account/UserId which is required when connecting over the NoMachine Network service, absolutely not, logging in to the Network service in the UI is not a pre-requisite.

[Britgirl]

Hi, please try the Workstation for Linux and see if it fits your requirements. If you create a NoMachine account, from your User Area you can generate an Evaluation license for any NoMachine product from the Enterprise family of products (Terminal Server, Enterprise Desktop and Cloud Server products).

[Britgirl]

Screen blanking blanks the physical screen, and the main physical session is on that physical screen which you just blanked 🙂 If local users want to be able to work on those Linux machines while the screen is still blanked, the product you need could be NoMachine Workstation from the NoMachine Terminal Server suite. This is a family of products available for Linux, and lets users have a physical desktop and a virtual session, one that is completely independent and with which you can interact even if the physical desktop is blanked, the physical desktop of the machine where the virtual session is running, is blanked.

Take a look at the following resources:
https://kb.nomachine.com/AR10K00700
https://www.nomachine.com/enterprise/terminal-server-products/workstation

[Britgirl]

In v9, we implemented changes to how the reconnect works. In order to add a further layer of security to the reconnection, we no longer use the user credentials, but connect and authenticate to the server through a security token. This token has a short expiration time, so when the lid is opened and the notebook system restored, the server rejects the automatic reconnection token authentication. So it’s not possible to reconnect without any user interaction. We are going to add a new key to the server which will allow the token expiry to be configured per user needs.

Please take a look at the dedicated article about how reconnection works:

https://kb.nomachine.com/AR02X01343

[Britgirl]

Hi, there is known issue on Wayland. You could try disabling Wayland and using Xorg instead to verify if it’s the same problem. Does the problem go away? Here is the link to the Trouble Report: https://kb.nomachine.com/TR08T10575.

[Britgirl]

Screen blanking is supported in all products. We are not aware of screen blanking issues when connecting to a physical desktop on XFCE. Does it also not blank screen from the !M icon of the system tray? (Desktop shared > Blank physical screen). Can you send the us the logs of the server host? Reproduce the issue again, then on the server host, go to the Server settings > Security > scroll down and click Take logs). You can attach them here or if you prefer send direct to forum[at]nomachine[dot]com. Thanks.

[Britgirl]

Hi,

from what you’ve written it seems you are activating screen blanking on the wrong side. Screen blanking blanks the screen of the target computer, the one you are connecting to. So, in your case, you have two Windows computers, let’s call them “A”, the computer you are connecting from (the “client”). And “B” the machine you are connecting to (the “server”). This means that to activate screen blanking, you must configure machine B, the server, to blank the screen.

You have two choices. You can either configure the ‘Server settings’ on machine B by enabling the box “Blank the physical screen when somebody connects” (Go to Server settings of Machine B > Security > tick the box ‘Blank the physical screen when somebody connects’. Or you can blank the screen during the session from the !M icon on the target desktop: i) start your NoMachine connection from A, ii) login to B with your system credentials, iii) go to the !M icon of the system tray on machine B, iv) click ‘Desktop shared’ and then toggle ‘Blank physical screen’.

[Britgirl]

We were able to report the issue. You can track the status of the fix using this link here: https://kb.nomachine.com/TR02X11712.
Thanks.

[Britgirl]

Unfortunately, there’s not much more we can debug. Although we would appreciate knowing if the the monitor issue disappeared when you set --eglcapture to no using the last package we provided.

[Author]

Posts