Is Using NoMachine with Port Forwarding a Security Risk?

0
4
Asked By CuriousCoder123 On

After a lot of trial and error, I finally found a remote desktop solution that works for me: NoMachine. I've successfully been able to control my desktop from my internal network, but now I want to access it remotely. Since NoMachine operates on port 4000, I set up port forwarding on my router to direct that port to my desktop's internal IP. I'm concerned about potential security vulnerabilities this might create. Is this a bad idea, and is there a safer way to achieve remote access? Thanks!

3 Answers

Answered By RustyFan92 On

I switched to RustDesk and removed NoMachine completely. It just seemed easier to set up for my needs!

LostInTechLand -

I had a tough time getting RustDesk to work, though! Any tips?

Answered By SSHmaster On

You might want to think about using SSH tunneling as an alternative. If you do this, you can port forward only the SSH port on your router, minimizing exposure. Just keep in mind that you’ll need to properly secure your SSH setup to avoid vulnerabilities.

CautiousUser99 -

But isn't setting up SSH secure enough for most users?

Answered By TechSavvyDude On

Exposing ports to the internet isn't ideal, and port 4000 could be targeted by attackers. Instead, consider using WireGuard to create a secure tunnel into your local network. This way, you connect first to your network before accessing the port. It’s a safer choice!

NetworkNinja42 -

Could you elaborate on how to set up WireGuard for this purpose?

Related Questions

LEAVE A REPLY

Please enter your comment!
Please enter your name here

This site uses Akismet to reduce spam. Learn how your comment data is processed.