Discussion Locked

Server 2000 and remote terminal services

0 helpful
2 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

We have a Windows Server 2000 machine supporting 5 users via Windows Terminal Services. Works great on our LAN. Supporting just one computer sure beats supporting five and the performance is excellent.

The next deployment step is for remote WTS access over the internet.

The server currently connects to the internet via a 1.5Mbit ADSL modem with static IP. We currently use a Watchguard SOHO device as a firewall - it seems to work fine however it seems that we might have been given a bum steer with regard to it's suitability for our next step - going remote with Terminal Services.

Although I found setting up WTS on our LAN to be very easy, my search for tutorial info on setting up for remote internet access has been less than fruitful.

Do I need to implement VPN for terminal services?
How do I configure the Watchguard SOHO box to allow WTS in?
Can server 2000 by itself (without a hardware based firewall) manage sufficient network security?

I am surprised that I can't find straight forward info on setting up this system - am I looking in the wrong places?

A final note - we are a small business that doesn't have thousands of dollars to spend on more advanced hardware firewalls. WE would ideally like to use standard facilities that come with Server 2000.

Can someone please point me in the right direction.

2 replies

by scottsman

It all is a question of your firewalls capabilites. if you can "publish" a server with it than you are in buisness just make a rule that opens port 3389 and passes through requests to the internal ip of your terminal server. than your clients will use your 1 static external ip to connect. I did this using w2k term server behind a w2k sbs running ISA. I had called Microsoft and they couldnt show me how to do this. but I finally hammered my way through it good luck and feel free to email me if you have further questions.

by garyinoz

Thanks for your response. I hope you can help me out a little more.

1. Do I need to use VPN services or will terminal services run direct as if it was on my local network? I imagine it will run standalone - I seem to remember somewhere that WTS has it's own encryption. I guess that the encryption keys are set up automatically by the WTS install disks of the server. Elsewhere I have read that WTS does not offer any securiyt - the log-on screen just pops up for anyone! Why then would WTS encrypt the traffic?

2. By opening up port 3389 as you suggest (I should do this on the hardware firewall?), do I compromise security of my server?

3. We have no intent "to publish" a web site on the internet.

Our connection to the internet is solely for three objectives:
a) allow internet access of employees on our local network via WTS or a local browser - running
b) facilitate acces to our mail server located at our local ISP - running
c) allow WTS access for remote company users via the internet - not running

Do I have this right?

Thanks again for your help Scotsman.

This discussion is closed to new replies.