Mister_E
join:2004-04-02
Etobicoke, ON
 ·Bell Sympatico
4 edits | First, I would specify the protocol as TCP.
Then, for the local port, you need to specify 3389 - don't specify all ports as this will leave your system open!
For the remote options, the port number should be set to all (or blank - I don't remember what Kerio 4.x uses). If the IP you're connecting from doesn't change (e.g. a static internet IP) you can specify it for added security - otherwise, don't specify an IP or set an IP range that belongs to the IP block you connect from.
Finally, the application specified should be C:\WINDOWS\system32\svchost.exe (as it's svchost that's listening to requests on port 3389 and will manage the Terminal services connection - assuming you're running XP at home). If this doesn't work, you may have to change the application specified to 'Any' to allow communication on port 3389 to get where it needs to go.
Also, if you have a router in between the home PC you're connecting to, you may have configure it to port forward 3389 to the PC's internal IP address. (If your router supports a VPN connection/VPN server, you'll be better off using this to establish the connection - see below.)
BE WARNED though, opening port 3389 is a security risk - many port scanners check to see if this port is open and attack via it, etc. The best solution is to set up a VPN connection first, then run Remote Desktop over the VPN. |
