Can not connect to Terminal Server W2K3

[Guest]

We have 10 W2K3 Servers. From one Windows 2000 Server when try to connect to W2K3 Servers it connects to 5 of them and would not connect to other five. My xp pro connects to all. It comes back and tells me Terminal server has ended the session.

 

[Rajneesh Mahajan \(MSFT\)]

Is there anything in the server's event log when you get this error?

Rajneesh
--
This posting is provided "AS IS" with no warranties, and confers no rights.
TS FAQ:
http://www.microsoft.com/windows2000/community/centers/terminal/terminal_faq.mspx

We have 10 W2K3 Servers. From one Windows 2000 Server when try to connect

to W2K3 Servers it connects to 5 of them and would not connect to other
five. My xp pro connects to all. It comes back and tells me Terminal server
has ended the session.

 

[Guest]

That's the first thing I checked. I get no errors in event viewer. Neither in Server nor in client. Strange. We have xp pro clients had the same problems and we updated with adminpack.msi and then they all started work fine. In short later version of rdp. But windows 2000 machine has the problem with latest rdp client as well. We were able to connect to it for 90 days and then it stopped. 5 W2K3 server connects fine and other five sends an error that your license cannot be upgraded. We have a license server running on our DOMAIN CONTROLLER with 20 license pack for application mode use configured as client licenses. I tried to delete registry key for temp license and then it says there is no client access license. After deleting license regisry key it was still connecting fine with the other five 2003 servers. We have not upgraded any of these boxes from NT 4. They all are brand new os and then upgraded active directory. Same thing with Exchange also. So I dont think any problem with NT4 TRACES. Whatever documents I found for licensing and client licenses can not be upgraded I checked them with no result.

 

[Rajneesh Mahajan \(MSFT\)]

It sounds like you are running out of licenses. Can you check if you have
any available using TS licensing tool?

--
This posting is provided "AS IS" with no warranties, and confers no rights.
TS FAQ:
http://www.microsoft.com/windows2000/community/centers/terminal/terminal_faq.mspx

That's the first thing I checked. I get no errors in event viewer. Neither

in Server nor in client. Strange. We have xp pro clients had the same
problems and we updated with adminpack.msi and then they all started work
fine. In short later version of rdp. But windows 2000 machine has the
problem with latest rdp client as well. We were able to connect to it for 90
days and then it stopped. 5 W2K3 server connects fine and other five sends
an error that your license cannot be upgraded. We have a license server
running on our DOMAIN CONTROLLER with 20 license pack for application mode
use configured as client licenses. I tried to delete registry key for temp
license and then it says there is no client access license. After deleting
license regisry key it was still connecting fine with the other five 2003
servers. We have not upgraded any of these boxes from NT 4. They all are
brand new os and then upgraded active directory. Same thing with Exchange
also. So I dont think any problem with NT4 TRACES. Whatever documents I
found for licensing and client licenses can not be upgraded I checked them
with no result.