Forum Replies Created
-
Posts
-
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.We have a fix for a similar problem included in the next maintenance release which has been scheduled for next week. Looking at the errors you pasted, it is possible that this could solve your problem with Cadence. I would wait to try that first.
Hi,
I wrongly assumed you had installed the free version on the remote host you are accessing hence the suggestion to install Workstation or another product from the Terminal Server range. You didn’t need to uninstall NoMachine Workstation and then install Terminal Server, so sorry for the confusion. They both support HW acceleration in NM virtual desktop sessions provided you enable VirtualGL on the server where you have installed Workstation/Terminal Server. We checked that the extension that you highlight as important is present in VirtualGL.
Please verify that you do have VirtualGL installed and that is enabled. Prequisites are that the host machine is a physical computer and has a hardware-accelerated 3D video card, and that Xorg is up and running to use the 3D video card.
You can follow the instructions here to enable VirtualGL:
How to enable VirtualGL support on Linux in NoMachine v. 6.2 or later
https://knowledgebase.nomachine.com/AR05P00982We have reproduced this behaviour and opened a Trouble Report which you can monitor at this link:
https://knowledgebase.nomachine.com/TR03T10493
A temporary workaround is to install Zenity or Kdialog in order to browse the file system.