Forum Replies Created
-
Posts
-
What NoMachine product and version have you installed on the local side and on the remote side?
I need to know the above information so that we can understand your set-up better.
With NoMachine are you remotely connecting to the physical desktop on Windows, are you connecting to a Linux desktop? Does the middle button stop working only when you connect to the remote desktop with NoMachine?
What OS are you connecting from? What OS are you connecting to? and version?
What NoMachine product and version have you installed on the local side and on the remote side?
Was the middle mouse working in a NoMachine remote desktop session before? What might have changed, if anything, since it was last working? An update?
invanvi, it could be related to HW decoding.
Can you disable HW decoding on the client side and tell us if this changes anything? Start the session, open the connection menu Ctrl-Alt-0, Display Settings -> Advanced (click modify) and check the box “Disable client side hardware decoding”.
You can also try disabling “client-side image post-processing”.
What happens?
Hi, this is not possible I’m afraid. How NoMachine prioritizes monitors depends on how they’re set in the systems settings.
Hi
are there special rules in Active Directory for the user which is trying to connect and can’t? E.g the user needs to change password in the next login? If you send us logs from the NoMachine Windows server host where you are trying to log in, these might help. To do that you need to enable debug, reproduce the problem and zip up the logs. Please send them forum[at]nomachine[dot]com making sure to reference the title’s topic as the subject of your email. Instructions are available here: https://knowledgebase.nomachine.com/DT11R00182#2
Just to clarify because you mentioned a simultaneous connections, the free version of NoMachine permits one incoming connection. If you want unlimited connections to the desktop (and all users will see the same desktop) you need Enterprise Desktop.
At a glance, it seems like a problem with access to the local xserver. Could something have changed on the system that would trigger this? Having a look in the session directory from var/log/node/ could reveal something useful.
It’s impossible for us to know why this is happening without taking a look at the logs. First of all, I would update to 7.8.2 if possible because there have been several releases since 6.9.1 and we can’t be sure that this isn’t related to something we already fixed. If the problem is still there after updating, enable debug, restart the server and then gather the logs up. Send them to forum[at]nomachine[dot]com making sure to use the title of this topic as the subject of your email. Instructions for enabling debug are available here: https://knowledgebase.nomachine.com/DT11R00182.
What version and product of NoMachine software are you using on the Linux side?
What is the distro?
What’s the desktop environment?Is it headless? See the tips here:
Connecting to Linux headless machines with NoMachine
https://knowledgebase.nomachine.com/AR03P00973Is Wayland used?
Notes for connections to Linux physical desktops running Wayland
https://knowledgebase.nomachine.com/AR02P00969Is it a virtual machine? If so, check this article:
Connecting to a Wayland-based desktop running in a Linux virtual machine
https://knowledgebase.nomachine.com/AR04R01083Hi, we’re still working on this. We’ll update the topic once we have some news about a possible solution.
The server shouldn’t be making any sound at all whilst someone is connected to it. And from what you write, I understand this is not happening.
Please, when you’re connected to the server, open the menu with ctrl-alt-session, go to Devices, select Audio and take a screenshot and attach it here. This will show me what I indicated in my previous reply when I referred to the Connection Menu Guide, picture 18.
Also please tell me the versions of Windows both sides otherwise we won’t be able to investigate.
Just a quick update on this. We decided to order a Logitech MX Keys for Mac to investigate, which we are in the process of doing now.
The licenses cannot be stored in another location. However, upgrading /updating the software as per the documentation’s instructions is a safe procedure and does not touch the server.lic files unless users remove the entire .nx directory.
Upon connecting the person sitting in front of the computer you are connecting to should see the mouse being moved. Can you tell us a bit more about your set-up? What Windows version on the client side, what Windows version is on the computer you want to connect to remotely?
This is a functionality supported in, for example, NoMachine Workstation, of the Terminal Server range. Take a look at this page: https://www.nomachine.com/terminal-server.