Licensing Server Not Resolve IP Address of Terminal Server

[Guest Darryl Smith]

I have set up the License Server Security Group setting on my Terminal Server

Licensing Server which is running Windows 2003. The majority of the time it

works fine, however, if there is a power outage, I get the following error

message in the System Log:

 

---------------------------------------

Event Type: Error

Event Source: TermServLicensing

Event Category: None

Event ID: 45

Date: 8/10/2007

Time: 11:57:56 AM

User: N/A

Computer:

Description:

A license could not be issued to XX.XX.XX.XX because it is not a member of

the Terminal Server Computers group.

 

For more information, see Help and Support Center at

http://go.microsoft.com/fwlink/events.asp.

---------------------------------------------------

 

The Terminal Server is a member of the Terminal Server Computers group, but

for some reason the Licensing Server cannot resolve the IP Address of the

Terminal Server even though both servers use the same DNS Server, and the

Licensing Server can resolve the IP Address fine via DNS.

 

Rebooting the Terminal Server seems to resolve the issue (until the next

power outage)

 

Does anyone know a fix for this?

 

Thank you in advance ....

 

Darryl Smith

[Guest sen_ismail@web.de]

Re: Licensing Server Not Resolve IP Address of Terminal Server

 

On Oct 8, 7:46 am, Darryl Smith

<DarrylSm...@discussions.microsoft.com> wrote:

> I have set up the License Server Security Group setting on my Terminal Server

> Licensing Server which is running Windows 2003. The majority of the time it

> works fine, however, if there is a power outage, I get the following error

> message in the System Log:

>

> ---------------------------------------

> Event Type: Error

> Event Source: TermServLicensing

> Event Category: None

> Event ID: 45

> Date: 8/10/2007

> Time: 11:57:56 AM

> User: N/A

> Computer:

> Description:

> A license could not be issued to XX.XX.XX.XX because it is not a member of

> the Terminal Server Computers group.

>

> For more information, see Help and Support Center athttp://go.microsoft.com/fwlink/events.asp.

> ---------------------------------------------------

>

> The Terminal Server is a member of the Terminal Server Computers group, but

> for some reason the Licensing Server cannot resolve the IP Address of the

> Terminal Server even though both servers use the same DNS Server, and the

> Licensing Server can resolve the IP Address fine via DNS.

>

> Rebooting the Terminal Server seems to resolve the issue (until the next

> power outage)

>

> Does anyone know a fix for this?

>

> Thank you in advance ....

>

> Darryl Smith

 

Hi,

 

you should try: http://support.microsoft.com/default.aspx?scid=kb;EN-US;279561

for Windows 2003 Server

Set on the TS Server your default TSLS with Ip Adress:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TermService

\Parameters > a new Key <IP Adress from TSLS Server>

You do not need to restart. Thsi disable the discovery prozess and the

TS Server is looking first to this Key bevor strating a discovery

process.

 

cheers,

Ismail

[Guest Vera Noest [MVP]]

Re: Licensing Server Not Resolve IP Address of Terminal Server

 

My first thought after reading your post was that you really should

try to fix these power outages. A decent UPS is not too expensive

and can save you a lot of trouble.

 

That said, it sounds to me as if there could be a timing problem,

with the TS maybe powering up faster than the LS does. Just a

guess, though. Here's an article which describes how this could

happen, assuming that there are multiple LS Licensing Server

Security groups in your domain:

918658 - Some Windows Server 2003-based terminal servers cannot

acquire a license when there is more than one License Server

security group

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

 

You could test this by taking them down in a controlled experiment

and then power them up manually to see what happens.

 

If this really is the cause, it's yet another argument for an UPS,

because most UPS managing software gives you the possibility to

built in a waiting period for some servers, which must be started

after other servers have come online.

_________________________________________________________

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?RGFycnlsIFNtaXRo?=

<DarrylSmith@discussions.microsoft.com> wrote on 08 okt 2007 in

microsoft.public.windows.terminal_services:

> I have set up the License Server Security Group setting on my

> Terminal Server Licensing Server which is running Windows 2003.

> The majority of the time it works fine, however, if there is a

> power outage, I get the following error message in the System

> Log:

>

> ---------------------------------------

> Event Type: Error

> Event Source: TermServLicensing

> Event Category: None

> Event ID: 45

> Date: 8/10/2007

> Time: 11:57:56 AM

> User: N/A

> Computer:

> Description:

> A license could not be issued to XX.XX.XX.XX because it is not a

> member of the Terminal Server Computers group.

>

> For more information, see Help and Support Center at

> http://go.microsoft.com/fwlink/events.asp.

> ---------------------------------------------------

>

> The Terminal Server is a member of the Terminal Server Computers

> group, but for some reason the Licensing Server cannot resolve

> the IP Address of the Terminal Server even though both servers

> use the same DNS Server, and the Licensing Server can resolve

> the IP Address fine via DNS.

>

> Rebooting the Terminal Server seems to resolve the issue (until

> the next power outage)

>

> Does anyone know a fix for this?

>

> Thank you in advance ....

>

> Darryl Smith

[Guest Darryl Smith]

Re: Licensing Server Not Resolve IP Address of Terminal Server

 

Update ....

 

It seems that power outages aren't part of the issue as another Terminal

Server & Licensing Server I have setup in our Datacentre also experiences the

same issue.

 

Discovering the License Server is not the issue as the Terminal Server is

requesting a TS-CAL from the License server fine. The issue is that the

License Server is producing the Error Message in the System Log of the

License Server. The workstation that is trying to remote to the Terminal

Server is getting a "The remote session was disconnected because there are no

Terminal Server client access licenses available for this computer"

 

I've had to implement the "License Server Security Group" to stop our

Windows 2003 Domain Controllers and non-Terminal Server Member Servers from

requesting TS-CALs.

 

Not sure what the reason is for the Terminal Server to suddenly request

TS-CALs using its IP Address rather than its Computer Name. Nothing in the

Event Logs indicate anything failing.

 

Has anyone come across this issue before?

 

Regards,

Darryl Smith

 

"Vera Noest [MVP]" wrote:

> My first thought after reading your post was that you really should

> try to fix these power outages. A decent UPS is not too expensive

> and can save you a lot of trouble.

>

> That said, it sounds to me as if there could be a timing problem,

> with the TS maybe powering up faster than the LS does. Just a

> guess, though. Here's an article which describes how this could

> happen, assuming that there are multiple LS Licensing Server

> Security groups in your domain:

> 918658 - Some Windows Server 2003-based terminal servers cannot

> acquire a license when there is more than one License Server

> security group

> http://support.microsoft.com/?kbid=918658

>

> You could test this by taking them down in a controlled experiment

> and then power them up manually to see what happens.

>

> If this really is the cause, it's yet another argument for an UPS,

> because most UPS managing software gives you the possibility to

> built in a waiting period for some servers, which must be started

> after other servers have come online.

> _________________________________________________________

> 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?RGFycnlsIFNtaXRo?=

> <DarrylSmith@discussions.microsoft.com> wrote on 08 okt 2007 in

> microsoft.public.windows.terminal_services:

>

> > I have set up the License Server Security Group setting on my

> > Terminal Server Licensing Server which is running Windows 2003.

> > The majority of the time it works fine, however, if there is a

> > power outage, I get the following error message in the System

> > Log:

> >

> > ---------------------------------------

> > Event Type: Error

> > Event Source: TermServLicensing

> > Event Category: None

> > Event ID: 45

> > Date: 8/10/2007

> > Time: 11:57:56 AM

> > User: N/A

> > Computer:

> > Description:

> > A license could not be issued to XX.XX.XX.XX because it is not a

> > member of the Terminal Server Computers group.

> >

> > For more information, see Help and Support Center at

> > http://go.microsoft.com/fwlink/events.asp.

> > ---------------------------------------------------

> >

> > The Terminal Server is a member of the Terminal Server Computers

> > group, but for some reason the Licensing Server cannot resolve

> > the IP Address of the Terminal Server even though both servers

> > use the same DNS Server, and the Licensing Server can resolve

> > the IP Address fine via DNS.

> >

> > Rebooting the Terminal Server seems to resolve the issue (until

> > the next power outage)

> >

> > Does anyone know a fix for this?

> >

> > Thank you in advance ....

> >

> > Darryl Smith

>

[Guest Vera Noest [MVP]]

Re: Licensing Server Not Resolve IP Address of Terminal Server

 

Let me see if I understand you correctly: clients connect to the

real TS and the TS requests a TS CAL from just about any server on

the network, which in their turn forward the request to the real TS

Licensing Server? Can you confirm that this is your situation?

 

It sounds weird! Have you run lsview from the Resource Kit to check

which servers are recognized as TS Licensing Servers?

Also have a look in AD, under LDAP://CN=TS-Enterprise-License-

Server,CN=site-name,CN=sites,CN=configuration,DC=domainname,DC=com

 

Can you fix the problem by configuring the TS with a list of

preferred TS Licensing Servers, in tscc.msc or a GPO?

 

_________________________________________________________

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?RGFycnlsIFNtaXRo?=

<DarrylSmith@discussions.microsoft.com> wrote on 19 nov 2007 in

microsoft.public.windows.terminal_services:

> Update ....

>

> It seems that power outages aren't part of the issue as another

> Terminal Server & Licensing Server I have setup in our

> Datacentre also experiences the same issue.

>

> Discovering the License Server is not the issue as the Terminal

> Server is requesting a TS-CAL from the License server fine. The

> issue is that the License Server is producing the Error Message

> in the System Log of the License Server. The workstation that is

> trying to remote to the Terminal Server is getting a "The remote

> session was disconnected because there are no Terminal Server

> client access licenses available for this computer"

>

> I've had to implement the "License Server Security Group" to

> stop our Windows 2003 Domain Controllers and non-Terminal Server

> Member Servers from requesting TS-CALs.

>

> Not sure what the reason is for the Terminal Server to suddenly

> request TS-CALs using its IP Address rather than its Computer

> Name. Nothing in the Event Logs indicate anything failing.

>

> Has anyone come across this issue before?

>

> Regards,

> Darryl Smith

>

> "Vera Noest [MVP]" wrote:

>

>> My first thought after reading your post was that you really

>> should try to fix these power outages. A decent UPS is not too

>> expensive and can save you a lot of trouble.

>>

>> That said, it sounds to me as if there could be a timing

>> problem, with the TS maybe powering up faster than the LS does.

>> Just a guess, though. Here's an article which describes how

>> this could happen, assuming that there are multiple LS

>> Licensing Server Security groups in your domain:

>> 918658 - Some Windows Server 2003-based terminal servers cannot

>> acquire a license when there is more than one License Server

>> security group

>> http://support.microsoft.com/?kbid=918658

>>

>> You could test this by taking them down in a controlled

>> experiment and then power them up manually to see what happens.

>>

>> If this really is the cause, it's yet another argument for an

>> UPS, because most UPS managing software gives you the

>> possibility to built in a waiting period for some servers,

>> which must be started after other servers have come online.

>> _________________________________________________________

>> 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?RGFycnlsIFNtaXRo?=

>> <DarrylSmith@discussions.microsoft.com> wrote on 08 okt 2007 in

>> microsoft.public.windows.terminal_services:

>>

>> > I have set up the License Server Security Group setting on my

>> > Terminal Server Licensing Server which is running Windows

>> > 2003. The majority of the time it works fine, however, if

>> > there is a power outage, I get the following error message in

>> > the System Log:

>> >

>> > ---------------------------------------

>> > Event Type: Error

>> > Event Source: TermServLicensing

>> > Event Category: None

>> > Event ID: 45

>> > Date: 8/10/2007

>> > Time: 11:57:56 AM

>> > User: N/A

>> > Computer:

>> > Description:

>> > A license could not be issued to XX.XX.XX.XX because it is

>> > not a member of the Terminal Server Computers group.

>> >

>> > For more information, see Help and Support Center at

>> > http://go.microsoft.com/fwlink/events.asp.

>> > ---------------------------------------------------

>> >

>> > The Terminal Server is a member of the Terminal Server

>> > Computers group, but for some reason the Licensing Server

>> > cannot resolve the IP Address of the Terminal Server even

>> > though both servers use the same DNS Server, and the

>> > Licensing Server can resolve the IP Address fine via DNS.

>> >

>> > Rebooting the Terminal Server seems to resolve the issue

>> > (until the next power outage)

>> >

>> > Does anyone know a fix for this?

>> >

>> > Thank you in advance ....

>> >

>> > Darryl Smith

[Guest Darryl Smith]

Re: Licensing Server Not Resolve IP Address of Terminal Server

 

No .... The Terminal Server is requesting a TS CAL from the Licensing Server

fine. It's just that the Licensing Server allocate a TS-CAL.

 

I know it's hard to follow so I decided to try and re-write the whole

situation so it's (possibly) easier to follow .....

 

I had to implement the "License Server Security Group" policy on my

Licensing Server because my Windows 2003 Domain Controllers and non-Terminal

Server Member Servers were requesting and dishing out TS-CALs to any

workstation that RDP'ed to them.

 

Now, I seem to be getting this issue come up every so often. I haven't been

able to pick what the root cause of the issue is yet, but the majority of the

time, a reboot of the Terminal Server will work (why I don't know either).

Basically what's happening is this .....

 

A user is getting the following error message on their workstation when they

try to RDP to the Terminal Server:

"The remote session was disconnected because there are no Terminal Server

client access licenses avaiable for this computer."

 

When I check the System Log on the Terminal Server, I get the following event:

"This Terminal Server is not able to communicate with the License Server.

Please make sure that this Terminal Server's computer account is a member of

the "Terminal Server Computers" group on the License Server"

 

When I check the System Log on the License Server, I get the following event:

"A license could not be issue to xx.xx.xx.xx [iP Address of the Terminal

Server] because it is not a member of the Terminal Server Computers group."

 

Basically what is happening is that the Licensing Server is not resolving

the Computer Name of the Terminal Server from its IP Address.

 

The Terminal Server is discovering and requesting a TS-CAL from the

Licensing Server, but the Licensing Server won't dish out the TS-CAL.

 

I hope I've explained the situation a bit better.

 

Thanks for your help thus far.

 

Regards,

Darryl Smith

 

"Vera Noest [MVP]" wrote:

> Let me see if I understand you correctly: clients connect to the

> real TS and the TS requests a TS CAL from just about any server on

> the network, which in their turn forward the request to the real TS

> Licensing Server? Can you confirm that this is your situation?

>

> It sounds weird! Have you run lsview from the Resource Kit to check

> which servers are recognized as TS Licensing Servers?

> Also have a look in AD, under LDAP://CN=TS-Enterprise-License-

> Server,CN=site-name,CN=sites,CN=configuration,DC=domainname,DC=com

>

> Can you fix the problem by configuring the TS with a list of

> preferred TS Licensing Servers, in tscc.msc or a GPO?

>

> _________________________________________________________

> 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?RGFycnlsIFNtaXRo?=

> <DarrylSmith@discussions.microsoft.com> wrote on 19 nov 2007 in

> microsoft.public.windows.terminal_services:

>

> > Update ....

> >

> > It seems that power outages aren't part of the issue as another

> > Terminal Server & Licensing Server I have setup in our

> > Datacentre also experiences the same issue.

> >

> > Discovering the License Server is not the issue as the Terminal

> > Server is requesting a TS-CAL from the License server fine. The

> > issue is that the License Server is producing the Error Message

> > in the System Log of the License Server. The workstation that is

> > trying to remote to the Terminal Server is getting a "The remote

> > session was disconnected because there are no Terminal Server

> > client access licenses available for this computer"

> >

> > I've had to implement the "License Server Security Group" to

> > stop our Windows 2003 Domain Controllers and non-Terminal Server

> > Member Servers from requesting TS-CALs.

> >

> > Not sure what the reason is for the Terminal Server to suddenly

> > request TS-CALs using its IP Address rather than its Computer

> > Name. Nothing in the Event Logs indicate anything failing.

> >

> > Has anyone come across this issue before?

> >

> > Regards,

> > Darryl Smith

> >

> > "Vera Noest [MVP]" wrote:

> >

> >> My first thought after reading your post was that you really

> >> should try to fix these power outages. A decent UPS is not too

> >> expensive and can save you a lot of trouble.

> >>

> >> That said, it sounds to me as if there could be a timing

> >> problem, with the TS maybe powering up faster than the LS does.

> >> Just a guess, though. Here's an article which describes how

> >> this could happen, assuming that there are multiple LS

> >> Licensing Server Security groups in your domain:

> >> 918658 - Some Windows Server 2003-based terminal servers cannot

> >> acquire a license when there is more than one License Server

> >> security group

> >> http://support.microsoft.com/?kbid=918658

> >>

> >> You could test this by taking them down in a controlled

> >> experiment and then power them up manually to see what happens.

> >>

> >> If this really is the cause, it's yet another argument for an

> >> UPS, because most UPS managing software gives you the

> >> possibility to built in a waiting period for some servers,

> >> which must be started after other servers have come online.

> >> _________________________________________________________

> >> 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?RGFycnlsIFNtaXRo?=

> >> <DarrylSmith@discussions.microsoft.com> wrote on 08 okt 2007 in

> >> microsoft.public.windows.terminal_services:

> >>

> >> > I have set up the License Server Security Group setting on my

> >> > Terminal Server Licensing Server which is running Windows

> >> > 2003. The majority of the time it works fine, however, if

> >> > there is a power outage, I get the following error message in

> >> > the System Log:

> >> >

> >> > ---------------------------------------

> >> > Event Type: Error

> >> > Event Source: TermServLicensing

> >> > Event Category: None

> >> > Event ID: 45

> >> > Date: 8/10/2007

> >> > Time: 11:57:56 AM

> >> > User: N/A

> >> > Computer:

> >> > Description:

> >> > A license could not be issued to XX.XX.XX.XX because it is

> >> > not a member of the Terminal Server Computers group.

> >> >

> >> > For more information, see Help and Support Center at

> >> > http://go.microsoft.com/fwlink/events.asp.

> >> > ---------------------------------------------------

> >> >

> >> > The Terminal Server is a member of the Terminal Server

> >> > Computers group, but for some reason the Licensing Server

> >> > cannot resolve the IP Address of the Terminal Server even

> >> > though both servers use the same DNS Server, and the

> >> > Licensing Server can resolve the IP Address fine via DNS.

> >> >

> >> > Rebooting the Terminal Server seems to resolve the issue

> >> > (until the next power outage)

> >> >

> >> > Does anyone know a fix for this?

> >> >

> >> > Thank you in advance ....

> >> >

> >> > Darryl Smith

>

[Guest Vera Noest [MVP]]

Re: Licensing Server Not Resolve IP Address of Terminal Server

 

Sounds even more weird!

I'd start by focusing on the first problem, though, that all

servers request a TS CAL when clients connect to them. I assume

that these other servers (the DCs and members servers) only have

Remote Desktop for Administration enabled, i.e. Terminal Services

is *not* installed on them?

 

_________________________________________________________

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?RGFycnlsIFNtaXRo?=

<DarrylSmith@discussions.microsoft.com> wrote on 20 nov 2007 in

microsoft.public.windows.terminal_services:

> No .... The Terminal Server is requesting a TS CAL from the

> Licensing Server fine. It's just that the Licensing Server

> allocate a TS-CAL.

>

> I know it's hard to follow so I decided to try and re-write the

> whole situation so it's (possibly) easier to follow .....

>

> I had to implement the "License Server Security Group" policy on

> my Licensing Server because my Windows 2003 Domain Controllers

> and non-Terminal Server Member Servers were requesting and

> dishing out TS-CALs to any workstation that RDP'ed to them.

>

> Now, I seem to be getting this issue come up every so often. I

> haven't been able to pick what the root cause of the issue is

> yet, but the majority of the time, a reboot of the Terminal

> Server will work (why I don't know either). Basically what's

> happening is this .....

>

> A user is getting the following error message on their

> workstation when they try to RDP to the Terminal Server:

> "The remote session was disconnected because there are no

> Terminal Server client access licenses avaiable for this

> computer."

>

> When I check the System Log on the Terminal Server, I get the

> following event: "This Terminal Server is not able to

> communicate with the License Server. Please make sure that this

> Terminal Server's computer account is a member of the "Terminal

> Server Computers" group on the License Server"

>

> When I check the System Log on the License Server, I get the

> following event: "A license could not be issue to xx.xx.xx.xx

> [iP Address of the Terminal Server] because it is not a member

> of the Terminal Server Computers group."

>

> Basically what is happening is that the Licensing Server is not

> resolving the Computer Name of the Terminal Server from its IP

> Address.

>

> The Terminal Server is discovering and requesting a TS-CAL from

> the Licensing Server, but the Licensing Server won't dish out

> the TS-CAL.

>

> I hope I've explained the situation a bit better.

>

> Thanks for your help thus far.

>

> Regards,

> Darryl Smith

>

> "Vera Noest [MVP]" wrote:

>

>> Let me see if I understand you correctly: clients connect to

>> the real TS and the TS requests a TS CAL from just about any

>> server on the network, which in their turn forward the request

>> to the real TS Licensing Server? Can you confirm that this is

>> your situation?

>>

>> It sounds weird! Have you run lsview from the Resource Kit to

>> check which servers are recognized as TS Licensing Servers?

>> Also have a look in AD, under LDAP://CN=TS-Enterprise-License-

>> Server,CN=site-name,CN=sites,CN=configuration,DC=domainname,DC=c

>> om

>>

>> Can you fix the problem by configuring the TS with a list of

>> preferred TS Licensing Servers, in tscc.msc or a GPO?

>>

>> _________________________________________________________

>> 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?RGFycnlsIFNtaXRo?=

>> <DarrylSmith@discussions.microsoft.com> wrote on 19 nov 2007 in

>> microsoft.public.windows.terminal_services:

>>

>> > Update ....

>> >

>> > It seems that power outages aren't part of the issue as

>> > another Terminal Server & Licensing Server I have setup in

>> > our Datacentre also experiences the same issue.

>> >

>> > Discovering the License Server is not the issue as the

>> > Terminal Server is requesting a TS-CAL from the License

>> > server fine. The issue is that the License Server is

>> > producing the Error Message in the System Log of the License

>> > Server. The workstation that is trying to remote to the

>> > Terminal Server is getting a "The remote session was

>> > disconnected because there are no Terminal Server client

>> > access licenses available for this computer"

>> >

>> > I've had to implement the "License Server Security Group" to

>> > stop our Windows 2003 Domain Controllers and non-Terminal

>> > Server Member Servers from requesting TS-CALs.

>> >

>> > Not sure what the reason is for the Terminal Server to

>> > suddenly request TS-CALs using its IP Address rather than its

>> > Computer Name. Nothing in the Event Logs indicate anything

>> > failing.

>> >

>> > Has anyone come across this issue before?

>> >

>> > Regards,

>> > Darryl Smith

>> >

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

>> >

>> >> My first thought after reading your post was that you really

>> >> should try to fix these power outages. A decent UPS is not

>> >> too expensive and can save you a lot of trouble.

>> >>

>> >> That said, it sounds to me as if there could be a timing

>> >> problem, with the TS maybe powering up faster than the LS

>> >> does. Just a guess, though. Here's an article which

>> >> describes how this could happen, assuming that there are

>> >> multiple LS Licensing Server Security groups in your domain:

>> >> 918658 - Some Windows Server 2003-based terminal servers

>> >> cannot acquire a license when there is more than one License

>> >> Server security group

>> >> http://support.microsoft.com/?kbid=918658

>> >>

>> >> You could test this by taking them down in a controlled

>> >> experiment and then power them up manually to see what

>> >> happens.

>> >>

>> >> If this really is the cause, it's yet another argument for

>> >> an UPS, because most UPS managing software gives you the

>> >> possibility to built in a waiting period for some servers,

>> >> which must be started after other servers have come online.

>> >> _________________________________________________________

>> >> 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?RGFycnlsIFNtaXRo?=

>> >> <DarrylSmith@discussions.microsoft.com> wrote on 08 okt 2007

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

>> >>

>> >> > I have set up the License Server Security Group setting on

>> >> > my Terminal Server Licensing Server which is running

>> >> > Windows 2003. The majority of the time it works fine,

>> >> > however, if there is a power outage, I get the following

>> >> > error message in the System Log:

>> >> >

>> >> > ---------------------------------------

>> >> > Event Type: Error

>> >> > Event Source: TermServLicensing

>> >> > Event Category: None

>> >> > Event ID: 45

>> >> > Date: 8/10/2007

>> >> > Time: 11:57:56 AM

>> >> > User: N/A

>> >> > Computer:

>> >> > Description:

>> >> > A license could not be issued to XX.XX.XX.XX because it is

>> >> > not a member of the Terminal Server Computers group.

>> >> >

>> >> > For more information, see Help and Support Center at

>> >> > http://go.microsoft.com/fwlink/events.asp.

>> >> > ---------------------------------------------------

>> >> >

>> >> > The Terminal Server is a member of the Terminal Server

>> >> > Computers group, but for some reason the Licensing Server

>> >> > cannot resolve the IP Address of the Terminal Server even

>> >> > though both servers use the same DNS Server, and the

>> >> > Licensing Server can resolve the IP Address fine via DNS.

>> >> >

>> >> > Rebooting the Terminal Server seems to resolve the issue

>> >> > (until the next power outage)

>> >> >

>> >> > Does anyone know a fix for this?

>> >> >

>> >> > Thank you in advance ....

>> >> >

>> >> > Darryl Smith

[Guest Darryl Smith]

Re: Licensing Server Not Resolve IP Address of Terminal Server

 

That's correct, yes.

 

"Vera Noest [MVP]" wrote:

> Sounds even more weird!

> I'd start by focusing on the first problem, though, that all

> servers request a TS CAL when clients connect to them. I assume

> that these other servers (the DCs and members servers) only have

> Remote Desktop for Administration enabled, i.e. Terminal Services

> is *not* installed on them?

>

> _________________________________________________________

> 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?RGFycnlsIFNtaXRo?=

> <DarrylSmith@discussions.microsoft.com> wrote on 20 nov 2007 in

> microsoft.public.windows.terminal_services:

>

> > No .... The Terminal Server is requesting a TS CAL from the

> > Licensing Server fine. It's just that the Licensing Server

> > allocate a TS-CAL.

> >

> > I know it's hard to follow so I decided to try and re-write the

> > whole situation so it's (possibly) easier to follow .....

> >

> > I had to implement the "License Server Security Group" policy on

> > my Licensing Server because my Windows 2003 Domain Controllers

> > and non-Terminal Server Member Servers were requesting and

> > dishing out TS-CALs to any workstation that RDP'ed to them.

> >

> > Now, I seem to be getting this issue come up every so often. I

> > haven't been able to pick what the root cause of the issue is

> > yet, but the majority of the time, a reboot of the Terminal

> > Server will work (why I don't know either). Basically what's

> > happening is this .....

> >

> > A user is getting the following error message on their

> > workstation when they try to RDP to the Terminal Server:

> > "The remote session was disconnected because there are no

> > Terminal Server client access licenses avaiable for this

> > computer."

> >

> > When I check the System Log on the Terminal Server, I get the

> > following event: "This Terminal Server is not able to

> > communicate with the License Server. Please make sure that this

> > Terminal Server's computer account is a member of the "Terminal

> > Server Computers" group on the License Server"

> >

> > When I check the System Log on the License Server, I get the

> > following event: "A license could not be issue to xx.xx.xx.xx

> > [iP Address of the Terminal Server] because it is not a member

> > of the Terminal Server Computers group."

> >

> > Basically what is happening is that the Licensing Server is not

> > resolving the Computer Name of the Terminal Server from its IP

> > Address.

> >

> > The Terminal Server is discovering and requesting a TS-CAL from

> > the Licensing Server, but the Licensing Server won't dish out

> > the TS-CAL.

> >

> > I hope I've explained the situation a bit better.

> >

> > Thanks for your help thus far.

> >

> > Regards,

> > Darryl Smith

> >

> > "Vera Noest [MVP]" wrote:

> >

> >> Let me see if I understand you correctly: clients connect to

> >> the real TS and the TS requests a TS CAL from just about any

> >> server on the network, which in their turn forward the request

> >> to the real TS Licensing Server? Can you confirm that this is

> >> your situation?

> >>

> >> It sounds weird! Have you run lsview from the Resource Kit to

> >> check which servers are recognized as TS Licensing Servers?

> >> Also have a look in AD, under LDAP://CN=TS-Enterprise-License-

> >> Server,CN=site-name,CN=sites,CN=configuration,DC=domainname,DC=c

> >> om

> >>

> >> Can you fix the problem by configuring the TS with a list of

> >> preferred TS Licensing Servers, in tscc.msc or a GPO?

> >>

> >> _________________________________________________________

> >> 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?RGFycnlsIFNtaXRo?=

> >> <DarrylSmith@discussions.microsoft.com> wrote on 19 nov 2007 in

> >> microsoft.public.windows.terminal_services:

> >>

> >> > Update ....

> >> >

> >> > It seems that power outages aren't part of the issue as

> >> > another Terminal Server & Licensing Server I have setup in

> >> > our Datacentre also experiences the same issue.

> >> >

> >> > Discovering the License Server is not the issue as the

> >> > Terminal Server is requesting a TS-CAL from the License

> >> > server fine. The issue is that the License Server is

> >> > producing the Error Message in the System Log of the License

> >> > Server. The workstation that is trying to remote to the

> >> > Terminal Server is getting a "The remote session was

> >> > disconnected because there are no Terminal Server client

> >> > access licenses available for this computer"

> >> >

> >> > I've had to implement the "License Server Security Group" to

> >> > stop our Windows 2003 Domain Controllers and non-Terminal

> >> > Server Member Servers from requesting TS-CALs.

> >> >

> >> > Not sure what the reason is for the Terminal Server to

> >> > suddenly request TS-CALs using its IP Address rather than its

> >> > Computer Name. Nothing in the Event Logs indicate anything

> >> > failing.

> >> >

> >> > Has anyone come across this issue before?

> >> >

> >> > Regards,

> >> > Darryl Smith

> >> >

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

> >> >

> >> >> My first thought after reading your post was that you really

> >> >> should try to fix these power outages. A decent UPS is not

> >> >> too expensive and can save you a lot of trouble.

> >> >>

> >> >> That said, it sounds to me as if there could be a timing

> >> >> problem, with the TS maybe powering up faster than the LS

> >> >> does. Just a guess, though. Here's an article which

> >> >> describes how this could happen, assuming that there are

> >> >> multiple LS Licensing Server Security groups in your domain:

> >> >> 918658 - Some Windows Server 2003-based terminal servers

> >> >> cannot acquire a license when there is more than one License

> >> >> Server security group

> >> >> http://support.microsoft.com/?kbid=918658

> >> >>

> >> >> You could test this by taking them down in a controlled

> >> >> experiment and then power them up manually to see what

> >> >> happens.

> >> >>

> >> >> If this really is the cause, it's yet another argument for

> >> >> an UPS, because most UPS managing software gives you the

> >> >> possibility to built in a waiting period for some servers,

> >> >> which must be started after other servers have come online.

> >> >> _________________________________________________________

> >> >> 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?RGFycnlsIFNtaXRo?=

> >> >> <DarrylSmith@discussions.microsoft.com> wrote on 08 okt 2007

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

> >> >>

> >> >> > I have set up the License Server Security Group setting on

> >> >> > my Terminal Server Licensing Server which is running

> >> >> > Windows 2003. The majority of the time it works fine,

> >> >> > however, if there is a power outage, I get the following

> >> >> > error message in the System Log:

> >> >> >

> >> >> > ---------------------------------------

> >> >> > Event Type: Error

> >> >> > Event Source: TermServLicensing

> >> >> > Event Category: None

> >> >> > Event ID: 45

> >> >> > Date: 8/10/2007

> >> >> > Time: 11:57:56 AM

> >> >> > User: N/A

> >> >> > Computer:

> >> >> > Description:

> >> >> > A license could not be issued to XX.XX.XX.XX because it is

> >> >> > not a member of the Terminal Server Computers group.

> >> >> >

> >> >> > For more information, see Help and Support Center at

> >> >> > http://go.microsoft.com/fwlink/events.asp.

> >> >> > ---------------------------------------------------

> >> >> >

> >> >> > The Terminal Server is a member of the Terminal Server

> >> >> > Computers group, but for some reason the Licensing Server

> >> >> > cannot resolve the IP Address of the Terminal Server even

> >> >> > though both servers use the same DNS Server, and the

> >> >> > Licensing Server can resolve the IP Address fine via DNS.

> >> >> >

> >> >> > Rebooting the Terminal Server seems to resolve the issue

> >> >> > (until the next power outage)

> >> >> >

> >> >> > Does anyone know a fix for this?

> >> >> >

> >> >> > Thank you in advance ....

> >> >> >

> >> >> > Darryl Smith

>

[Guest Vera Noest [MVP]]

Re: Licensing Server Not Resolve IP Address of Terminal Server

 

Then I would call Microsoft Support.

I can't remember that I have ever read about a similar issue here,

a RDfA enabled server requesting TS CALs.

_________________________________________________________

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?RGFycnlsIFNtaXRo?=

<DarrylSmith@discussions.microsoft.com> wrote on 20 nov 2007 in

microsoft.public.windows.terminal_services:

> That's correct, yes.

>

> "Vera Noest [MVP]" wrote:

>

>> Sounds even more weird!

>> I'd start by focusing on the first problem, though, that all

>> servers request a TS CAL when clients connect to them. I assume

>> that these other servers (the DCs and members servers) only

>> have Remote Desktop for Administration enabled, i.e. Terminal

>> Services is *not* installed on them?

>>

>> _________________________________________________________

>> 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?RGFycnlsIFNtaXRo?=

>> <DarrylSmith@discussions.microsoft.com> wrote on 20 nov 2007 in

>> microsoft.public.windows.terminal_services:

>>

>> > No .... The Terminal Server is requesting a TS CAL from the

>> > Licensing Server fine. It's just that the Licensing Server

>> > allocate a TS-CAL.

>> >

>> > I know it's hard to follow so I decided to try and re-write

>> > the whole situation so it's (possibly) easier to follow .....

>> >

>> > I had to implement the "License Server Security Group" policy

>> > on my Licensing Server because my Windows 2003 Domain

>> > Controllers and non-Terminal Server Member Servers were

>> > requesting and dishing out TS-CALs to any workstation that

>> > RDP'ed to them.

>> >

>> > Now, I seem to be getting this issue come up every so often.

>> > I haven't been able to pick what the root cause of the issue

>> > is yet, but the majority of the time, a reboot of the

>> > Terminal Server will work (why I don't know either).

>> > Basically what's happening is this .....

>> >

>> > A user is getting the following error message on their

>> > workstation when they try to RDP to the Terminal Server:

>> > "The remote session was disconnected because there are no

>> > Terminal Server client access licenses avaiable for this

>> > computer."

>> >

>> > When I check the System Log on the Terminal Server, I get the

>> > following event: "This Terminal Server is not able to

>> > communicate with the License Server. Please make sure that

>> > this Terminal Server's computer account is a member of the

>> > "Terminal Server Computers" group on the License Server"

>> >

>> > When I check the System Log on the License Server, I get the

>> > following event: "A license could not be issue to xx.xx.xx.xx

>> > [iP Address of the Terminal Server] because it is not a

>> > member of the Terminal Server Computers group."

>> >

>> > Basically what is happening is that the Licensing Server is

>> > not resolving the Computer Name of the Terminal Server from

>> > its IP Address.

>> >

>> > The Terminal Server is discovering and requesting a TS-CAL

>> > from the Licensing Server, but the Licensing Server won't

>> > dish out the TS-CAL.

>> >

>> > I hope I've explained the situation a bit better.

>> >

>> > Thanks for your help thus far.

>> >

>> > Regards,

>> > Darryl Smith

>> >

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

>> >

>> >> Let me see if I understand you correctly: clients connect to

>> >> the real TS and the TS requests a TS CAL from just about any

>> >> server on the network, which in their turn forward the

>> >> request to the real TS Licensing Server? Can you confirm

>> >> that this is your situation?

>> >>

>> >> It sounds weird! Have you run lsview from the Resource Kit

>> >> to check which servers are recognized as TS Licensing

>> >> Servers? Also have a look in AD, under

>> >> LDAP://CN=TS-Enterprise-License-

>> >> Server,CN=site-name,CN=sites,CN=configuration,DC=domainname,D

>> >> C=c om

>> >>

>> >> Can you fix the problem by configuring the TS with a list of

>> >> preferred TS Licensing Servers, in tscc.msc or a GPO?

>> >>

>> >> _________________________________________________________

>> >> 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?RGFycnlsIFNtaXRo?=

>> >> <DarrylSmith@discussions.microsoft.com> wrote on 19 nov 2007

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

>> >>

>> >> > Update ....

>> >> >

>> >> > It seems that power outages aren't part of the issue as

>> >> > another Terminal Server & Licensing Server I have setup in

>> >> > our Datacentre also experiences the same issue.

>> >> >

>> >> > Discovering the License Server is not the issue as the

>> >> > Terminal Server is requesting a TS-CAL from the License

>> >> > server fine. The issue is that the License Server is

>> >> > producing the Error Message in the System Log of the

>> >> > License Server. The workstation that is trying to remote

>> >> > to the Terminal Server is getting a "The remote session

>> >> > was disconnected because there are no Terminal Server

>> >> > client access licenses available for this computer"

>> >> >

>> >> > I've had to implement the "License Server Security Group"

>> >> > to stop our Windows 2003 Domain Controllers and

>> >> > non-Terminal Server Member Servers from requesting

>> >> > TS-CALs.

>> >> >

>> >> > Not sure what the reason is for the Terminal Server to

>> >> > suddenly request TS-CALs using its IP Address rather than

>> >> > its Computer Name. Nothing in the Event Logs indicate

>> >> > anything failing.

>> >> >

>> >> > Has anyone come across this issue before?

>> >> >

>> >> > Regards,

>> >> > Darryl Smith

>> >> >

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

>> >> >

>> >> >> My first thought after reading your post was that you

>> >> >> really should try to fix these power outages. A decent

>> >> >> UPS is not too expensive and can save you a lot of

>> >> >> trouble.

>> >> >>

>> >> >> That said, it sounds to me as if there could be a timing

>> >> >> problem, with the TS maybe powering up faster than the LS

>> >> >> does. Just a guess, though. Here's an article which

>> >> >> describes how this could happen, assuming that there are

>> >> >> multiple LS Licensing Server Security groups in your

>> >> >> domain: 918658 - Some Windows Server 2003-based terminal

>> >> >> servers cannot acquire a license when there is more than

>> >> >> one License Server security group

>> >> >> http://support.microsoft.com/?kbid=918658

>> >> >>

>> >> >> You could test this by taking them down in a controlled

>> >> >> experiment and then power them up manually to see what

>> >> >> happens.

>> >> >>

>> >> >> If this really is the cause, it's yet another argument

>> >> >> for an UPS, because most UPS managing software gives you

>> >> >> the possibility to built in a waiting period for some

>> >> >> servers, which must be started after other servers have

>> >> >> come online.

>> >> >> _________________________________________________________

>> >> >> 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?RGFycnlsIFNtaXRo?=

>> >> >> <DarrylSmith@discussions.microsoft.com> wrote on 08 okt

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

>> >> >>

>> >> >> > I have set up the License Server Security Group setting

>> >> >> > on my Terminal Server Licensing Server which is running

>> >> >> > Windows 2003. The majority of the time it works fine,

>> >> >> > however, if there is a power outage, I get the

>> >> >> > following error message in the System Log:

>> >> >> >

>> >> >> > ---------------------------------------

>> >> >> > Event Type: Error

>> >> >> > Event Source: TermServLicensing

>> >> >> > Event Category: None

>> >> >> > Event ID: 45

>> >> >> > Date: 8/10/2007

>> >> >> > Time: 11:57:56 AM

>> >> >> > User: N/A

>> >> >> > Computer:

>> >> >> > Description:

>> >> >> > A license could not be issued to XX.XX.XX.XX because it

>> >> >> > is not a member of the Terminal Server Computers group.

>> >> >> >

>> >> >> > For more information, see Help and Support Center at

>> >> >> > http://go.microsoft.com/fwlink/events.asp.

>> >> >> > ---------------------------------------------------

>> >> >> >

>> >> >> > The Terminal Server is a member of the Terminal Server

>> >> >> > Computers group, but for some reason the Licensing

>> >> >> > Server cannot resolve the IP Address of the Terminal

>> >> >> > Server even though both servers use the same DNS

>> >> >> > Server, and the Licensing Server can resolve the IP

>> >> >> > Address fine via DNS.

>> >> >> >

>> >> >> > Rebooting the Terminal Server seems to resolve the

>> >> >> > issue (until the next power outage)

>> >> >> >

>> >> >> > Does anyone know a fix for this?

>> >> >> >

>> >> >> > Thank you in advance ....

>> >> >> >

>> >> >> > Darryl Smith