Forum / NoMachine for Windows / Problems connecting through my NAT router
Tagged: connection win11 wan
- This topic has 1 reply, 2 voices, and was last updated 7 months, 3 weeks ago by Britgirl.
-
AuthorPosts
-
May 2, 2024 at 23:37 #48003professorkParticipant
I have my NoMachine Windows 11 machine in my DMZ. I have opened port 4000 for TCP and UDP.
When I try to connect from outside my LAN it fails with the following log:Info: Starting NoMachine version 8.11.3.
Info: Loading settings from ‘C:/Users/xxxxxxx/.nx\config\player.cfg’.
Info: Loaded translation files for ‘English’.
85924 41452 2024-05-02 18:25:41 574.619 Main: Creating the client session.
85924 41452 2024-05-02 18:25:41 574.619 ClientSession: Initializing session at 0x0000000003dfa220.
85924 41452 2024-05-02 18:25:41 645.859 ClientSession: Initialized session at 0x0000000003dfa220.
85924 41452 2024-05-02 18:25:41 647.868 ClientSession: Starting session at 0x0000000003dfa220.
85924 41452 2024-05-02 18:25:41 650.882 ClientSession: Going to start session ‘C:\Users\xxxxxxx\OneDrive – xxxxxx.edu\Documents\NoMachine\CohServer.nxs’.
85924 41452 2024-05-02 18:25:41 664.382 Connection: Initializing connection at 0x0000000006c91bb0.
85924 41452 2024-05-02 18:25:41 666.382 Connection: Initialized connection at 0x0000000006c91bb0.
85924 41452 2024-05-02 18:25:41 666.382 Connection: Starting connection at 0x0000000006c91bb0.
85924 41452 2024-05-02 18:25:41 666.382 ClientDaemonConnector: Starting a new connection to host ‘cohserver.xxxxx-xxxxx.com’ on port ‘4000’.
85924 41452 2024-05-02 18:25:41 667.382 Connection: Started connection at 0x0000000006c91bb0.
85924 41452 2024-05-02 18:25:41 674.897 ClientSession: Started session at 0x0000000003dfa220.
Info: Slave server running with pid 66912.
Info: Listening to slave connections on port 56213.
85924 41452 2024-05-02 18:25:41 683.945 Main: Entering the GUI event loop.
Info: Connection to 100.111.11.161 port 4000 started at 18:25:41 734.031.
85924 182700 2024-05-02 18:25:42 896.654 ClientSession: A valid certificate for this server was found.
85924 41452 2024-05-02 18:25:47 919.472 ClientSession: Going to query the server for available services.
85924 41452 2024-05-02 18:26:09 530.611 Connection: WARNING! Ignoring the I/O error and waiting for the daemon error reporting.
Info: Connection to 100.111.11.161 port 4000 closed at 18:26:09 530.611.
85924 41452 2024-05-02 18:26:09 530.611 Connection: Connection at 0x0000000006c91bb0 failed.
85924 41452 2024-05-02 18:26:09 530.611 ClientSession: Runnable at 0x0000000006c91bb0 caused the session at 0x0000000003dfa220 to fail.
85924 41452 2024-05-02 18:26:09 531.109 ClientSession: Failing reason is ‘The connection with the server was lost’.
85924 41452 2024-05-02 18:26:09 533.610 ClientSession: Stopping session at 0x0000000003dfa220.
85924 41452 2024-05-02 18:26:09 536.110 ClientSession: Destroying display client.
Info: Slave server running with pid 82528.
Info: Listening to slave connections on port 30656.
85924 41452 2024-05-02 18:26:09 551.110 Connection: Stopping connection at 0x0000000006c91bb0.
85924 41452 2024-05-02 18:26:09 551.110 ClientDaemonConnector: Stopping the current connection.
85924 41452 2024-05-02 18:26:09 551.609 Connection: Stopped connection at 0x0000000006c91bb0.
85924 41452 2024-05-02 18:26:09 562.610 ClientSession: Stopped session at 0x0000000003dfa220.
May 7, 2024 at 08:54 #48050BritgirlKeymasterYou’re reaching the remote machine but for some reason the connection is being closed. When you installed NoMachine on Windows, did you reboot the machine? Is it possible for you to make a quick test whilst on the same LAN as the computer you’re trying to reach?
In any case, logs from both sides (client and server) would be useful. For Windows, run
%ALLUSERSPROFILE%\NoMachine\nxserver\nxserver.exe --debug --enable all
in a cmd console run as administrator.
Reproduce the problem (connect from whichever client it is)
Then gather the logs.
%ALLUSERSPROFILE%\NoMachine\nxserver\nxserver.exe --debug --collect
The log archive is created in
%PROGRAMDATA%/NoMachine/var/log/archives
On the device you are connecting from, depending on the OS follow the instructions here, btw you didn’t mention the client-side OS):
Fourth Step: Collect Client Side Logs
https://kb.nomachine.com/DT07S00243 -
AuthorPosts
This topic was marked as solved, you can't post.