Terminal server 2000 in 2003 domain

[Guest WS]

We recently upgrade our w2k domain to w2k3 domain. There is no w2k domain

controller and we rise the function level to Windows 2003. Now the exsiting

windows 200 terminal server won't take any new Terminal session. What should

we do?

 

Thanks for your help!

 

WS

[Guest Vera Noest [MVP]]

Re: Terminal server 2000 in 2003 domain

 

Check the EventLog. I'm pretty sure that the W2K TS will complain

there about not being able to locate a TS Licensing Server (but

verify this!).

Most likely, the TS Licensing Service was running on one of your DC's

(because a W2K LS has to run on a DC). I believe that an inplace

upgrade from W2K to 2003 also updates the Licensing Service, but it

has to be reactivated manually.

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

TS troubleshooting: http://ts.veranoest.net

___ please respond in newsgroup, NOT by private email ___

 

=?Utf-8?B?V1M=?= <WS@discussions.microsoft.com> wrote on 29 nov

2007 in microsoft.public.windows.terminal_services:

> We recently upgrade our w2k domain to w2k3 domain. There is no

> w2k domain controller and we rise the function level to Windows

> 2003. Now the exsiting windows 200 terminal server won't take

> any new Terminal session. What should we do?

>

> Thanks for your help!

>

> WS

[Guest WS]

Re: Terminal server 2000 in 2003 domain

 

You are exactly right! I reactivated the license server. It works!

 

Thanks for pointing me to the right direction!

 

WS

 

"Vera Noest [MVP]" wrote:

> Check the EventLog. I'm pretty sure that the W2K TS will complain

> there about not being able to locate a TS Licensing Server (but

> verify this!).

> Most likely, the TS Licensing Service was running on one of your DC's

> (because a W2K LS has to run on a DC). I believe that an inplace

> upgrade from W2K to 2003 also updates the Licensing Service, but it

> has to be reactivated manually.

> _________________________________________________________

> Vera Noest

> MCSE, CCEA, Microsoft MVP - Terminal Server

> TS troubleshooting: http://ts.veranoest.net

> ___ please respond in newsgroup, NOT by private email ___

>

> =?Utf-8?B?V1M=?= <WS@discussions.microsoft.com> wrote on 29 nov

> 2007 in microsoft.public.windows.terminal_services:

>

> > We recently upgrade our w2k domain to w2k3 domain. There is no

> > w2k domain controller and we rise the function level to Windows

> > 2003. Now the exsiting windows 200 terminal server won't take

> > any new Terminal session. What should we do?

> >

> > Thanks for your help!

> >

> > WS

>

[Guest Vera Noest [MVP]]

Re: Terminal server 2000 in 2003 domain

 

Great! I'm glad that your problem is solved, and thanks for the

feedback!

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

TS troubleshooting: http://ts.veranoest.net

___ please respond in newsgroup, NOT by private email ___

 

=?Utf-8?B?V1M=?= <WS@discussions.microsoft.com> wrote on 30 nov

2007 in microsoft.public.windows.terminal_services:

> You are exactly right! I reactivated the license server. It

> works!

>

> Thanks for pointing me to the right direction!

>

> WS

>

> "Vera Noest [MVP]" wrote:

>

>> Check the EventLog. I'm pretty sure that the W2K TS will

>> complain there about not being able to locate a TS Licensing

>> Server (but verify this!).

>> Most likely, the TS Licensing Service was running on one of

>> your DC's (because a W2K LS has to run on a DC). I believe that

>> an inplace upgrade from W2K to 2003 also updates the Licensing

>> Service, but it has to be reactivated manually.

>> _________________________________________________________

>> Vera Noest

>> MCSE, CCEA, Microsoft MVP - Terminal Server

>> TS troubleshooting: http://ts.veranoest.net

>> ___ please respond in newsgroup, NOT by private email ___

>>

>> =?Utf-8?B?V1M=?= <WS@discussions.microsoft.com> wrote on 29 nov

>> 2007 in microsoft.public.windows.terminal_services:

>>

>> > We recently upgrade our w2k domain to w2k3 domain. There is

>> > no w2k domain controller and we rise the function level to

>> > Windows 2003. Now the exsiting windows 200 terminal server

>> > won't take any new Terminal session. What should we do?

>> >

>> > Thanks for your help!

>> >

>> > WS