Imagine the less tech-savy, how much can they expose themselves by trying to do the same, now that everyone is going online/remote.
The difficult bit is to know exactly what ports and IPs are supposed to be in Internal, External, and if it needs tcp and udp.Īnd in case of a double NAT, should both routers be configured with exactly the same forwarding? As you can see even in the link you shared, that other fellow didn’t know which ports needed to be forwarded, and therefore probably exposed himself as easy target to hackers. To me it’s not difficult to set a port forwarding and an exception in the firewall once we log in to the router. Anyway, that’s something that could be more clear in the documentation between and. But perhaps it’s my ignorance in networks/security and I didn’t get it. I removed all manual attempts of forwarding, and it works with automatic UPnP now, that I don’t have double NAT anymore.įrom the documentation, it’s really not clear to me that just by enabling EnableNXClientAuthentication, I’m actually refusing connections without a correct SSL certificate (is that even the case?!). I managed to get it yesterday, it’s all good now. So, as soon as I turned on EnableNXClientAuthentication 1 in the server.cfg, it wouldn’t connect anymore, and that apparently was the issue I was having, the SSL wasn’t properly done.
Then I decided to move forward with configuring SSL to discover at which point it stopped working. I reinstalled NoMachine over the long weekend, and succeeded on connecting over internet.
0 kommentar(er)
