Forum Replies Created
-
Posts
-
We need to see NoMachine server-side logs. These must be taken from the machine you are connecting to.
Instructions are here:
https://kb.nomachine.com/DT07S00243#2You can send them to forum[at]nomachine[dot]com or attach them here.
Please disregard my previous explanation about the bug related to smartcard forwarding. This was a misunderstanding on my part of what developers had been investigating and their findings. The Trouble Report for your issue is available at the following link:
About the TR being public, not yet, we are going to publish it soon, when it’s ready I will paste the link here.
We have a Trouble Report open in relation to forwarding smartcard which does not work correctly when the automount option is enabled. It’s caused by some changes introduced to the ssh-agent in an OpenSSH update which, in order to increase the security level, block the execution of PKCS#11 libraries not in the default path or in the verified path. Smartcard will be mounted correctly after user navigates manually to smartcard panel in the menu to add it there. Btw, general improvements to device forwarding are coming in the release of NoMachine 9, including the possibility to detect devices newly plugged in during the session.
It looks to be a known issue,
White screen occurs when connecting to a KDE/Plasma Wayland desktop on Kubuntu
https://kb.nomachine.com/TR07U10921The patch is planned for the next maintenance, version 8.12.
Our initial tests show that it’s necessary to uncomment the “DefaultDesktopCommand” key in the node.cfg.
#For GNOME session:
DefaultDesktopCommand "env XDG_SESSION_TYPE=wayland dbus-run-session /etc/X11/Xsession gnome-session"#For XFCE:
DefaultDesktopCommand "dbus-run-session startxfce4"Maybe you could try these.
The logs show that screen sharing is disabled. This suggests either that “Desktop Shared” is not enabled. You can check this in the NoMachine Server settings on the Debian host.
Or that in Security -> Desktop Access, you have unticked “Don’t allow the owner of the desktop to connect if the desktop is not shared”. Are you always connecting from remote as the owner of the desktop? By “owner”, I mean the same user account that is actually logged on the Debian server.
The free version of NoMachine supports one incoming connection to the system. Have you always been using the free version? Maybe you installed the free version thinking you were installing one of the other products?
Hi, SSH sessions are possible when the server side has a product from the Enterprise suite installed. It’s definitely possible to run an NX session through an SSH tunnel. Check out this article for the instructions:
Hi Sven, thanks for coming back with your findings and the link. This is indeed a bug with the nvidia drivers and not something that we can fix in the NoMachine software.
Hi Jon,
The free edition of NoMachine is for access to the physical display, so it’s the correct behaviour. Maybe what you are looking for is NoMachine Workstation from the Terminal Server family for Linux? Check out the differences here: https://kb.nomachine.com/AR10K00702. The Workstation is available to download here: https://www.nomachine.com/product&p=NoMachine%20Workstation.
If no input is arriving on the Mac side, it could be a simple issue of permissions not set on the macOS system during installation of NoMachine. Go to System Settings > Privacy > Accessibility and then “+” and add NoMachine. If it’s already there, remove and add it again (see this article https://kb.nomachine.com/AR11Q01061). Then connect again from Windows.
The GDM issue could be this: https://www.nomachine.com/TR07S10316.
About the blurry screen connecting from Windows (your images may be too large for our upload tool, email is best):
– Right-click the NoMachine app shortcut on your desktop and select Properties
– Select the Compatibility tab
– Click “Change high DPI settings”
– Check the box “Override high DPI scaling behavior”
– Select “Application” from the combo under “Scaling performed by”Does that help?