G
Guest
Let say you change RD listening port to something else than 3389. You open
up your firewalls (XP's and Norton Internet Security and my routers builtin)
to that other port. You set up SSH for the RD connection.
The RD server is behind a router that uses NAT, and my port is forwarded to
the servers ipaddress.
Now, if making a connection, that specific session is very very secure.
But your RD server is wide open anyways, since you opened up that port. And
the only thing that will keep it free from hackers is a very strong password.
Am i right?? Is there any other way to tighten that "hole", I don't want to
use VPN.
up your firewalls (XP's and Norton Internet Security and my routers builtin)
to that other port. You set up SSH for the RD connection.
The RD server is behind a router that uses NAT, and my port is forwarded to
the servers ipaddress.
Now, if making a connection, that specific session is very very secure.
But your RD server is wide open anyways, since you opened up that port. And
the only thing that will keep it free from hackers is a very strong password.
Am i right?? Is there any other way to tighten that "hole", I don't want to
use VPN.