Britgirl

[Britgirl]

Apologies, I didn’t point out that this is a global setting, and requires you to exit the Player first (Quit the player from the system tray !M icon), make the requested change and save, then re-open the Player. Can you try again?

We’re investigating it our side as well in the meantime.

[Britgirl]

Hi, no there isn’t. This is to keep the number of shortcuts to the minimum to avoid clashing with system shortcuts.
The shortcut options available (and which you can edit if you prefer) can be found in the Player settings > Input > Shortcuts.

[Britgirl]

Hi, this is a valid request for connections to the physical desktop and should be relatively easy to do, so we’ll open a feature request. Are you also handling users connecting with guest desktop sharing? Because if that’s the case, the name of the desktop owner cannot be shown for privacy reasons and so this FR will not apply to that type of user.

[Britgirl]

Is the session in fullscreen when you encounter this? When the session runs in fullscreen mode, NoMachine disables the display sleep timer in order to offer users a more comfortable experience (such as when streaming media). There’s a key that should regulate this. In .nx/config/player.cfg, can you edit the key “Turn off energy saving while in fullscreen mode” to false? Does this help?

[Britgirl]

Please execute the following on the Linux side and send us the output.

ps -aux | grep nxnode

Then read the PID

And then: cat /proc/<PID>/environ

[Britgirl]

So the computers are on the same LAN, and they can see each other.

By default, when you are prompted to input the credentials of the system account of the desktop you want to connect to, if you don’t use the same credentials as the owner of that desktop, you will need authorization of the owner. Check the NoMachine security settings on the Zorin host (Server settings > security > that the following option is enabled:

Don’t require acceptance if the user logged in as the owner of the desktop
Enabled by default. If someone is trying to connect to your desktop, a pop up message asking for your permission appears. By default such authorization is not requested if the connecting user is also the desktop owner, or if he/she is a system administrator or a NoMachine administrator or trusted user.

https://kb.nomachine.com/DT07S00237#2.5

If that option is enabled, and the balloon notification is popping up when you connect, it means you are not the owner of the desktop.

About the connection timeout issue when connecting to the Windows host,  go into ‘Edit connection’ in Machines and check what is in the host field. Are there multiple IP addresses? See here for a similar topic I answered a while back: https://forum.nomachine.com/topic/how-to-make-nomachine-update-target-computer-ips#post-39467

[Britgirl]

There are some things which are not clear:

What is the OS you are connecting from (client side)?
What is the OS you are connecting to (server side)? If the server is on macOS, confirm that NoMachine has accessibility permissions.
What is the NoMachine version you are using, client and server?

When you write “before I can access a window that responds to my mouse” do you mean you can’t interact with the server desktop through the NoMachine window?

[Britgirl]

Hi, I’ve split this off to start a new topic because you submitted it to a topic which was about macOS, so best to keep them separate.

[Britgirl]

It’s a bug on the server side, but this problem will be removed when v9 comes out. The default timeout will be 30 secs in version 9.

[Britgirl]

Yes, it seems there are a few issues with the latest Ubuntu and RPi5 (not NoMachine issues). You might also consider using XFCE instead of Gnome.

[Britgirl]

An update: we have to backtrack on what we last wrote. We thought we had reproduced the same issue, but it was a false allarm. It seems to be related strictly to Android Studio. We will keep investigating and update here if we find anything.  I imagine you’ve already tried:

– adb kill-server

-revoke usb debugging authorisation

 

[Britgirl]

Hi, you said you followed the instructions in the article about headless https://kb.nomachine.com/AR03P00973 in point 4. Executing the steps there correctly shouldn’t require any further intervention.

If you stop the display server, NoMachine should start its own virtual one. What happens when you stop the display server and restart the nxserver, and then try to connect?

You also wrote ” and after a few minutes:” What happens after a few minutes? Did you mean to attach an image or show an error maybe? Please attach it using the attach tool below.

[Britgirl]

Hmm, are you able to access and zip up the VAR folder and send it to us? (C:\ProgramData\NoMachine\…)

[Britgirl]

Hi and welcome 🙂

…there should be a timeout to close the connection if client has disappeared for (say) 60 seconds.

You’re right and there is.

Try setting the following key in node.cfg on the server side:

ProxyExtraOptions timeout=30

Something for the future, the current default timeout is too long and this will change in v9.

[Britgirl]

During tests we noticed some Xorg crashes with some specified graphic card drivers when, on proxmox, the “Default” option in “Display” settings was set. Changing it to “SPICE” stopped the Xorg crashes.

Does this help in your case?

[Author]

Posts