We help IT Professionals succeed at work.

Terminal Services turned on on Windows 2000 web server

I have a vendor that will install a product for me if I turn on Terminal Services, he says.

Is that the same as using Remote Desktop Connection? If I get it setup so I can do that, can he use Terminal Services?

Meanwhile, I've had it on, and I've had pcanywhere on my server in the past, but once we stopped colocation and host them ourselves, we turned it all off. So I need to know how to get it back on.

In my firewalls (software and hardware), I have the Port 3389 TCP and UDP turned on for Terminal Services in the software firewall. In the hardware firewall I have Port 3389 active for the SUA Server. And in Lan to Lan Firewall, I have RDP/TCP/UDP 3389 active from and to any.

Yet, it does not work. Do I need something on in IIS? when I type in the IP address of the server, and select Connect, it errors and says it could not connect. It gives as a possible reason that Remote connections might not be enabled.

Where else should I enable this and am I doing it right so far?


Watch Question

Yes, terminal services is used for both application terminal services and remote desktop for administration, the only difference is the options you select when you install it.

Then, so long as he has an account with administrative permissions, he'll be able to logon using remote desktop (RDP).

As for PC Anywhere, can you give more info?  You may just need to enable a service and configure the firewall.

For the firewall, with TS you just need port 3389 open (I think TCP and UDP, but not sure).
Starr DuskkASP.NET VB.NET Developer


>>For the firewall, with TS you just need port 3389 open (I think TCP and UDP, but not sure).

Well, as indicated in my original, that's what I have, but it's not letting me in.

I don't need pcanywhere now, I was just saying at one time I used it. But right now all I need is Remote Desktop/Terminal Services.

Something must be missing? Can anyone help me, please?

See http://support.microsoft.com/kb/306624.

I'd also check to see whether you can use Terminal Services Client (remote desktop) directly from the server in question.  If you cannot use a remote desktop session to access the server from the server itself, then it's a configuration issue, otherwise it is most likely a firewall problem.
Glad to help.  Thanks for the points :)

Explore More ContentExplore courses, solutions, and other research materials related to this topic.