Forum / NoMachine for Windows / Blocked by firewall or NAT blocking incoming traffic
- This topic has 1 reply, 2 voices, and was last updated 4 years, 4 months ago by  Carin. Carin.
- 
		AuthorPosts
- 
		
			
				
June 26, 2021 at 09:39 #34203 AreeenParticipant AreeenParticipantI am getting the following error while connecting remote desktop. A connection timeout has occurred while trying to connect to ‘100.96.227.49’ on port ‘24044’. 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. Below are the connection logs… Could you please help someone to clear this issue. Info: Starting NoMachine version 7.6.2. Info: Loading settings from ‘C:\Users\HP\.nx\config\player.cfg’. Info: Loaded translation files for ‘English’. 148 16124 12:50:32 704.432 Main: Creating the client session. 148 16124 12:50:32 720.060 ClientSession: Initializing session at 0x016ce000. 148 16124 12:50:32 902.386 ClientSession: Initialized session at 0x016ce000. 148 16124 12:50:32 909.083 ClientSession: Starting session at 0x016ce000. 148 16124 12:50:32 909.083 ClientSession: Going to start session ‘C:\Users\HP\Documents\NoMachine\Connection to 192.168.1.102.nxs’. 148 16124 12:50:32 955.944 ClientThread: Creating new thread. 148 16124 12:50:32 955.944 Connection: Initializing connection at 0x0510fc50. 148 16124 12:50:32 971.569 Connection: Initialized connection at 0x0510fc50. 148 16124 12:50:32 971.569 Connection: Starting connection at 0x0510fc50. 148 16124 12:50:32 971.569 ClientDaemonConnector: Starting a new connection to host ‘100.96.227.49’ on port ‘24044’. 148 16124 12:50:32 971.569 Connection: Started connection at 0x0510fc50. 148 16124 12:50:32 987.193 ClientSession: Started session at 0x016ce000. Info: Slave server running with pid 7380. Info: Listening to slave connections on port 49335. 148 16124 12:50:33 018.460 Main: Entering the GUI event loop. 148 16124 12:51:02 986.107 Connection: Connection at 0x0510fc50 failed. 148 16124 12:51:02 986.107 ClientSession: Runnable at 0x0510fc50 caused the session at 0x016ce000 to fail. 148 16124 12:51:02 986.107 ClientSession: Failing reason is ‘A connection timeout has occurred while trying to connect to ‘100.96.227.49’ on port ‘24044’. 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.’. 148 16124 12:51:03 001.731 ClientSession: Stopping session at 0x016ce000. Info: Slave server running with pid 10808. Info: Listening to slave connections on port 63525. 148 16124 12:51:03 048.588 Connection: Stopping connection at 0x0510fc50. 148 16124 12:51:03 064.210 ClientDaemonConnector: Stopping the current connection. 148 16124 12:51:03 064.210 Connection: Stopped connection at 0x0510fc50. 148 16124 12:51:03 126.708 ClientSession: Stopped session at 0x016ce000. June 29, 2021 at 09:48 #34242 CarinParticipant CarinParticipantHi Areeen, It looks like this is an issue related to your network configuration. You can take a look at this article to help you check your network settings How to connect to NoMachine when the server is behind a NAT router or a firewall 
- 
		AuthorPosts
This topic was marked as solved, you can't post.

