Event ID : 1004 - The terminal server cannot optain a client licen

[Guest Anders]

I have a Win2000 TS licensing server and 2 Win2000 TS running in AppMode. I

have about 40 users, Win XP and Intermec devices using the TS. When I try to

connect with some new clients I get a 1004 error. All the "old" clients are

working fine, but I cannot connect with any of the new clients.

 

The licensing server have "lost" all my TS, I can just see the licensing

server it self. When I am trying to connect to one of my TS from the

licensing server, I got this message : Windows cannot connect to a licensing

server.

 

I have tried to follow the Guidelines from Q239107, but it still dos´nt work.

 

It seems that I have got a system where it is´nt possible to connect any new

clients !!

 

Anybody - help !!!

 

Regards Anders

[Guest Vera Noest [MVP]]

Re: Event ID : 1004 - The terminal server cannot optain a client licen

 

comments inline

 

=?Utf-8?B?QW5kZXJz?= <Anders@discussions.microsoft.com> wrote on

19 sep 2007 in microsoft.public.windows.terminal_services:

> I have a Win2000 TS licensing server and 2 Win2000 TS running in

> AppMode.

 

Is the TS Licensing Server running on the Domain Controller? Have

you checked that it is actually running?

Are there any errors or warnings in the EventLog on the TS

Licensing Server?

> I have about 40 users, Win XP and Intermec devices

> using the TS. When I try to connect with some new clients I get

> a 1004 error. All the "old" clients are working fine, but I

> cannot connect with any of the new clients.

>

> The licensing server have "lost" all my TS, I can just see the

> licensing server it self.

 

The licensing server has no knowledge about your Terminal Servers,

so it can't have lost them either.

It's the other way around, your Terminal Servers must be able to

find your TS Licensing Server.

> When I am trying to connect to one of

> my TS from the licensing server, I got this message : Windows

> cannot connect to a licensing server.

 

When you open the TS Licensing Manager on the TS Licensing Server,

do you see the licenses that are issued? If not, do you see them

when you connect to the TS Licensing Server (*not* a TS)?

> I have tried to follow the Guidelines from Q239107, but it still

> dos´nt work.

 

On which server did you try to implement KB 239107? I suspect that

you made the registry change on the TS Licensing Server. If so, you

must do it on each terminal Server.

> It seems that I have got a system where it is´nt possible to

> connect any new clients !!

>

> Anybody - help !!!

>

> Regards Anders

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

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

___ please respond in newsgroup, NOT by private email ___

[Guest Anders]

Re: Event ID : 1004 - The terminal server cannot optain a client l

 

Re: Event ID : 1004 - The terminal server cannot optain a client l

 

Hi Vera

 

1. The Licensing Server is running on the DC

2. Yes, it is running.

3. I did found some errors in the event log :

 

Event Type: Warning

Event Source: TermServLicensing

Event Category: None

Event ID: 22

Date: 19-09-2007

Time: 09:25:57

User: N/A

Computer: BIWEB

Description:

The Terminal Services Licensing server BIWEB has no license pack registered

for product 'Windows 2000 Terminal Services Client Access License'. Use

Terminal Services Licensing administrative tool to register the licenses pack.

 

 

Event Type: Warning

Event Source: TermService

Event Category: None

Event ID: 1013

Date: 15-02-2007

Time: 11:39:28

User: N/A

Computer: BIWEB

Description:

The terminal server has exceeded the maximum number of allowed connections.

 

4. About "loosing" the Terminal Servers, I am convinced that the "Terminal

Service Licensing Manager" once could see the Terminal Servers, but I am not

sure.

 

5. Yes - At the Terminal Service Licensing Manager I can see the licenses

tha are issued.

 

Existing Win 2000 license - Buil-in - Unlimited - 45 Issued

Temp license for existing win 2000 license - Temp - 2 Issued

Temp license Win 2000 term service Client Access - Temp - 6 Issued

 

6. I Implementet the q239107 only at one of my terminal servers, just to

see if it worked, but it did´nt.

 

Do I have to try to deactivate / reactivate the Terminal Licensing Server ??

 

Best Regards

 

Anders

 

 

"Vera Noest [MVP]" wrote:

> comments inline

>

> =?Utf-8?B?QW5kZXJz?= <Anders@discussions.microsoft.com> wrote on

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

>

> > I have a Win2000 TS licensing server and 2 Win2000 TS running in

> > AppMode.

>

> Is the TS Licensing Server running on the Domain Controller? Have

> you checked that it is actually running?

> Are there any errors or warnings in the EventLog on the TS

> Licensing Server?

>

> > I have about 40 users, Win XP and Intermec devices

> > using the TS. When I try to connect with some new clients I get

> > a 1004 error. All the "old" clients are working fine, but I

> > cannot connect with any of the new clients.

> >

> > The licensing server have "lost" all my TS, I can just see the

> > licensing server it self.

>

> The licensing server has no knowledge about your Terminal Servers,

> so it can't have lost them either.

> It's the other way around, your Terminal Servers must be able to

> find your TS Licensing Server.

>

> > When I am trying to connect to one of

> > my TS from the licensing server, I got this message : Windows

> > cannot connect to a licensing server.

>

> When you open the TS Licensing Manager on the TS Licensing Server,

> do you see the licenses that are issued? If not, do you see them

> when you connect to the TS Licensing Server (*not* a TS)?

>

> > I have tried to follow the Guidelines from Q239107, but it still

> > dos´nt work.

>

> On which server did you try to implement KB 239107? I suspect that

> you made the registry change on the TS Licensing Server. If so, you

> must do it on each terminal Server.

>

> > It seems that I have got a system where it is´nt possible to

> > connect any new clients !!

> >

> > Anybody - help !!!

> >

> > Regards Anders

> _________________________________________________________

> Vera Noest

> MCSE, CCEA, Microsoft MVP - Terminal Server

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

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

>

[Guest Vera Noest [MVP]]

Re: Event ID : 1004 - The terminal server cannot optain a client l

 

Re: Event ID : 1004 - The terminal server cannot optain a client l

 

OK, that explains your issue.

You simply have to purchase and install TS CALs for your down-level

clients.

Seems you need 6 of them, one for each client who has been issued a

"Temporary license Win 2000 term service Client Access"

 

_________________________________________________________

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?QW5kZXJz?= <Anders@discussions.microsoft.com> wrote on

20 sep 2007 in microsoft.public.windows.terminal_services:

> Hi Vera

>

> 1. The Licensing Server is running on the DC

> 2. Yes, it is running.

> 3. I did found some errors in the event log :

>

> Event Type: Warning

> Event Source: TermServLicensing

> Event Category: None

> Event ID: 22

> Date: 19-09-2007

> Time: 09:25:57

> User: N/A

> Computer: BIWEB

> Description:

> The Terminal Services Licensing server BIWEB has no license pack

> registered for product 'Windows 2000 Terminal Services Client

> Access License'. Use Terminal Services Licensing administrative

> tool to register the licenses pack.

>

>

> Event Type: Warning

> Event Source: TermService

> Event Category: None

> Event ID: 1013

> Date: 15-02-2007

> Time: 11:39:28

> User: N/A

> Computer: BIWEB

> Description:

> The terminal server has exceeded the maximum number of allowed

> connections.

>

> 4. About "loosing" the Terminal Servers, I am convinced that the

> "Terminal Service Licensing Manager" once could see the Terminal

> Servers, but I am not sure.

>

> 5. Yes - At the Terminal Service Licensing Manager I can see the

> licenses tha are issued.

>

> Existing Win 2000 license - Buil-in - Unlimited - 45 Issued

> Temp license for existing win 2000 license - Temp - 2 Issued

> Temp license Win 2000 term service Client Access - Temp - 6

> Issued

>

> 6. I Implementet the q239107 only at one of my terminal

> servers, just to see if it worked, but it did´nt.

>

> Do I have to try to deactivate / reactivate the Terminal

> Licensing Server ??

>

> Best Regards

>

> Anders

>

>

> "Vera Noest [MVP]" wrote:

>

>> comments inline

>>

>> =?Utf-8?B?QW5kZXJz?= <Anders@discussions.microsoft.com> wrote

>> on 19 sep 2007 in microsoft.public.windows.terminal_services:

>>

>> > I have a Win2000 TS licensing server and 2 Win2000 TS running

>> > in AppMode.

>>

>> Is the TS Licensing Server running on the Domain Controller?

>> Have you checked that it is actually running?

>> Are there any errors or warnings in the EventLog on the TS

>> Licensing Server?

>>

>> > I have about 40 users, Win XP and Intermec devices

>> > using the TS. When I try to connect with some new clients I

>> > get a 1004 error. All the "old" clients are working fine, but

>> > I cannot connect with any of the new clients.

>> >

>> > The licensing server have "lost" all my TS, I can just see

>> > the licensing server it self.

>>

>> The licensing server has no knowledge about your Terminal

>> Servers, so it can't have lost them either.

>> It's the other way around, your Terminal Servers must be able

>> to find your TS Licensing Server.

>>

>> > When I am trying to connect to one of

>> > my TS from the licensing server, I got this message : Windows

>> > cannot connect to a licensing server.

>>

>> When you open the TS Licensing Manager on the TS Licensing

>> Server, do you see the licenses that are issued? If not, do you

>> see them when you connect to the TS Licensing Server (*not* a

>> TS)?

>>

>> > I have tried to follow the Guidelines from Q239107, but it

>> > still dos´nt work.

>>

>> On which server did you try to implement KB 239107? I suspect

>> that you made the registry change on the TS Licensing Server.

>> If so, you must do it on each terminal Server.

>>

>> > It seems that I have got a system where it is´nt possible

>> > to connect any new clients !!

>> >

>> > Anybody - help !!!

>> >

>> > Regards Anders

>> _________________________________________________________

>> Vera Noest

>> MCSE, CCEA, Microsoft MVP - Terminal Server

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

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

[Guest Anders]

Re: Event ID : 1004 - The terminal server cannot optain a client l

 

Re: Event ID : 1004 - The terminal server cannot optain a client l

 

OK - maybe it is a stupid question, but I believe that my Win XP and Intermec

terminals had a license for free at Terminal Service 2000, it is the main

reason why I choose the TS2000. I am aware of that I have to pay for all

licenses to a Terminal Server 2003, but also TS 2000 ??

 

"Vera Noest [MVP]" wrote:

> OK, that explains your issue.

> You simply have to purchase and install TS CALs for your down-level

> clients.

> Seems you need 6 of them, one for each client who has been issued a

> "Temporary license Win 2000 term service Client Access"

>

> _________________________________________________________

> 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?QW5kZXJz?= <Anders@discussions.microsoft.com> wrote on

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

>

> > Hi Vera

> >

> > 1. The Licensing Server is running on the DC

> > 2. Yes, it is running.

> > 3. I did found some errors in the event log :

> >

> > Event Type: Warning

> > Event Source: TermServLicensing

> > Event Category: None

> > Event ID: 22

> > Date: 19-09-2007

> > Time: 09:25:57

> > User: N/A

> > Computer: BIWEB

> > Description:

> > The Terminal Services Licensing server BIWEB has no license pack

> > registered for product 'Windows 2000 Terminal Services Client

> > Access License'. Use Terminal Services Licensing administrative

> > tool to register the licenses pack.

> >

> >

> > Event Type: Warning

> > Event Source: TermService

> > Event Category: None

> > Event ID: 1013

> > Date: 15-02-2007

> > Time: 11:39:28

> > User: N/A

> > Computer: BIWEB

> > Description:

> > The terminal server has exceeded the maximum number of allowed

> > connections.

> >

> > 4. About "loosing" the Terminal Servers, I am convinced that the

> > "Terminal Service Licensing Manager" once could see the Terminal

> > Servers, but I am not sure.

> >

> > 5. Yes - At the Terminal Service Licensing Manager I can see the

> > licenses tha are issued.

> >

> > Existing Win 2000 license - Buil-in - Unlimited - 45 Issued

> > Temp license for existing win 2000 license - Temp - 2 Issued

> > Temp license Win 2000 term service Client Access - Temp - 6

> > Issued

> >

> > 6. I Implementet the q239107 only at one of my terminal

> > servers, just to see if it worked, but it did´nt.

> >

> > Do I have to try to deactivate / reactivate the Terminal

> > Licensing Server ??

> >

> > Best Regards

> >

> > Anders

> >

> >

> > "Vera Noest [MVP]" wrote:

> >

> >> comments inline

> >>

> >> =?Utf-8?B?QW5kZXJz?= <Anders@discussions.microsoft.com> wrote

> >> on 19 sep 2007 in microsoft.public.windows.terminal_services:

> >>

> >> > I have a Win2000 TS licensing server and 2 Win2000 TS running

> >> > in AppMode.

> >>

> >> Is the TS Licensing Server running on the Domain Controller?

> >> Have you checked that it is actually running?

> >> Are there any errors or warnings in the EventLog on the TS

> >> Licensing Server?

> >>

> >> > I have about 40 users, Win XP and Intermec devices

> >> > using the TS. When I try to connect with some new clients I

> >> > get a 1004 error. All the "old" clients are working fine, but

> >> > I cannot connect with any of the new clients.

> >> >

> >> > The licensing server have "lost" all my TS, I can just see

> >> > the licensing server it self.

> >>

> >> The licensing server has no knowledge about your Terminal

> >> Servers, so it can't have lost them either.

> >> It's the other way around, your Terminal Servers must be able

> >> to find your TS Licensing Server.

> >>

> >> > When I am trying to connect to one of

> >> > my TS from the licensing server, I got this message : Windows

> >> > cannot connect to a licensing server.

> >>

> >> When you open the TS Licensing Manager on the TS Licensing

> >> Server, do you see the licenses that are issued? If not, do you

> >> see them when you connect to the TS Licensing Server (*not* a

> >> TS)?

> >>

> >> > I have tried to follow the Guidelines from Q239107, but it

> >> > still dos´nt work.

> >>

> >> On which server did you try to implement KB 239107? I suspect

> >> that you made the registry change on the TS Licensing Server.

> >> If so, you must do it on each terminal Server.

> >>

> >> > It seems that I have got a system where it is´nt possible

> >> > to connect any new clients !!

> >> >

> >> > Anybody - help !!!

> >> >

> >> > Regards Anders

> >> _________________________________________________________

> >> Vera Noest

> >> MCSE, CCEA, Microsoft MVP - Terminal Server

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

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

>

[Guest Vera Noest [MVP]]

Re: Event ID : 1004 - The terminal server cannot optain a client l

 

Re: Event ID : 1004 - The terminal server cannot optain a client l

 

Only W2K Pro, XP Pro and Vista Business clients receive a free TS

CAL from the built-in pool of licenses on the Licensing Server (the

licenses that are called "Existing Win 2000 license - Built-in -

Unlimited").

 

All downlevel clients (thin clients, linux, Macintosh, XP Home,

etc) need a purchased TS CAL.

So it's probably your Intermec clients that need a purchased TS

CAL. You can verify that when you check which clients have received

an temporary W2K Per Device CAL.

_________________________________________________________

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?QW5kZXJz?= <Anders@discussions.microsoft.com> wrote on

20 sep 2007 in microsoft.public.windows.terminal_services:

> OK - maybe it is a stupid question, but I believe that my Win XP

> and Intermec terminals had a license for free at Terminal

> Service 2000, it is the main reason why I choose the TS2000. I

> am aware of that I have to pay for all licenses to a Terminal

> Server 2003, but also TS 2000 ??

>

> "Vera Noest [MVP]" wrote:

>

>> OK, that explains your issue.

>> You simply have to purchase and install TS CALs for your

>> down-level clients.

>> Seems you need 6 of them, one for each client who has been

>> issued a "Temporary license Win 2000 term service Client

>> Access"

>>

>> _________________________________________________________

>> 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?QW5kZXJz?= <Anders@discussions.microsoft.com> wrote

>> on 20 sep 2007 in microsoft.public.windows.terminal_services:

>>

>> > Hi Vera

>> >

>> > 1. The Licensing Server is running on the DC

>> > 2. Yes, it is running.

>> > 3. I did found some errors in the event log :

>> >

>> > Event Type: Warning

>> > Event Source: TermServLicensing

>> > Event Category: None

>> > Event ID: 22

>> > Date: 19-09-2007

>> > Time: 09:25:57

>> > User: N/A

>> > Computer: BIWEB

>> > Description:

>> > The Terminal Services Licensing server BIWEB has no license

>> > pack registered for product 'Windows 2000 Terminal Services

>> > Client Access License'. Use Terminal Services Licensing

>> > administrative tool to register the licenses pack.

>> >

>> >

>> > Event Type: Warning

>> > Event Source: TermService

>> > Event Category: None

>> > Event ID: 1013

>> > Date: 15-02-2007

>> > Time: 11:39:28

>> > User: N/A

>> > Computer: BIWEB

>> > Description:

>> > The terminal server has exceeded the maximum number of

>> > allowed connections.

>> >

>> > 4. About "loosing" the Terminal Servers, I am convinced that

>> > the "Terminal Service Licensing Manager" once could see the

>> > Terminal Servers, but I am not sure.

>> >

>> > 5. Yes - At the Terminal Service Licensing Manager I can see

>> > the licenses tha are issued.

>> >

>> > Existing Win 2000 license - Buil-in - Unlimited - 45 Issued

>> > Temp license for existing win 2000 license - Temp - 2 Issued

>> > Temp license Win 2000 term service Client Access - Temp - 6

>> > Issued

>> >

>> > 6. I Implementet the q239107 only at one of my terminal

>> > servers, just to see if it worked, but it did´nt.

>> >

>> > Do I have to try to deactivate / reactivate the Terminal

>> > Licensing Server ??

>> >

>> > Best Regards

>> >

>> > Anders

>> >

>> >

>> > "Vera Noest [MVP]" wrote:

>> >

>> >> comments inline

>> >>

>> >> =?Utf-8?B?QW5kZXJz?= <Anders@discussions.microsoft.com>

>> >> wrote on 19 sep 2007 in

>> >> microsoft.public.windows.terminal_services:

>> >>

>> >> > I have a Win2000 TS licensing server and 2 Win2000 TS

>> >> > running in AppMode.

>> >>

>> >> Is the TS Licensing Server running on the Domain Controller?

>> >> Have you checked that it is actually running?

>> >> Are there any errors or warnings in the EventLog on the TS

>> >> Licensing Server?

>> >>

>> >> > I have about 40 users, Win XP and Intermec devices

>> >> > using the TS. When I try to connect with some new clients

>> >> > I get a 1004 error. All the "old" clients are working

>> >> > fine, but I cannot connect with any of the new clients.

>> >> >

>> >> > The licensing server have "lost" all my TS, I can just see

>> >> > the licensing server it self.

>> >>

>> >> The licensing server has no knowledge about your Terminal

>> >> Servers, so it can't have lost them either.

>> >> It's the other way around, your Terminal Servers must be

>> >> able to find your TS Licensing Server.

>> >>

>> >> > When I am trying to connect to one of

>> >> > my TS from the licensing server, I got this message :

>> >> > Windows cannot connect to a licensing server.

>> >>

>> >> When you open the TS Licensing Manager on the TS Licensing

>> >> Server, do you see the licenses that are issued? If not, do

>> >> you see them when you connect to the TS Licensing Server

>> >> (*not* a TS)?

>> >>

>> >> > I have tried to follow the Guidelines from Q239107, but it

>> >> > still dos´nt work.

>> >>

>> >> On which server did you try to implement KB 239107? I

>> >> suspect that you made the registry change on the TS

>> >> Licensing Server. If so, you must do it on each terminal

>> >> Server.

>> >>

>> >> > It seems that I have got a system where it is´nt

>> >> > possible to connect any new clients !!

>> >> >

>> >> > Anybody - help !!!

>> >> >

>> >> > Regards Anders

>> >> _________________________________________________________

>> >> Vera Noest

>> >> MCSE, CCEA, Microsoft MVP - Terminal Server

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

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

[Guest Anders]

Re: Event ID : 1004 - The terminal server cannot optain a client l

 

Re: Event ID : 1004 - The terminal server cannot optain a client l

 

Hi again

 

It is`nt easy !!

 

The Activation Status of the TS license server is ACTIVATED.

The Temp lic for W2K TS CAL are identified, and are not the Intermec Clients.

When I`m trying to add more Licenses, I got this info :

 

The license server`s activation has expired. To use this license server, you

must reactivate it. Do you want to reactivate the server now?

 

I have`nt reactivated the server yet, because I`m not sure what is going to

happen with my existing and OK clients. As I have mentiont, I have newer

installed any CAL at my licensing server. I have been told that my Intermec

terminals have a CAL for free, and it seems to be correct, it have worked for

about 2½ year, until now.

 

It seems that I have to reactivate the license server, but what will happen

with my existing Clients ??

 

Best Regards

 

Anders

 

"Vera Noest [MVP]" wrote:

> Only W2K Pro, XP Pro and Vista Business clients receive a free TS

> CAL from the built-in pool of licenses on the Licensing Server (the

> licenses that are called "Existing Win 2000 license - Built-in -

> Unlimited").

>

> All downlevel clients (thin clients, linux, Macintosh, XP Home,

> etc) need a purchased TS CAL.

> So it's probably your Intermec clients that need a purchased TS

> CAL. You can verify that when you check which clients have received

> an temporary W2K Per Device CAL.

> _________________________________________________________

> 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?QW5kZXJz?= <Anders@discussions.microsoft.com> wrote on

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

>

> > OK - maybe it is a stupid question, but I believe that my Win XP

> > and Intermec terminals had a license for free at Terminal

> > Service 2000, it is the main reason why I choose the TS2000. I

> > am aware of that I have to pay for all licenses to a Terminal

> > Server 2003, but also TS 2000 ??

> >

> > "Vera Noest [MVP]" wrote:

> >

> >> OK, that explains your issue.

> >> You simply have to purchase and install TS CALs for your

> >> down-level clients.

> >> Seems you need 6 of them, one for each client who has been

> >> issued a "Temporary license Win 2000 term service Client

> >> Access"

> >>

> >> _________________________________________________________

> >> 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?QW5kZXJz?= <Anders@discussions.microsoft.com> wrote

> >> on 20 sep 2007 in microsoft.public.windows.terminal_services:

> >>

> >> > Hi Vera

> >> >

> >> > 1. The Licensing Server is running on the DC

> >> > 2. Yes, it is running.

> >> > 3. I did found some errors in the event log :

> >> >

> >> > Event Type: Warning

> >> > Event Source: TermServLicensing

> >> > Event Category: None

> >> > Event ID: 22

> >> > Date: 19-09-2007

> >> > Time: 09:25:57

> >> > User: N/A

> >> > Computer: BIWEB

> >> > Description:

> >> > The Terminal Services Licensing server BIWEB has no license

> >> > pack registered for product 'Windows 2000 Terminal Services

> >> > Client Access License'. Use Terminal Services Licensing

> >> > administrative tool to register the licenses pack.

> >> >

> >> >

> >> > Event Type: Warning

> >> > Event Source: TermService

> >> > Event Category: None

> >> > Event ID: 1013

> >> > Date: 15-02-2007

> >> > Time: 11:39:28

> >> > User: N/A

> >> > Computer: BIWEB

> >> > Description:

> >> > The terminal server has exceeded the maximum number of

> >> > allowed connections.

> >> >

> >> > 4. About "loosing" the Terminal Servers, I am convinced that

> >> > the "Terminal Service Licensing Manager" once could see the

> >> > Terminal Servers, but I am not sure.

> >> >

> >> > 5. Yes - At the Terminal Service Licensing Manager I can see

> >> > the licenses tha are issued.

> >> >

> >> > Existing Win 2000 license - Buil-in - Unlimited - 45 Issued

> >> > Temp license for existing win 2000 license - Temp - 2 Issued

> >> > Temp license Win 2000 term service Client Access - Temp - 6

> >> > Issued

> >> >

> >> > 6. I Implementet the q239107 only at one of my terminal

> >> > servers, just to see if it worked, but it did´nt.

> >> >

> >> > Do I have to try to deactivate / reactivate the Terminal

> >> > Licensing Server ??

> >> >

> >> > Best Regards

> >> >

> >> > Anders

> >> >

> >> >

> >> > "Vera Noest [MVP]" wrote:

> >> >

> >> >> comments inline

> >> >>

> >> >> =?Utf-8?B?QW5kZXJz?= <Anders@discussions.microsoft.com>

> >> >> wrote on 19 sep 2007 in

> >> >> microsoft.public.windows.terminal_services:

> >> >>

> >> >> > I have a Win2000 TS licensing server and 2 Win2000 TS

> >> >> > running in AppMode.

> >> >>

> >> >> Is the TS Licensing Server running on the Domain Controller?

> >> >> Have you checked that it is actually running?

> >> >> Are there any errors or warnings in the EventLog on the TS

> >> >> Licensing Server?

> >> >>

> >> >> > I have about 40 users, Win XP and Intermec devices

> >> >> > using the TS. When I try to connect with some new clients

> >> >> > I get a 1004 error. All the "old" clients are working

> >> >> > fine, but I cannot connect with any of the new clients.

> >> >> >

> >> >> > The licensing server have "lost" all my TS, I can just see

> >> >> > the licensing server it self.

> >> >>

> >> >> The licensing server has no knowledge about your Terminal

> >> >> Servers, so it can't have lost them either.

> >> >> It's the other way around, your Terminal Servers must be

> >> >> able to find your TS Licensing Server.

> >> >>

> >> >> > When I am trying to connect to one of

> >> >> > my TS from the licensing server, I got this message :

> >> >> > Windows cannot connect to a licensing server.

> >> >>

> >> >> When you open the TS Licensing Manager on the TS Licensing

> >> >> Server, do you see the licenses that are issued? If not, do

> >> >> you see them when you connect to the TS Licensing Server

> >> >> (*not* a TS)?

> >> >>

> >> >> > I have tried to follow the Guidelines from Q239107, but it

> >> >> > still dos´nt work.

> >> >>

> >> >> On which server did you try to implement KB 239107? I

> >> >> suspect that you made the registry change on the TS

> >> >> Licensing Server. If so, you must do it on each terminal

> >> >> Server.

> >> >>

> >> >> > It seems that I have got a system where it is´nt

> >> >> > possible to connect any new clients !!

> >> >> >

> >> >> > Anybody - help !!!

> >> >> >

> >> >> > Regards Anders

> >> >> _________________________________________________________

> >> >> Vera Noest

> >> >> MCSE, CCEA, Microsoft MVP - Terminal Server

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

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

>

[Guest Vera Noest [MVP]]

Re: Event ID : 1004 - The terminal server cannot optain a client l

 

Re: Event ID : 1004 - The terminal server cannot optain a client l

 

Reactivating your LS should not have an impact on your already

issued licenses.

Details are here:

 

306578 - HOW TO: Deactivate or Reactivate a License Server Using

Terminal Services Licensing

http://support.microsoft.com/?kbid=306578

 

_________________________________________________________

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?QW5kZXJz?= <Anders@discussions.microsoft.com> wrote on

02 okt 2007 in microsoft.public.windows.terminal_services:

> Hi again

>

> It is`nt easy !!

>

> The Activation Status of the TS license server is ACTIVATED.

> The Temp lic for W2K TS CAL are identified, and are not the

> Intermec Clients. When I`m trying to add more Licenses, I got

> this info :

>

> The license server`s activation has expired. To use this license

> server, you must reactivate it. Do you want to reactivate the

> server now?

>

> I have`nt reactivated the server yet, because I`m not sure what

> is going to happen with my existing and OK clients. As I have

> mentiont, I have newer installed any CAL at my licensing server.

> I have been told that my Intermec terminals have a CAL for free,

> and it seems to be correct, it have worked for about 2½ year,

> until now.

>

> It seems that I have to reactivate the license server, but what

> will happen with my existing Clients ??

>

> Best Regards

>

> Anders

>

> "Vera Noest [MVP]" wrote:

>

>> Only W2K Pro, XP Pro and Vista Business clients receive a free

>> TS CAL from the built-in pool of licenses on the Licensing

>> Server (the licenses that are called "Existing Win 2000 license

>> - Built-in - Unlimited").

>>

>> All downlevel clients (thin clients, linux, Macintosh, XP Home,

>> etc) need a purchased TS CAL.

>> So it's probably your Intermec clients that need a purchased TS

>> CAL. You can verify that when you check which clients have

>> received an temporary W2K Per Device CAL.

>> _________________________________________________________

>> 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?QW5kZXJz?= <Anders@discussions.microsoft.com> wrote

>> on 20 sep 2007 in microsoft.public.windows.terminal_services:

>>

>> > OK - maybe it is a stupid question, but I believe that my Win

>> > XP and Intermec terminals had a license for free at Terminal

>> > Service 2000, it is the main reason why I choose the TS2000.

>> > I am aware of that I have to pay for all licenses to a

>> > Terminal Server 2003, but also TS 2000 ??

>> >

>> > "Vera Noest [MVP]" wrote:

>> >

>> >> OK, that explains your issue.

>> >> You simply have to purchase and install TS CALs for your

>> >> down-level clients.

>> >> Seems you need 6 of them, one for each client who has been

>> >> issued a "Temporary license Win 2000 term service Client

>> >> Access"

>> >>

>> >> _________________________________________________________

>> >> 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?QW5kZXJz?= <Anders@discussions.microsoft.com>

>> >> wrote on 20 sep 2007 in

>> >> microsoft.public.windows.terminal_services:

>> >>

>> >> > Hi Vera

>> >> >

>> >> > 1. The Licensing Server is running on the DC

>> >> > 2. Yes, it is running.

>> >> > 3. I did found some errors in the event log :

>> >> >

>> >> > Event Type: Warning

>> >> > Event Source: TermServLicensing

>> >> > Event Category: None

>> >> > Event ID: 22

>> >> > Date: 19-09-2007

>> >> > Time: 09:25:57

>> >> > User: N/A

>> >> > Computer: BIWEB

>> >> > Description:

>> >> > The Terminal Services Licensing server BIWEB has no

>> >> > license pack registered for product 'Windows 2000 Terminal

>> >> > Services Client Access License'. Use Terminal Services

>> >> > Licensing administrative tool to register the licenses

>> >> > pack.

>> >> >

>> >> >

>> >> > Event Type: Warning

>> >> > Event Source: TermService

>> >> > Event Category: None

>> >> > Event ID: 1013

>> >> > Date: 15-02-2007

>> >> > Time: 11:39:28

>> >> > User: N/A

>> >> > Computer: BIWEB

>> >> > Description:

>> >> > The terminal server has exceeded the maximum number of

>> >> > allowed connections.

>> >> >

>> >> > 4. About "loosing" the Terminal Servers, I am convinced

>> >> > that the "Terminal Service Licensing Manager" once could

>> >> > see the Terminal Servers, but I am not sure.

>> >> >

>> >> > 5. Yes - At the Terminal Service Licensing Manager I can

>> >> > see the licenses tha are issued.

>> >> >

>> >> > Existing Win 2000 license - Buil-in - Unlimited - 45

>> >> > Issued Temp license for existing win 2000 license - Temp -

>> >> > 2 Issued Temp license Win 2000 term service Client Access

>> >> > - Temp - 6 Issued

>> >> >

>> >> > 6. I Implementet the q239107 only at one of my terminal

>> >> > servers, just to see if it worked, but it did´nt.

>> >> >

>> >> > Do I have to try to deactivate / reactivate the Terminal

>> >> > Licensing Server ??

>> >> >

>> >> > Best Regards

>> >> >

>> >> > Anders

>> >> >

>> >> >

>> >> > "Vera Noest [MVP]" wrote:

>> >> >

>> >> >> comments inline

>> >> >>

>> >> >> =?Utf-8?B?QW5kZXJz?= <Anders@discussions.microsoft.com>

>> >> >> wrote on 19 sep 2007 in

>> >> >> microsoft.public.windows.terminal_services:

>> >> >>

>> >> >> > I have a Win2000 TS licensing server and 2 Win2000 TS

>> >> >> > running in AppMode.

>> >> >>

>> >> >> Is the TS Licensing Server running on the Domain

>> >> >> Controller? Have you checked that it is actually running?

>> >> >> Are there any errors or warnings in the EventLog on the

>> >> >> TS Licensing Server?

>> >> >>

>> >> >> > I have about 40 users, Win XP and Intermec devices

>> >> >> > using the TS. When I try to connect with some new

>> >> >> > clients I get a 1004 error. All the "old" clients are

>> >> >> > working fine, but I cannot connect with any of the new

>> >> >> > clients.

>> >> >> >

>> >> >> > The licensing server have "lost" all my TS, I can just

>> >> >> > see the licensing server it self.

>> >> >>

>> >> >> The licensing server has no knowledge about your Terminal

>> >> >> Servers, so it can't have lost them either.

>> >> >> It's the other way around, your Terminal Servers must be

>> >> >> able to find your TS Licensing Server.

>> >> >>

>> >> >> > When I am trying to connect to one of

>> >> >> > my TS from the licensing server, I got this message :

>> >> >> > Windows cannot connect to a licensing server.

>> >> >>

>> >> >> When you open the TS Licensing Manager on the TS

>> >> >> Licensing Server, do you see the licenses that are

>> >> >> issued? If not, do you see them when you connect to the

>> >> >> TS Licensing Server (*not* a TS)?

>> >> >>

>> >> >> > I have tried to follow the Guidelines from Q239107, but

>> >> >> > it still dos´nt work.

>> >> >>

>> >> >> On which server did you try to implement KB 239107? I

>> >> >> suspect that you made the registry change on the TS

>> >> >> Licensing Server. If so, you must do it on each terminal

>> >> >> Server.

>> >> >>

>> >> >> > It seems that I have got a system where it

>> >> >> > is´nt possible to connect any new

>> >> >> > clients !!

>> >> >> >

>> >> >> > Anybody - help !!!

>> >> >> >

>> >> >> > Regards Anders

>> >> >> _________________________________________________________

>> >> >> Vera Noest

>> >> >> MCSE, CCEA, Microsoft MVP - Terminal Server

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

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