Forum Replies Created
-
Posts
-
Hi, submit those attachments to forum[at]nomachine[dot]com. Did you follow the instructions that I wrote in my earlier reply from last week?
Audio has to be enabled on the system you are connecting to (miniPC) and then from the connection menu you mute the sound on the server which appears to be what you did. Does this not mute audio on the server?
You can use
--terminateor simply--restart nxserver.Terminating the Session from Command Line
To terminate a virtual desktop or remote desktop session you can run:
nxserver --terminate SESSIONIDor:nxserver --terminate DISPLAYIDTo terminate sessions of a certain user, run instead:
nxserver --terminate USERNAMEFinally, if you want to terminate all sessions, just restart the server:
nxserver --restartor shutdown if you want to forbid new connections until the server is started again:
nxserver --shutdownHi, the free edition of NoMachine allows one connection to the remote physical desktop. If you are sitting in front of your computer and working on it locally, another user will be able to connect to it from remote in view or interactive mode (you can decide in the moment they connect). If, on the other hand, you’d like to connect remotely to your computer (one connection), another user cannot access your desktop because it would be considered two connections. In that case, you need Enterprise Desktop for Linux which will connect multiple users to the same physical display or NoMachine Workstation which lets you run up to 4 virtual desktops on the same host (NoMachine virtual desktops) and lets multiple users connect to them.
Differences between NoMachine Enterprise Desktop and the free to download NoMachine package
https://knowledgebase.nomachine.com/AR07L00808Differences between NoMachine Free Edition for Linux and NoMachine Workstation for Linux
https://knowledgebase.nomachine.com/AR10K00702In all of NoMachine products, the owner of the desktop decides if another user can connect in view-only or interactive mode is possible. You can also configure this in the NoMachine Server Settings of the computer you want to access. The guide here is useful for that: https://knowledgebase.nomachine.com/DT11R00177
For a user to connect they will need account credentials on that computer i.e username and password. With the release of version 8, in attended desktop scenarios (i.e you must authorise) it will be possible for users to connect to your desktop without requiring a system account. They will be able to connect temporarily using the Guest Desktop Sharing functionality. This doesn’t change anything in the connection count that I described above.
More information about your question is also available here in the following topics:
‘https://forums.nomachine.com/topic/run-single-client-nomachine-to-reach-many-servers ‘
‘https://forums.nomachine.com/topic/connecting-when-another-user-is-locally-logged-in ‘
‘https://forums.nomachine.com/topic/what-is-physical-desktop-and-virtual-desktop ‘Hello,
Due to changes in Windows API, we had to find an alternative solution based on a custom display driver.
We already opened a Trouble Report for this issue which you probably found linked in this forum assuming you’ve already searched as your post suggests. Maybe you already saw it? We are fully aware of the importance of having this feature and the solution will be released in version 8.
Screen blanking is no longer available on Windows 10, version 2004
https://knowledgebase.nomachine.com/TR10R09864Hi, you are using an old version of NoMachine software on the server side which is no longer supported. If you search in this forum, black screen on Linux will take you to an article about headless machines (no monitor attached). It would seem that the problem is on the server side. Perhaps you updated the OS recently?
Connecting to Linux headless machines with NoMachine
https://knowledgebase.nomachine.com/AR03P00973You don’t mention whether your server has the free version installed or if there is a Terminal Server product installed (e.g Workstation). Either way, if possible, please evaluate updating it because there have been numerous improvements since then and any investigation we carry out will only be on the latest version available to users.
Just to answer your questions from your last reply.
We are not sure if we need to
/etc/NX/nxserver --virtualgl nosince we added those DesktopCommands, so we tried it both ways (/etc/NX/nxserver --virtualglyes and noUse
/etc/NX/nxserver --virtualgl yesonly. Setting it to ‘no’ would just disable VirtualGLAdded 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"Hi, this feature is planned for the first release of version 8, which is in its final stages of development.
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?
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
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.
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?
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.
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.