Remote session was disconnected because there are no terminal server licensing servers available

[Guest MSNews]

Remote session was disconnected because there are no terminal server licensing servers available

 

Hi,

 

Yes, I know there are many posts on this. What's different about this one is

that it is a Windows 2000 Server/TS issue with just on particular XP client.

 

In other words, any number of other clients work fine except a particular XP

client machine. Perhaps this should be posted and the XP forum though if

anyone can help I would be grateful before I reformat!

 

Many thanks

 

Piloo

[Guest Vera Noest [MVP]]

Re: Remote session was disconnected because there are no terminal server licensing servers available

 

Re: Remote session was disconnected because there are no terminal server licensing servers available

 

Does the XP client run XP Pro or XP Home Edition?

If it runs XP Home, it needs a purchased TS CAL.

 

If it runs XP Pro: is this client located on the same network as

other clients (and the TS), or is it connecting over the Internet?

 

The error message that you report is a bit mysterious, though. If

this was a client problem, I'd expect an error like: "your

temporary license has expired".

 

Are you sure that the other clients have received a permanent

license? Can you start the TS Licensing Manager and post back here

which type of licenses you have, and how many are issued and

available? Have you verified that the Terminal Server can locate

the TS Licensing Server? Can you post the licensing related EventID

and Source from the EventLog on the TS?

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

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

___ please respond in newsgroup, NOT by private email ___

 

"MSNews" <asanamxx@hotmail.com> wrote on 26 okt 2007 in

microsoft.public.windows.terminal_services:

> Hi,

>

> Yes, I know there are many posts on this. What's different about

> this one is that it is a Windows 2000 Server/TS issue with just

> on particular XP client.

>

> In other words, any number of other clients work fine except a

> particular XP client machine. Perhaps this should be posted and

> the XP forum though if anyone can help I would be grateful

> before I reformat!

>

> Many thanks

>

> Piloo

[Guest MSNews]

Re: Remote session was disconnected because there are no terminal server licensing servers available

 

Re: Remote session was disconnected because there are no terminal server licensing servers available

 

Hi Vera, thanks for looking in.

 

The client is XPPro and regardless of how it connects to the network it has

the same problem. Being a W2K TS with TSL on a SBS2000 box licenced for 25

users there is no constraint on the licencising insofar as only 10 have been

issued so far.

 

Mysterious; you can say that again!

 

Piloo

 

"Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> wrote in message

news:Xns99D5DF5697885veranoesthemutforsse@207.46.248.16...

> Does the XP client run XP Pro or XP Home Edition?

> If it runs XP Home, it needs a purchased TS CAL.

>

> If it runs XP Pro: is this client located on the same network as

> other clients (and the TS), or is it connecting over the Internet?

>

> The error message that you report is a bit mysterious, though. If

> this was a client problem, I'd expect an error like: "your

> temporary license has expired".

>

> Are you sure that the other clients have received a permanent

> license? Can you start the TS Licensing Manager and post back here

> which type of licenses you have, and how many are issued and

> available? Have you verified that the Terminal Server can locate

> the TS Licensing Server? Can you post the licensing related EventID

> and Source from the EventLog on the TS?

> _________________________________________________________

> Vera Noest

> MCSE, CCEA, Microsoft MVP - Terminal Server

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

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

>

> "MSNews" <asanamxx@hotmail.com> wrote on 26 okt 2007 in

> microsoft.public.windows.terminal_services:

>

>> Hi,

>>

>> Yes, I know there are many posts on this. What's different about

>> this one is that it is a Windows 2000 Server/TS issue with just

>> on particular XP client.

>>

>> In other words, any number of other clients work fine except a

>> particular XP client machine. Perhaps this should be posted and

>> the XP forum though if anyone can help I would be grateful

>> before I reformat!

>>

>> Many thanks

>>

>> Piloo

[Guest Donald C. Burr]

RE: Remote session was disconnected because there are no terminal serv

 

RE: Remote session was disconnected because there are no terminal serv

 

Saw this once before

This fixed it

 

Article ID : 279561

 

 

 

--

Donald C. Burr

Chief Technology Officer

TruckCenter.com, LLC

 

 

 

"MSNews" wrote:

> Hi,

>

> Yes, I know there are many posts on this. What's different about this one is

> that it is a Windows 2000 Server/TS issue with just on particular XP client.

>

> In other words, any number of other clients work fine except a particular XP

> client machine. Perhaps this should be posted and the XP forum though if

> anyone can help I would be grateful before I reformat!

>

> Many thanks

>

> Piloo

>

>

>

[Guest Vera Noest [MVP]]

Re: Remote session was disconnected because there are no terminal server licensing servers available

 

Re: Remote session was disconnected because there are no terminal server licensing servers available

 

OK, that answers my first 2 questions, but I would still need to

know the answer to my other questions to be able to give any

meaningfull reply:

>> Are you sure that the other clients have received a permanent

>> license?

>> Can you start the TS Licensing Manager and post back

>> here which type of licenses you have, and how many are issued

>> and available?

>> Have you verified that the Terminal Server can

>> locate the TS Licensing Server?

>> Can you post the licensing

>> related EventID and Source from the EventLog on the TS?

 

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

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

___ please respond in newsgroup, NOT by private email ___

 

"MSNews" <asanamxx@hotmail.com> wrote on 27 okt 2007 in

microsoft.public.windows.terminal_services:

> Hi Vera, thanks for looking in.

>

> The client is XPPro and regardless of how it connects to the

> network it has the same problem. Being a W2K TS with TSL on a

> SBS2000 box licenced for 25 users there is no constraint on the

> licencising insofar as only 10 have been issued so far.

>

> Mysterious; you can say that again!

>

> Piloo

>

> "Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> wrote

> in message

> news:Xns99D5DF5697885veranoesthemutforsse@207.46.248.16...

>> Does the XP client run XP Pro or XP Home Edition?

>> If it runs XP Home, it needs a purchased TS CAL.

>>

>> If it runs XP Pro: is this client located on the same network

>> as other clients (and the TS), or is it connecting over the

>> Internet?

>>

>> The error message that you report is a bit mysterious, though.

>> If this was a client problem, I'd expect an error like: "your

>> temporary license has expired".

>>

>> Are you sure that the other clients have received a permanent

>> license? Can you start the TS Licensing Manager and post back

>> here which type of licenses you have, and how many are issued

>> and available? Have you verified that the Terminal Server can

>> locate the TS Licensing Server? Can you post the licensing

>> related EventID and Source from the EventLog on the TS?

>> _________________________________________________________

>> Vera Noest

>> MCSE, CCEA, Microsoft MVP - Terminal Server

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

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

>>

>> "MSNews" <asanamxx@hotmail.com> wrote on 26 okt 2007 in

>> microsoft.public.windows.terminal_services:

>>

>>> Hi,

>>>

>>> Yes, I know there are many posts on this. What's different

>>> about this one is that it is a Windows 2000 Server/TS issue

>>> with just on particular XP client.

>>>

>>> In other words, any number of other clients work fine except a

>>> particular XP client machine. Perhaps this should be posted

>>> and the XP forum though if anyone can help I would be grateful

>>> before I reformat!

>>>

>>> Many thanks

>>>

>>> Piloo