Britgirl

[Britgirl]

Just to answer your questions from your last reply.

We are not sure if we need to /etc/NX/nxserver --virtualgl no  since we added those DesktopCommands, so we tried it both ways (/etc/NX/nxserver --virtualgl yes   and   no

Use  /etc/NX/nxserver --virtualgl yes only. Setting it to ‘no’ would just disable VirtualGL

 

Added both the following in /usr/NX/etc/node.cfg
DefaultDesktopCommand “/etc/gdm/Xsession ‘env XDG_SESSION_TYPE=x11 /usr/NX/scripts/vgl/vglrun gnome-session –session=gnome'”
CommandStartGnome “/etc/gdm/Xsession ‘env XDG_SESSION_TYPE=x11 /usr/NX/scripts/vgl/vglrun gnome-session –session=gnome”

It’s not necessary to insert vglrun. You could try with

DefaultDesktopCommand "/bin/dbus-launch --exit-with-session gnome-session --session=gnome --disable-acceleration-check"

[Britgirl]

Hi, this feature is planned for the first release of version 8, which is in its final stages of development.

[Britgirl]

A shared drive will show up like in the last image of the tutorial here: https://www.nomachine.com/accessing-files-on-local-or-remote-disk-drives. It appears as a folder, in our case “My office documents”.  We checked on our Windows machines in our lab and were able to share. Can you show us a screenshot, if possible, of what you see when you open the explorer?

[Britgirl]

Please update to the latest released. NoMachine 7.9.2 fixes the TR referenced in this thread.

[Britgirl]

This topic is related to the issue found here and a fix was officially released in verison 7.9.2 https://knowledgebase.nomachine.com/TR02T10484

[Britgirl]

Thanks for confirming that. Here is the link to the Trouble Report which you can use to monitor when a fix has been officially released.

https://knowledgebase.nomachine.com/TR03T10492

When we have a final fix ready, we’ll send you a patched software package to download and use until the official fix is released.

[Britgirl]

Hi, updating NoMachine for it then to stop working is certainly not the correct behaviour.

Just so that I understand properly, have you updated NoMachine on your Ubuntu server and the nxserver has stopped working? So for example, you updated to 7.8.2 last month and it stopped working, you also updated to 7.9.2 and it stopped working? On both these occasions did you check in Settings -> Server that the nxserver had stopped and you restarted it?

….that it only works on newest versions

I’m not sure if you mean with “versions” if you are referring to the NoMachine software or the Linux distro you are using. If you are referring to the newest version of Ubuntu, NoMachine software is also supported on Ubuntu on much earlier versions than the one you are using. If you were referring to NoMachine software, whilst we recommend that users keep both client and server-side software version-aligned, this doesn’t mean that for your Windows 11 client to connect to your Ubuntu server, you need 7.9.2 on both sides. We always maintain compatibility between NoMachine versions, unless there is a technical reason where we recommend updating both sides.

Specifically, when I try to connect it cannot detect any displays and after continuing, shows no available desktops on this server.

So now you can’t connect at all or did you get round the problem? Can you provide more details in that case?

[Britgirl]

Thanks for the additional info. We’re glad to know you resolved the problem because so far we hadn’t been unable to reproduce the behaviour, and I was about to suggest you try with a different desktop environment such as Mate or XFCE.

[Britgirl]

This isn’t possible on Android AFAWK. As of now there is no way to grab the input of an external keyboard on Android in order to avoid some keys from being captured by the system. There are hacks out there but nothing official.  If this ever becomes possible, we’ll certainly update the application to make use of it. NoMachine allows shortcuts which are not being captured by the system. Until then, for certain key combos, users should use the virtual NoMachine extended keyboard.

[Britgirl]

Can I have a user give me access without the user knowing their IP or computer?

 

At the moment, in order to connect to a remote desktop with NoMachine, you need to know the IP hostname/address of that host.

Connecting without knowing the IP address will be possible when we release the following functionality, NoMachine Network, which is planned for version 9. You can read more about what it will offer here: https://knowledgebase.nomachine.com/FR07J02731.

The user has internet access but they can not seem to get their correct IP or computer name

Have you tried NoMachine and not been able to connect?

[Britgirl]

It doesn’t seem to be directly related to NoMachine (you say you shut down the NoMachine server).  You could try booting the host in runlevel 3. Alternatively, the nvidia forums might be able to provide some advice on those errors you are getting.

[Britgirl]

This looks similar to: https://forums.nomachine.com/topic/black-screen-no-protocol-specified-warning-failed-to-open-display-0 which was a problem with Wayland. Following the instructions in our article about headless Linux machines https://knowledgebase.nomachine.com/AR03P00973 solved the problem.

[Britgirl]

The feature you need is in the Workstation.  (It is not available in the Free Edition). You can download the evaluation from this link here: https://www.nomachine.com/download/linux&id=13

Making it possible to treat multi-monitors on the client as separate monitors in virtual desktop sessions

https://knowledgebase.nomachine.com/FR12K02799

[Britgirl]

This is identical to https://forums.nomachine.com/topic/nomachine-multi-monitor-problems. Please refer to that topic from now on. Thanks.

[Britgirl]

Can you describe your set-up and the problem? What NoMachine products and versions do you have installed.

[Author]

Posts