Forum Replies Created
-
Posts
-
When you say remote machine, are you referring to the server side?
Can you show us a screenshot of what you are seeing?
What options in Display are enabled/disabled? (Ctrl-Alt-0 -> Display)
We got the image thanks.
Do you have “Scale to window” disabled (submit a screen of the session menu, Ctrl-Alt-0 -> Display)?
Hi, we don’t currently have a license management product. In the future, we will be bringing license management and reporting to the server side, so this will allow customers to keep track of what is in use and what isn’t. We can’t provide an ETA at the moment.
Linking here the original topic https://forum.nomachine.com/topic/client-on-debian-bullseye-aborts-on-connect
For the NoMachine logs, on the device you are connecting from:
– launch the NoMachine UI on the user’s computer from Programs or Menu
– click on Settings -> Player -> Security
– check Don’t delete log files on exit option
– Connect to the server and reproduce the problem.
– Compress the user’s home/.nx directory containing logs.
– Send the compressed logs archive to NoMachine Support Team by e-mail.On the Raspberry Pi server side, please see https://kb.nomachine.com/DT07S00243.
Also submit the journalctl from the server side as well.
– NoMachine product and version on local and remote machine (free version, Workstation, etc).
– Is the flickering happening with other applications?
– What’s the content of the browser when you observe the flickering? (e.g are you watching a video, is it a regular web page, something else?)
Logs were not useful unfortunately. It seems to be more of a problem with the VM and not NoMachine. We have not noticed similar behaviour during tests (and we test with multiple hypervisor solutions).
Thanks for your contribution. It confirms what I previously wrote. This topic is now going to be closed.
The log you sent is not complete. A full set of logs is required. Please follow the instructions here for the server machine: https://kb.nomachine.com/DT07S00243 and send them via email.
So, in that case, SSH jumphost support is not available. What you could try is placing Cloud Server on the jumphost server? Cloud Server can be used as a gateway to broker connections to desktops/machines that are behind the cloud server, on the corporate network. Take a look at https://kb.nomachine.com/DT06S00225. This could be an option for you if you don’t want to allow direct SSH connections.
a) machine sleep (stand-by) or display sleep. It’s hard to say
Knowing this, though, is important. You could try to see if disabling the automatic suspension and leaving only the “Display sleep” enabled helps or changes anything. Configuring your OS that way should permit the display to wake up when an event is received from the Player.
Thanks for letting us know. This confirms that it’s not a NoMachine issue. You might be interested in reading this post by another user, related to nvidia drivers from Ubuntu.
The logs you attached are from the server, though it’s not clear if you took those from the Ubuntu machine or the Windows client.
We need to see the Player logs from the Window client. Please see the section “Fourth Step: Collect Client Side Logs” in https://kb.nomachine.com/DT07S00243. Attach them here or send them directly to forum[at]nomachine[dot]com.
Thanks
Thanks SparkleCoder for your contribution!
We’ll make sure we reference your post if others come with the same issue 🙂
When connecting to the remote desktop, the general consensus is that as many keys as possible are captured to be used in the remote desktop session. What you could do, when you have the session open, is open the menu (Ctrl-Alt-0). No keys are forwarded to the remote session when the menu is open. So, activate the menu, continue with your local desktop activity using the media keys. You can press Esc in the session to bring back the remote desktop.
HI,
are you using the latest version of NoMachine on both client and server sides? What NoMachine products did you install? Is it the latest version of Manjaro?
Can you send us the logs? Please follow the instructions here: https://kb.nomachine.com/DT07S00243 and send both player and server side logs to forum[at]nomachine[dot]com. Thanks!