Telnet: Unable to connect to remote host: Connection timed outĪnd there you go. Test the port connection from another host not whitelisted telnet 192.168.57.26 4000 Trying 192.168.57.26. Telnet: Unable to connect to remote host: Connection timed out nc -vnz 192.168.57.26 4000 (UNKNOWN) 4000 (?) : Connection timed outĪnd you can now allow specific IPs to connect to NoMachine server.įor example, on UFW, you would simply use the command below ufw allow from 192.168.57.33 to any port 4000 proto tcp Once you have update the configuration, try to connect to the port. You can restart from the UI or restart from the command line by running the command below /usr/NX/bin/nxserver -restart Verify Connection to NoMachine Port Restart NoMachine server to effect the changes.
So now, in order to manually control NoMachine Ports on Firewall, open the NoMachine server configuration file, and update the value for the EnableFirewallConfiguration configuration option.
Sample output showing the port connections is blocked by firewall (UNKNOWN) 22 (ssh) : Connection timed out
Now, from one of the external systems, let us try to connect to SSH port to verify that UFW is running and blocking connections nc -vn 192.168.57.26 22 To confirm that UFW is running and blocking, we can try to test the connection to SSH port from a different server Ĭonfirm that the ssh service is running on a remote desktop system running NoMachine server netstat -altnp | grep 22 tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 571/sshd: /usr/sbin In my test system, UFW is running and no port is opened on the firewall ufw status Status: active
0 kommentar(er)
