Forum Replies Created
-
Posts
-
We 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.
Our sysadmin are on it 😉
If you need information, feel free to post a new topic on the forums. Or you can write directly to info[at]nomachine[at]com if you prefer (normally you would do this via the website on the Contact Us page, but given that it is not accessible…)
Hi, Forums and the Knowledge Base are accessible. The store and main website are temporarily offline for maintenance. If I can be of help here, let me know 🙂
Hi, can you submit the image again as a separate attachment? or send it to forum[at]nomachine[dot]com and I will upload it to your original topic. Thanks!
We aren’t aware of any issues of installing NoMachine in a VM provided the VM is running on Mac hardware. Is this your case?
macOS’s EULA doesn’t allow macOS to be installed in a VM that is not running on Mac hardware as far as I am aware. Due to these licensing restrictions it’s not possible for us to investigate installing NoMachine in VMs which are not running on Mac hardware.
After installing ‘zenity’ the update works as described. (your RPM does not mention it in its requires list)
Zenity is not a requirement for installing NoMachine hence we don’t write that is required. If it’s present on the system we use it, if it’s not present NoMachine opens the dialog to enter the password.
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.