Discussion Locked

Terminal services client setup

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

I've just started sinking my teeth into WINDOWS 2000 and I am looking for some help concerning the setup of terminal services on the client side using windows 2000 professional.
This is the scenario. We have a client with a NT 4.0 sp6 Terminal server. This server is behind a firewall. I have setup up PPTP using my windows 2000 Professional wkstn and it connects fine. The thin client part is where I am stuck. I am assuming that possibly this functionality is built into windows 2000, but I could not seem to find info on setting this up so I can actually pull the terminal servers login screen. I have tried the the terminal server client that works on my 98 machine but does not seem to work with w2k.

6 replies

by michel

Just download the latest client from MS, or ue the one that is shared in the TSCLIENT directory on the terminal server (it does require local install). If you W98 setup works behind the firewall, W2K should have no problem

by ltclay

I have done this and tried it on two different w2k workstations. One workstation with a static public IP and the other behind a firewall using NAT.
I get the same error message on both

Server is busy.. and it will not connect. However on thewindows 98 machines it connects fine with sam scenarios of a publis IP and a NAT IP

by parbo

I dont think this is beinig loaded by default but i can be mistaken. Anyway this should be listed under accessories/communication/hyperterminal. If its not there go to the control panel/add remove programs/communications and add it.

by ltclay

There was some confusion that I might be talking about hyperterm. I am trying to implement thin client terminal services not a telnet/hyperterm type connection

This discussion is closed to new replies.