4 replies
by codyt8 Accepted solution
by seanferd Accepted solution
There might be something that could occur within the LAN, but that is a lower risk.
However, simply having a port open means nothing. You just don't open ports you don't use. Attackers, using nmap or not, always know your port 80, 53, etc. are always open.
Further, know the difference of a port being open on your router from a port being open on a computer. The first is internet-facing, while the latter is in your network behind the router and its firewall.
There is no inherent security risk in having any port open over another port being open, other than the fact that you are connected to the internet at all. Any real risk involving Remote Desktop is more likely to be in RDP itself, not just the port being open.
by tobif Accepted solution
I agree with all Seanferd said above, but would like to add a couple of notes.
On your router you can't have more than one forward from port 3389. If you want to open connections to several computers, then you'd need to move the RDP client to a different port number on each computer and then forward the corresponding ports to each computer from your router. (The RDP protocol doesn't like to be forwarded from one port number to a different one, so you need to touch the registry in all these computers.)
A more secure solution is to publish the RDP hosts only for the internal network, and then let your colleagues connect to the work network via VPN, instead. Once they've reached the inside, they can then connect their RDP session the normal way.
Edit: Deleted a tail that was left over.
by codyt8 Accepted solution
This discussion is closed to new replies.
Trending Networks posts
Sort by Trending