I have one Windows 2000 Professional client that
consistently gets the error "client could not connect to
the terminal server. The Server may be too busy."  I have
verified that port 3389 is open.

I have 4 Thin client (WinTerms). They will not connect to
the T.S.  I get the following error message. "The
Terminal server ended the connection or a netwrok error
occured. Please try to reconnect.". The event viewer show

We have just installed a 2003 server (it is not a domain
server)  on a 2000 domain(sp4).
I was wondering do I need to do something to start
terminal services?

Greetings All,
Windows 2000 server (SP3) in NT4 domain.  Terminal
Services running in Application mode.  Has been properly
activated.  Problem:  Only administrators are able to

I am running 2k terminal Server to a bunch of thin
clients.  Some of the thin clients were used as testing
clients, and are no longer needed to have a license doled
out to them.  

I have simple Jobs(IE and calculator) scheduled on win 2000 server which
runs, but does not open the application window, what is wrong?
I am executing by terminal server using remote desktop connection.
On my win 2000 professional runs ok and open all windows!

I'm trying to logon on to a win2000 Server from a win2000 workstation and I
keep getting this message "You Do Not Have Access To Logon To This Session".
What privileges or rights need to be set to allow me to do this?
Thanks for any help

I have 25 users on a Windows 2000 enviroment, 3 locations
all on the same domain. We utilize Terminal Services for
the 2 remote locations to access our business system (a
dos base platform, QP4) we are a retail business. When we

Is it possible to connect to my Win2K workstation (non-server) from my WinXP
computer from home via Terminal Services? If so, what do I need to do on my
Win2K computer to allow this?
Thanks,

I have users on my Win2K Terminal Server who don't always
log off at night.  However, I want to make sure that there
are no files locked for backups.  I was wondering if there
is an easy way to write a batch file that would log off

I'm using Win 2k services in a multi NT domain environment.  When users open
mstsc and click Connect to logon, the domain they are not logging from is
not displayed.  I know you have to set that in default.rdp and save that,
which I have done.  However in some cases, this still does ...

I have a problem which has occured a few times and has me
concerned that it might start to happen more often.  One
user tries to login under Metaframe XP FR2 and where he
was able to login no problem last week, suddenly cannot

I just bought 3 ipaq pdas (4300 series running pocket pc
2003).  As I configured each one, they were able to log on
to my terminal server (win 2000 server) just once.  After
that they just time out. I see event 1004 in event

I downloaded and installed a Remote Desktop client on a
W2K PC.  I have not yet, been able to access this W2K PC
remotely from Win XP PC.  I can access the Win XP
remotely from the W2K PC.  I'm not able to access the

I installed Outlook 2003 on a Citrix W2K Terminal server and preconifigured user profiles by creating a PRF file. The problem I am having is that I cannot get the PRF file to run when a user account launches Outlook 2003 for the first time in a terminal session. I have followed ...