...no Terminal Server License Servers available...

[c1utch]

I'm using a 180 day evaluation copy of Windows 2003 server to test terminal services. (Microsoft says its supposed to be a full version) I set it up about 3-4 months ago and enabled the terminal server license service on my domain controller. Right after I set it up, I would log onto the 2003 terminal server itself and go to the terminal server licensing tool within Administrative Tools. I noticed that the license server (My DC) wasn't showing up. I then right clicked and connected to it manually, which I then could browse the licenses that have been added, but when I close this tool down and open it again, the 2003 sever says again that it can't find a terminal license server on the domain. In other words, it wouldn't find it automatically...only if I manually connected to it using this tool.

Terminal services worked fine off of this server for about 3 months, even though the above problem lingered in the back of my head...remember, this is only a test server. Clients (using windows 2000 pro) were able to connect just fine without any problems. However, about a week ago I started getting an error when I or anyone else from other windows 2000 pro boxes try to connect. They get the following error:

Remote Desktop Disconnected
The remote session was disconnected because there are no Terminal Server License Servers available to provide a license.
Please contact the server administrator.

I've tried a couple of different tricks that I've found off the web, most have which have been registry tweaks to point the TS to the Term. License Server.

I still think it stems back to the fact that my Windows 2003 server can't remember where the heck my TS License server is.

Anyone have any ideas?

Chris

 

[Davetoo]

Did you purchase CAL's for 2003 TS? The license structure for 2003 is completely different, you have to purchase TS CAL's for any system that connects to a 2003 TS, there are no more "built-in" TS licenses for W2K or XP Pro.

I'm Certifiable, not certified.
It just means my answers are from experience, not a book.

 

[c1utch]

Why won't the Windows 2003 server automatically connect to my DC through the TS licensing tool. I would think that even though I don't have any licenses for 2003, it would still connect to the DC (TS Licensing Server).

Also, why were all my clients able to connect and now none of them can. Not even new PC's that have never connected before. If the 2003 TS issued 30 or 60 day temporary licenses to those clients, why did they all expire at the same time, even though those temp. licenses were issued at different times?

Chris

 

[Davetoo]

TS in app mode will work for 90 days, then quit, regardless of when licenses were issued. It's 90 days from initialization of the TS, not from when the license was issued.

I'm Certifiable, not certified.
It just means my answers are from experience, not a book.

 

[c1utch]

Ahhhh, that makes sense. Sucks though. I had my boss bought on the idea that we wouldn't need TS CAL's for the Windows 2000 clients.

Let me pick your brain while I've got you.

From you experience, is there much of a difference between Windows 2000 Server and Windows 2003 server in terms of Terminal Services? (Printer redirection, 3rd party applications working in TS, etc.) In other words, what would I loose if I ended up using Windows 2000 Server so that I could use my Windows 2000 CAL's to connect?

Chris

 

[Davetoo]

Haven't worked with 2003 (yet), but I understand it simplifies printer connects, etc. over 2000.

I'm Certifiable, not certified.
It just means my answers are from experience, not a book.

 

[jasonhill]

Windows 2003 has rdp5.2 2000 has rdp5.

I am running a windows2000 ts with pxes on the client side(linux thing) I have tried running on both 2000 and 2003. 2000 looks fine but only runs in a limited amount of colors. 2003 or rdp5.2 has alot of other features like full color and some other stuff(can't remember right now.)

http://www.google.com

rdp5.2

 

[c1utch]

jasonhill,

Well, before I responded I checked a couple things out. At first I thought most, if not all of the functionality of the newer version of TS was entirely within the client (which doesn't make sense) The reason I thought this is of all the settings you can change before making your connection to the server. (display settings, LPT-COM port and local driver mappings, etc.) However, when I connected to a windows 2000 server using the 5.2 client, I noticed my local drives weren't getting mapped. This led me to the windows 2000 server TS configuration tool. I noticed that mapping the client drives was greyed out and also audio mapping. The light bulb went on over my head. I remember looking into why these two were greyed out sever months ago. I guess even though they are both there, they can't be configured in Windows 2000 server. I don't know why microsoft included these two features, only to tease us since they aren't supported.

My conclusion...the client and the TS configuration of RDP-TCP connection work hand in hand. Even though I'm using the newer client, my Windows 2000 server doesn't support the extra functionality that the client offers.

This sound right?

-Chris

Chris