Forum Replies Created
-
Posts
-
Slodi, the logs you submitted were from the connecting client only.
We need the logs from the machine that you are connecting to (server side). On the server machine (in your case Windows remote version: Edition: Windows 10 Home Version: 21H1 Build: 19043.1415), enable logs as per Fra’s instructions.
Then, start a connection from your client side Windows machine and reproduce the problem. Gather the logs from the server side
To do that on Windows, open a CMD console as administrator and run:
cd %ProgramFiles(x86)%\NoMachine\bin nxserver --debug --collectThe log archive is named as: NoMachine-log-<timestamp>.zip (e.g. NoMachine-log-2018.09.27-11.44.01.zip) and stored in: %PROGRAMDATA%/NoMachine/var/log/archives on Windows 10.
Hi, based on the logs, we need to narrow debug down further. Can you check your email inbox? We would need you to try a second debug package and resubmit logs.
This sounds more of a consultancy project and a bit out of scope of the tips and assistance that these forums can provide. It might be worth getting in touch with our support team if you have not done so already. We can keep this topic open a bit longer in case other users have have some tips they’re willing to share 🙂
Thanks for updating the topic. We did actually have a look at this problem in our labs and weren’t able to start bspwm from GDM without NoMachine involved, so it seems to be a problem with bspwm, not NoMachine.
One thing, just to start: the article you linked is a very special case. In fact it was a problem of a Windows update, not a problem with the update of the Player.
We thought it could be something strange made by the new Windows and, apparently, the NoMachine reinstall, copying and checking again its files, worked.
In your case there should definitely not be any need to reinstall NoMachine.
BTW the Player should ask if you want to update the key of the server, but it doesn’t do that. We are trying to understand what it can be, trying to reproduce the problem.
There are 3 things you can check:
1) that the NoMachine server is running on the Windows 11 host that you are trying to connect to:
open the NoMachine player > Settings > Server > Status. Does the server show as running? Are any IP addresses listed there. You can see an the example here: https://knowledgebase.nomachine.com/DT11R00177#3.1. If it isn’t, enable the server. (Btw, when you initially installed NoMachine did you restart the computer?)
2) Connecting to the localhost is an simple test to check that NoMachine is up and running correctly as well. On the Windows 11 computer, open the Player > Add connection > write ‘localhost’ in the field ‘Host’ and click ‘Connect’. A successful connection to localhost will show your desktop infinitely mirrored within the Player window.
3) If you’re connecting to the NoMachine server from a public network, verify that its public IP is visible in the list (point 1) and that your connection uses the port mapped on the router.
Some more useful tips are available here:
Thanks for posting the workaround.
(related topic https://forums.nomachine.com/topic/libreoffice-not-rendering-under-windows)
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.