Forum / NoMachine for Windows / After trial license expired, NoMachine fails to connect
- This topic has 2 replies, 2 voices, and was last updated 8 hours, 41 minutes ago by
jzeevi.
-
AuthorPosts
-
September 19, 2025 at 16:24 #54407
jzeevi
ParticipantI have used NoMachine for several years on my work laptop to get to my computers in my house (when on the same network). Recently I upgraded to the latest version with the nomachine networking. However, I do not need the nomachine networking features (yet!) so I reinstalled (the same version) but deleted my login and NM networking access.
My work laptop (from my home network) can see my home computers. It can connect to several of them, but my newest one (Win 11 Pro which was telling me my trial license expired) can be seen, but not connected to after I deleted my NM network account and removed NM (and the directory storing stuff) and reinstalled NM. I cannot see my work machine from the laptop either (anymore).
I looked at the logs for a connections and got this:
Info: Starting NoMachine version 9.1.24.
Info: Loading settings from ‘C:\Users\jzeevi\.nx\config\player.cfg’.
Info: Loaded translation files for ‘English’.
30980 31540 2025-09-19 09:29:14 416.416 Main: Creating the client session.
30980 31540 2025-09-19 09:29:14 416.416 ClientSession: Initializing session at 0x0000000003653040.
30980 31540 2025-09-19 09:29:14 523.348 ClientSession: Initialized session at 0x0000000003653040.
30980 31540 2025-09-19 09:29:14 523.348 ClientSession: Starting session at 0x0000000003653040.
30980 31540 2025-09-19 09:29:14 528.057 ClientSession: Going to start session ‘C:\Users\jzeevi\.nx\cache\349b5918-ab24-47b9-bcef-c511538a31e0.nxs’.
30980 31540 2025-09-19 09:29:14 546.724 Connection: Initializing connection at 0x0000000006b5ca80.
30980 31540 2025-09-19 09:29:14 549.769 Connection: Initialized connection at 0x0000000006b5ca80.
30980 31540 2025-09-19 09:29:14 549.769 Connection: Starting connection at 0x0000000006b5ca80.
30980 31540 2025-09-19 09:29:14 549.769 ClientDaemonConnector: Starting a new connection to host ‘192.168.44.1’ on port ‘4000’.
30980 31540 2025-09-19 09:29:14 549.769 Connection: Started connection at 0x0000000006b5ca80.
30980 31540 2025-09-19 09:29:14 555.168 ClientSession: Started session at 0x0000000003653040.
Info: Slave server running with pid 30780.
Info: Listening to slave connections on port 31387.
30980 31540 2025-09-19 09:29:14 555.168 Main: Entering the GUI event loop.
30980 31540 2025-09-19 09:29:44 552.098 Connection: Connection at 0x0000000006b5ca80 failed.
30980 31540 2025-09-19 09:29:44 552.098 ClientSession: Runnable at 0x0000000006b5ca80 caused the session at 0x0000000003653040 to fail.
30980 31540 2025-09-19 09:29:44 552.098 ClientSession: Failing reason is ‘A connection timeout has occurred while trying to connect to ‘192.168.44.1’ on port ‘4000’. The issue could either be caused by a networking problem, by a firewall or NAT blocking incoming traffic or by a wrong server address. Please verify your configuration and try again.’.
30980 31540 2025-09-19 09:29:44 555.487 ClientSession: Stopping session at 0x0000000003653040.
30980 31540 2025-09-19 09:29:44 568.022 ClientSession: Destroying display client.
Info: Slave server running with pid 28440.
Info: Listening to slave connections on port 60841.
30980 31540 2025-09-19 09:29:44 584.365 Connection: Stopping connection at 0x0000000006b5ca80.
30980 31540 2025-09-19 09:29:44 595.366 ClientDaemonConnector: Stopping the current connection.
30980 31540 2025-09-19 09:29:44 595.366 Connection: Stopped connection at 0x0000000006b5ca80.
30980 31540 2025-09-19 09:29:44 609.020 ClientSession: Stopped session at 0x0000000003653040.So, I’m very confused about what is going on and not sure how to proceed to get this new laptop “on the network”.
I’m looking for suggestions how to debug – especially given that it worked until my trial license expired (I was using NX protocol, to my knowledge, not the NM Networking protocol)
Help?
September 22, 2025 at 12:40 #54414Britgirl
KeymasterHi,
“given that it worked until my trial license expired” – are you referring to the NoMachine Network trial license (7 days)? This will have let you connect to any of your machines (once added to NoMachine Network) using their Machine Id. Now that the Network trial is expired, you can continue to use the IP address to connect to your computers as you used to do.
(Btw you didn’t need to reinstall NoMachine to remove Network-related configurations. You can disconnect the machine from NoMachine Network, that’s all. Then it stops being reachable with its Machine Id)
“not sure how to proceed to get this new laptop “on the network””
You are using 192.168.44.1 to connect, which is a LAN-based IP address, and not for external access, so we’re assuming that client and server machines are on the same home subnetwork.
First, rightclick the connection, and click ‘Edit’, open the Host combo box and verify that the selected IP address matches the subnet of the client. Another thing you can check is the nxserver is running on the computer you want to access (Settings > Server > Status). Can you show us a screenshot of the Machines and Edit panels? If you don’t wish to submit them here, you can send them via email to forum[at]nomachine[dot]com.
September 22, 2025 at 15:47 #54419jzeevi
ParticipantNot realizing initial posts are moderated, I stared at the problem a lot longer and realized that something was swapping the C and D bytes of the IPV4 address. The actual address is 192.168.1.44, not 192.168.44.1.
I’m not sure if that swapping is in the server responding to the connect request or in the NM instance requesting the connection. I did not create the connection manually, so suspect there’s some minor bug somewhere, but wasn’t sure if I should report it.
Thank you for responding. Please advise if I should create a bug report.
-
AuthorPosts
You must be logged in to reply to this topic. Please login here.