nonsequitur
[H]ard|Gawd
- Joined
- Feb 13, 2002
- Messages
- 1,525
I occasionally help my previous employer with IT issues, and I'd like to put in place some options for me to do some of the administration remotely.
the current setup has ms server 2000 as a domain controller, and about a dozen workstations. the tricky part is that the internet connection is shared with several other businesses in the building and this company doesn't control the router and ports opened/forwarded. the isp would cooperate, but i'm trying to head-off hearing too many "no's"
I would use win2k server's terminal server to do remote administration most likely without a vpn (unless the horde feels the standard encryption is crap).
I searched some here:
http://hardforum.com/showthread.php?t=1163160&highlight=remote+administration
and see that port 3389 is for terminal services
how difficult would it be to use a non-standard port for this purpose? what would be a good way to pick one?
the current setup has ms server 2000 as a domain controller, and about a dozen workstations. the tricky part is that the internet connection is shared with several other businesses in the building and this company doesn't control the router and ports opened/forwarded. the isp would cooperate, but i'm trying to head-off hearing too many "no's"
I would use win2k server's terminal server to do remote administration most likely without a vpn (unless the horde feels the standard encryption is crap).
I searched some here:
http://hardforum.com/showthread.php?t=1163160&highlight=remote+administration
and see that port 3389 is for terminal services
how difficult would it be to use a non-standard port for this purpose? what would be a good way to pick one?