Forum Replies Created
-
Posts
-
Are you trying to connect to the PIs by clicking on the list of machines that are automatically discovered on the network? In this case, the problem could be that all the NoMachine server instances share the same uuid. So you can try to create a new connection file by manually specifying the IP address of the single machines, or use the solution suggested here: https://forums.nomachine.com/topic/two-machines-using-same-advertising-information#post-36818.
Thank you for that! We checked and can confirm the fix you provided works when for that version of Fail2ban 0.11.2. We will be updating our article about Fail2ban soon (https://www.nomachine.com/AR05P00983).
Can you try and toggle NoMachine off and on again in Security & Privacy -> Privacy -> Screen recording in the macOS system preferences? And restart the server.
We’ve not been able to reproduce. We would like to send you a debug package in order to understand why authentication is failing. Would you be able to install it and send us the logs? (we’ll send you instructions).
This appears to be a problem with macOS and Rosetta, and not NoMachine. A number of Mac users have had similar issues with other applications, such as here:
Do you have the latest macOS updates installed? Restart the system and then make a clean reinstall of NoMachine.
Hi, thanks for this. We are now verifying. Do you happen to have a link to the known Fail2ban bug? That way we can link to it.
Hi Zom-B, would you also like to try the debug package for us and send us the logs from the Windows server host?
@mcvitas please check your email inbox because we have sent you details concerning the debug package.
So this was most likely to do with your system’s configuration, and not something broken in NoMachine. Thanks for letting us know.
You don’t mention what the Workstation Linux distribution is nor the Desktop Environment (KDE, Gnome, other?). Maybe these were in your previous reply as well, under ‘Desktop version’ and seems to be missing. The images you posted can be added as separate attachments (not in the body, unfortunately) Can you send them again? Also, were you able to connect to this desktop previously?
Are you the administrator of the Linux computer that you are connecting to? Please confirm the version of the NoMachine Workstation software that you have installed. Logs would be useful from the Workstation host. You can extract them using the instructions here:
https://knowledgebase.nomachine.com/DT11R00181
If you are not the administrator, please contact them and request them to open a ticket in the customer center so the support team can investigate why you are not able to connect.
Strange problem and not one we have seen in our tests.
Open a terminal on the affected host execute ‘xdpyinfo’ and ‘xrdb -query -all’ . What’s the output?
If you change the font in the NoMachine Player settings, does the problem go away?
Hi, are you using the latest version of NoMachine software? If not, I recommend you update all machines.
We would need to see the NoMachine logs of the affected Windows host as well. Please take a look at this document for instructions for Windows: https://knowledgebase.nomachine.com/DT11R00181#1.4. Enable debug ‘restart nxserver’ not the machine, connect and if there is still ‘no available’ collect logs and send to us.
Does this problem come up after changes in the user that is opening the desktop? So multiple “fast user switches”?
EDIT: This issue could possibly be related to the TR we solved in 7.8.2 -> https://knowledgebase.nomachine.com/TR05S10241.