Britgirl

[Britgirl]

Got them thank you!

[Britgirl]

We have not received any logs 🙁

Are you able to send them again?

For the authentication failure issue it would be better to start a new topic about that with all the details and the specific error message you are getting.

[Britgirl]

Hi, I’ve just forwarded it on to you again. It was originally issued from the Forums backend. I’m not sure what happened there. Let me know that you got it.

[Britgirl]

The instructions for enabling and gathering logs manually are correct 😉

Try the shorter method “Collect server side logs automatically”

https://knowledgebase.nomachine.com/DT11R00182#1

Command nxserver --debug --enable allows you to enable debug logs for all components: nxserver, nxnode, nxwebplayer/client and the display agent in one go. It must be executed on the machine where the problem occurs. In your case, this is on the Windows machine server-side.

To do it on Windows, open a CMD console as administrator and move to the ‘bin’ folder under the NoMachine installation, e.g:

cd %ProgramFiles(x86)%\NoMachine\bin
nxserver --debug --enable all

Connect and reproduce the problem. When you’ve reproduced the issue, you then do:

cd %ProgramFiles(x86)%\NoMachine\bin
nxserver --debug --collect

The log archive is named as: NoMachine-log-.zip (e.g. NoMachine-log-2022.01.19-9.15.01.zip) and stored in: %PROGRAMDATA%/NoMachine/var/log/archives.

[Britgirl]

Hi,

it seems the Player logs were missing. And we would need to see those. In the UI on the computer you are connecting from:

– Make sure that the box to not delete log files on exit is flagged
– Connect to the server and reproduce the problem.
– Compress the user’s home/.nx directory containing logs.

[Britgirl]

Hi, this is a known issue. Please use this link to track its status:

Right mouse button doesn’t work on Android 8
https://knowledgebase.nomachine.com/TR07P08723

[Britgirl]

so I did reinstall the entire OS from scratch and installed NoMachine freshly and it works fine.

 

So it seems something was not quite right with your Arch install.  Thanks for letting us know.

 

previously I was able to set practically any display resolution for the remote server

You will find some useful tips and information here:

Some tips about resize and scaling options for NoMachine
https://www.nomachine.com/AR02M00835

[Britgirl]

Did you get the macOS prompt to approve permissions?

Try the tips in this article here: https://knowledgebase.nomachine.com/AR01P00962

If that doesn’t work, also try the procedure here as well: https://forums.nomachine.com/topic/unable-to-get-audio-working-10-14#post-34576

[Britgirl]

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 --collect

The 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.

[Britgirl]

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.

[Britgirl]

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 🙂

[Britgirl]

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.

[Britgirl]

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.

[Britgirl]

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:

https://knowledgebase.nomachine.com/AR10R01099

[Britgirl]

Thanks for posting the workaround.

(related topic https://forums.nomachine.com/topic/libreoffice-not-rendering-under-windows)

[Author]

Posts