nomachine error 138 no conecta a xp home

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.

0: NoMachine is disabled from automatically controlling firewalling of its services and Firewall must be configured manually.1: NoMachine is enabled to automatically control the firewalling of its services.The NoMachine configuration option for controlling the firewalling of its configured servers is EnableFirewallConfiguration. So how can you control NoMachine ports on Firewall?Īccording the NoMachine configuration file, usually, BaseDirectory/etc/server.cfg, the NoMachine server automatically configures the firewall for all of its configured services. Now, try to test the connection to NoMachine server port nc -vnz 192.168.57.26 4000 (UNKNOWN) 4000 (?) open 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

Nomachine error 138 no conecta a xp home