Terminal Server Has Ended Your Connection

  • Thread starter Thread starter Sam
  • Start date Start date
S

Sam

I have been using a Windows 2000 Pro machine to connect to
a Windows 2000 Server on my LAN through Terminal Services.
The server was in Remote Management mode, and was switched
to Application mode. I am now unable to access that
server, and get the error message:

Terminal Server Has Ended Your Connection

This error only occurs with this machine. I don't have any
issues connecting from any other machine or any other
client. When I switch the server back to Remote Management
mode, I am able to connect again using this machine.

I am able to connect to other Terminal servers on the same
LAN using the same client machine if they are in Remote
Access Mode. I am unable to connect to them if they are in
Application Mode. I would appreciate any help.
 
Switching to Application mode means that you need licensing.
If you check the EventLog on the TS, you'll probably see event
1004 ("cannot issue license") as well as event 1010 ("cannot find
license server").

Install and activate a Terminal Services Licensing server on a
Domain Controller. See to it that the LS and the TS are at least
on SP3 level. Buy and install TS CALs for every client that is not
running W2K Pro or XP Pro.

Note: as far as I know, you can't buy W2K TS CALs anymore, so
you'll have to buy Windows 2003 TS CALs and use your downgrade
right to be able to install them on a W2K LS. You'll probably have
to phone the Clearinghouse during installation of your TS CALs.

Windows 2000 Terminal Services Licensing FAQ
http://www.microsoft.com/windows2000/server/howtobuy/pricing/tsfaq
..asp

Windows Server 2003 Pricing and Licensing FAQ
http://www.microsoft.com/windowsserver2003/howtobuy/licensing/pric
licfaq.mspx
 
It is not license issue, if you are using window 2000 pro.
It is connection issue. Try to ping -l 1400 -f ip adress
 
I tried to ping using 1492, which was the default MTU
size, and that did not work. I worked my way to 1418,
which seemed to work, and I changed the MTU size on the
server through RegEdit. I have not found the MTU on my
Windows 2000 machine. Changing the MTU size on the server
does not appear to solve the problem.

I am curious why this just started to happen, considering
the machine was working find previously. That's the only
thing that leads me to think that a time related thing,
like the "90 day evaluation period" of TS Application Mode
has expired.

I appreciate any an all feedback.
 
On my network, I have one Windows 2000 Server, and one
Windows 2000 SBS with 15 CALs. Is there a way I can use
the CALs on SBS to connect to the Windows 2000 Server,
without having to purchase additional CALs?
Thanks,
Sam
 
CALs and TS CALs are two different things. And the first thing you
need is to set up the licensing server. Even if the OS on the
client is entitled to a free TS CAL, it will get one from the LS.
 
Back
Top