Client Can't connect.

[Guest Guillermo Martin]

Hi!!

We have a DC windows 2003 and one server with windows 2000 for terminal

services.

Today, just one client can't connect to the server.

The system event log on the Terminal server shows Event ID 1004 - "The

terminal

server cannot issue a client license". This shows up

everytime this specific client tries to login.

 

....Somebody can help me?

Thak you in advance!

Guille

[Guest Vera Noest [MVP]]

Re: Client Can't connect.

 

Have you checked the TS Licensing Manager? Does this client hold an

expired temporary license?

Which OS is this client running?

If it's running W2K Pro or XP Pro, it should receive a free TS CAL

from the built-in pool of "Existing Windows 2000 TS CALs".

But if it runs XP Home, NT, linux, Mac, or some thin client OS, it

needs a purchased TS CAL.

Is the client on the same LAN as the Terminal Server, or is it

connecting over a WAN link?

Can the client connect to the TS when you log on to the client with

a local Administrator account? If yes, then the user doesn't have

sufficient rights to the registry key which stores the license

locally.

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

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

___ please respond in newsgroup, NOT by private email ___

 

"Guillermo Martin" <pcencasa@hotmail.com> wrote on 19 sep 2007 in

microsoft.public.windows.terminal_services:

> Hi!!

> We have a DC windows 2003 and one server with windows 2000 for

> terminal services.

> Today, just one client can't connect to the server.

> The system event log on the Terminal server shows Event ID 1004

> - "The terminal

> server cannot issue a client license". This shows up

> everytime this specific client tries to login.

>

> ...Somebody can help me?

> Thak you in advance!

> Guille

[Guest TP]

Re: Client Can't connect.

 

Hi Guille,

 

Is your TS Licensing server activated with available purchased

TS CALs?

 

If the clients are Windows 2000, XP Pro, Vista Business/Ultimate/Enterprise,

or 2003 then they will receive a free TS CAL from the TS licensing server.

All other OS versions require a purchased TS CAL, for example, XP Home,

Vista Basic, Vista Home Premium, Windows CE, Linux, Mac, WinME, etc.

 

Are there any events in your TS server's System log with Source: TermService

Event ID: 1010 relating to not being able to find a licensing server?

 

Are there any events in your TS Licensing server's System log with

Source: TermServLicensing?

 

Thanks for answering my questions.

 

-TP

 

Guillermo Martin wrote:

> Hi!!

> We have a DC windows 2003 and one server with windows 2000 for

> terminal services.

> Today, just one client can't connect to the server.

> The system event log on the Terminal server shows Event ID 1004 - "The

> terminal

> server cannot issue a client license". This shows up

> everytime this specific client tries to login.

>

> ...Somebody can help me?

> Thak you in advance!

> Guille

[Guest Guillermo Martin]

Re: Client Can't connect.

 

Vera:

The Client is a Windows 98 under temporary license.

The client connect vía WAN.

The client can't connect with TS.

Another Clients can connect.

 

 

"Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> escribió en el

mensaje news:Xns99B0E25D55BFveranoesthemutforsse@207.46.248.16...

> Have you checked the TS Licensing Manager? Does this client hold an

> expired temporary license?

> Which OS is this client running?

> If it's running W2K Pro or XP Pro, it should receive a free TS CAL

> from the built-in pool of "Existing Windows 2000 TS CALs".

> But if it runs XP Home, NT, linux, Mac, or some thin client OS, it

> needs a purchased TS CAL.

> Is the client on the same LAN as the Terminal Server, or is it

> connecting over a WAN link?

> Can the client connect to the TS when you log on to the client with

> a local Administrator account? If yes, then the user doesn't have

> sufficient rights to the registry key which stores the license

> locally.

> _________________________________________________________

> Vera Noest

> MCSE, CCEA, Microsoft MVP - Terminal Server

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

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

>

> "Guillermo Martin" <pcencasa@hotmail.com> wrote on 19 sep 2007 in

> microsoft.public.windows.terminal_services:

>

> > Hi!!

> > We have a DC windows 2003 and one server with windows 2000 for

> > terminal services.

> > Today, just one client can't connect to the server.

> > The system event log on the Terminal server shows Event ID 1004

> > - "The terminal

> > server cannot issue a client license". This shows up

> > everytime this specific client tries to login.

> >

> > ...Somebody can help me?

> > Thak you in advance!

> > Guille

[Guest Guillermo Martin]

Re: Client Can't connect.

 

TP:

I have licmgr.exe installed, but i don't know if this is the TS Licensing

server, If I go to add windows components I have unselect "Terminal Server

Licensing".

Where I need to activate this, in Windows 2000 or in windows 2003? (ts

server is windows 2000 and DC is Windows 2003)

Yes, in the application I have this event: (in windows 2000)

 

Event ID: 213

Source: License Manager

Description: Replication of license information failed because the

license logging service on server <servername> could not be contacted.

 

....Some Ideas?

Thank You!!!!

Guille

 

 

"TP" <tperson.knowspamn@mailandnews.com> escribió en el mensaje

news:upGsvov#HHA.3900@TK2MSFTNGP02.phx.gbl...

> Hi Guille,

>

> Is your TS Licensing server activated with available purchased

> TS CALs?

>

> If the clients are Windows 2000, XP Pro, Vista

Business/Ultimate/Enterprise,

> or 2003 then they will receive a free TS CAL from the TS licensing server.

> All other OS versions require a purchased TS CAL, for example, XP Home,

> Vista Basic, Vista Home Premium, Windows CE, Linux, Mac, WinME, etc.

>

> Are there any events in your TS server's System log with Source:

TermService

> Event ID: 1010 relating to not being able to find a licensing server?

>

> Are there any events in your TS Licensing server's System log with

> Source: TermServLicensing?

>

> Thanks for answering my questions.

>

> -TP

>

> Guillermo Martin wrote:

> > Hi!!

> > We have a DC windows 2003 and one server with windows 2000 for

> > terminal services.

> > Today, just one client can't connect to the server.

> > The system event log on the Terminal server shows Event ID 1004 - "The

> > terminal

> > server cannot issue a client license". This shows up

> > everytime this specific client tries to login.

> >

> > ...Somebody can help me?

> > Thak you in advance!

> > Guille

[Guest TP]

Re: Client Can't connect.

 

Hi Guille,

 

1. On your DC install Terminal Server Licensing through Add/Remove

Windows Components by checking it and clicking next, etc.

 

2. Open up Terminal Server Licensing (licmgr.exe), right-click on the

server and choose Activate Server, follow the wizard instructions.

 

3. Install your purchased TS CALs by right-clicking on the server

name and choosing Install Licenses. Restart your Terminal Server or

give it some time to recognize that a TS licensing server is available.

 

You mentioned to Vera that you had a windows 98 machine. This is

one of OS versions that *require* a purchased TS CAL when connecting

to a Windows 2000 Terminal Server. See my previous reply for a list

of OS versions that do not require a purchased TS CAL.

 

-TP

 

Guillermo Martin wrote:

> TP:

> I have licmgr.exe installed, but i don't know if this is the TS

> Licensing server, If I go to add windows components I have unselect

> "Terminal Server Licensing".

> Where I need to activate this, in Windows 2000 or in windows 2003? (ts

> server is windows 2000 and DC is Windows 2003)

> Yes, in the application I have this event: (in windows 2000)

>

> Event ID: 213

> Source: License Manager

> Description: Replication of license information failed because the

> license logging service on server <servername> could not be

> contacted.

>

> ...Some Ideas?

> Thank You!!!!

> Guille