Forum Replies Created
-
Posts
-
Oh. OK, I found it.
Ubuntu has at least three firewall options, and I just found the third. The ports need to be opened in order for NoMachine to work.
sudo firewall-cmd –permanent –add-port=4000/tcp
sudo firewall-cmd –permanent –add-port=4000/udp
sudo firewall-cmd –reload
Since I’m just running Ubuntu out of the box (just used the defaults), I’m surprised no one else has run into this.
Might the updates to the firewall be added to the install scripts, or the install instructions?
thanks!
A little more sleuthing… the Linux host is rejecting the packets to port 4000. Enclosed is the pcap trace from wireshark. The ‘ufw’ firewall was off. I turned it on and allowed port 4000, no difference.
Thanks for the response. I’m not sure it’s the package. The logs don’t show any sort of attempted connection at all.
I looked using wireshark, and I see lots of ICMP errors when the Windows host tries to access the Linux machine.
Another data point, I can’t get the linux boxes to connect to each other either. That’s when I get the “No Route” error. From Win to Ubuntu I get a time out.
Is NoMachine using some sort of discovery protocol to find the other host, or is it going direct to TCP:4000?