Forum Replies Created
-
Posts
-
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.
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?
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.
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.
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
This is identical to https://forums.nomachine.com/topic/nomachine-multi-monitor-problems. Please refer to that topic from now on. Thanks.
Can you describe your set-up and the problem? What NoMachine products and versions do you have installed.
Hi, I understand that scaling to 100% can be problematic for some (me included 😉 ) It’s just to see whether this stops the problem from occurring, which in our case scaling from 125% to 100% worked. If you tell us that the problem disappears when setting the scaling options to 100%, we’ll know it’s the same problem and we can then send you a patched package. Our team is already working on a fix.
If it is the same problem, setting the display scaling to 100% should be done on the computer where the menu (e.g Open menu panel or Transfer file) is not showing or not showing properly. So this would be the server-side.
Hi, we have managed to reproduce a similar problem and it was triggered by the OS’s display scaling to 125%. The workaround in our case was to switch back to 100%. Could you make sure that your Windows display is configured to scale at 100%?
Hi,
thanks for updating your topic. I’m glad to know you fixed the issue. From what you described you have a headless Linux. We have an article in our knowledge base which provides guidelines for Connecting to Linux headless machines with NoMachine such as disabling the Xserver. You can find it here: https://knowledgebase.nomachine.com/AR03P00973. If NoMachine detects that the X server is already running, it doesn’t use its own virtual display and that is what triggers the “no available desktops” message.