LAN PCs show as available, but cannot be connected

[fisherman]

NoMachine does the NoMachine server out-of-the-box firewall rules and assign them to the Firewall Profile “ALL”. Profile ALL is group of all Networks ( DOMAIN, PRIVATE, PUBLIC ) you can get more information from Microsoft website.

Please send us client and server logs to allow us to fully understand if problem is related to our software or something with your firewall setup.

[Eugene]

Here is the log from the failed connection.

Attachments:

1. Desktop-home-Windows-10-2021-11-25-16.22.31.zip

[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!

[Author]

Posts