Britgirl

[Britgirl]

Joseph, we did not receive any attachments from you. Could you send them again?

[Britgirl]

Thanks for letting us know, but we would still like to investigate some more, if you are available 🙂 in order to make sure that NoMachine is working correctly and to see what improvements could be made. For example, improving printed messages to inform the user.

What we would need ideally is the debug logs from the server-side.

1. In a console, enable nxserver debug (you check for detailed instructions for your OS here: https://knowledgebase.nomachine.com/DT11R00182)

# /etc/NX/nxserver --enable server --debug 
NX> 900 Debug mode enabled for: server

2. Restart nxserver:

# /etc/NX/nxserver --restart

3. Fetch upnp status:

# /etc/NX/nxserver --upnpstatus

4. If no port mapping is shown, please start port mapping by hand:

# /etc/NX/nxserver --upnpmap

After which you should gather the logs and send to us at forum[at]nomachine[dot]com.

[Britgirl]

Can you also tell me the following?

– the router model
– what the exact full output of --upnpstatus and --upnpmap is when you execute those commands?
– which NoMachine product you have installed on the computer you are connecting to?

[Britgirl]

Ok Alex, thanks for letting us know 🙂

[Britgirl]

Hi, did you already follow the instructions here?

How to connect over the internet to NoMachine behind a NAT router
https://knowledgebase.nomachine.com/AR10R01099

[Britgirl]

(although no password is set on this machine but that doesnt stop me connecting to another machine without a password)

Something I missed is what you wrote just above. This might be an important factor here. Please see here: https://forums.nomachine.com/topic/access-windows-pc-that-doesnt-have-password

[Britgirl]

Hi, NoMachine is compatible with Windows 11. Out of interest, did you also try connecting from a different client-side computer to this Windows 11 host?

We aren’t aware of similar problems with this version, so the best thing is for us to check the logs of the affected Windows 11 host. Can you follow the instructions here and then send the logs you extract via email to forum[at]nomachine[dot]com? Just put the topic title in the subject of your email. Thanks!

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

[Britgirl]

Can you provide some more details about your environment? For example, do the 10  RPIs have different IP addresses?

[Britgirl]

Hi, the attachments didn’t attach correctly. Could you send them direct so I can attach them separately? 🙂 Just send them to forum[at]nomachine[dot]com and use the topic title as the subject. Thanks!

[Britgirl]

Thanks for bringing this to our attention. We’ve now updated the article with the additional information and feedback you provided, so thanks again for pointing this out. As soon as we’ve added support for VA-API, we’ll update the article again to make this clear.

[Britgirl]

Can you send us the $HOME/.nx directory from the server side? They are missing from the logs that you sent.

[Britgirl]

We got your logs and extra info. Thank you!

[Britgirl]

In order to understand the complete context can you tell us exactly how you are using NoMachine? You mention context-switching, can you give some more details?

Btw, with a subscription you are entitled to open a support ticket from your customer area, and as a Premium you have a response time of four business hours. You can submit tickets by logging on here: https://www.nomachine.com/support and scrolling down to Customer Center 🙂

[Britgirl]

Eugene, the logs were incomplete. We need them from the computer which you are connecting to, the server side and the debug logs from the client-side computer you are connecting from. Please follow the instructions from this document on the computer you are connecting to (the server side):

First Step: Enable Debug Level on the Problematic Host
https://knowledgebase.nomachine.com/DT11R00182#1

I will paste it here:

To enable debug 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

Second Step: Connect and Reproduce the Problem

Be sure that the Don’t delete log files on exit checkbox is selected in the client user’s interface in the Settings -> Security panel of your client-side computer.

Third Step: Create the Log Archive

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

The log archive is named as: NoMachine-log-.zip (e.g. NoMachine-log-2018.09.27-11.44.01.zip) and stored in: %PROGRAMDATA%/NoMachine/var/log/archives on Windows 10, 8.x, 7 and Vista or in Documents and Settings/All Users/NoMachine/var/log/archives Windows XP.

Send both sets of logs as attachments to forum[at]nomachine[dot]com. Thanks!

[Britgirl]

Thanks for submitting this to our forums! Other RPi users could find it extremely useful 🙂

[Author]

Posts