Windows NT TSL

  • Thread starter Thread starter Jason
  • Start date Start date
J

Jason

Configuring Terminal Services in a test lab just for the practice of
installation and configuration. Using Eval copy of 03 from the MSPRESS
self-paced training kit.

Set up three servers-- one DC, two member servers. Configured both severs
as Term Servers. Installed Term Serv Licensing on SRV1. From SRV2- I can
terminal into SRV1 without issue.

From SRV1- I cannot terminal into SRV2. I receive a lengthy logon message
relating to permissions and RDP membership. RDP membership is fine, rights
are fine, etc. If I install another Term Serv Licensing server also on
SRV2- error goes away.

Did it again- one way. TSL was on SRV1, TS on SRV2. Could not Terminal
into SRV2 unless TSL was locally installed.

Can someone explain to me why TSL needs to be local? All machines are part
of the same domain. Is this a name resolution issue? DNS appears to be
fine.

Jason Yates
 
No, it's not a name resolution problem, it's a TS Licensing Service
discovery problem.

I assume that you installed your TS Licensing Server on SVR1 as a
Domain LS, correct?
If so, then it is by design that SVR2 cannot find it. A Domain LS
which does not run on a DC is not automatically discovered. It
would have been if you had installed the TSLS as a Domain LS on the
DC, or as an Enterprise LS on a member server (which publishes it
in Active Directory).

This is documented here:

301932 - Terminal Services Licensing service discovery
http://support.microsoft.com/?kbid=301932

You can solve the problem by defining a preferred TSLS on both
servers. This can be done:
1) in Terminal Services Configuration - Server settings
2) in the registry
279561 - How to Override the License Server Discovery Process in
Windows Server 2003 Terminal Services
http://support.microsoft.com/?kbid=279561
3) in a Group Policy:
Computer Configuration - Administrative templates - Windows
Components - Terminal Services
"Use the specified Terminal Server license servers"

Also make sure that you run SP2 on all servers, since it fixes a
number of problems related to Terminal Server (Licensing).

_________________________________________________________
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?SmFzb24=?= <Jason@discussions.microsoft.com> wrote on 18
jul 2007 in microsoft.public.windows.terminal_services:

> Configuring Terminal Services in a test lab just for the
> practice of installation and configuration. Using Eval copy of
> 03 from the MSPRESS self-paced training kit.
>
> Set up three servers-- one DC, two member servers. Configured
> both severs as Term Servers. Installed Term Serv Licensing on
> SRV1. From SRV2- I can terminal into SRV1 without issue.
>
> From SRV1- I cannot terminal into SRV2. I receive a lengthy
> logon message relating to permissions and RDP membership. RDP
> membership is fine, rights are fine, etc. If I install another
> Term Serv Licensing server also on SRV2- error goes away.
>
> Did it again- one way. TSL was on SRV1, TS on SRV2. Could not
> Terminal into SRV2 unless TSL was locally installed.
>
> Can someone explain to me why TSL needs to be local? All
> machines are part of the same domain. Is this a name
> resolution issue? DNS appears to be fine.
>
> Jason Yates
 
Cool! This is good info . . . however, I installed it as an Enterprise LS--
I'm confident of this fact b/c I walked through this process about four
times. All four times was the same single DC setup so no replication issues.
The TLS servers were on member servers and part of the domain. I'll look in
AD for the "publishing" info. I'm assuming it's on the properties of the
server object.

I'll look over the KB articles too! Thanks a bunch!

Jason Yates

"Vera Noest [MVP]" wrote:

> No, it's not a name resolution problem, it's a TS Licensing Service
> discovery problem.
>
> I assume that you installed your TS Licensing Server on SVR1 as a
> Domain LS, correct?
> If so, then it is by design that SVR2 cannot find it. A Domain LS
> which does not run on a DC is not automatically discovered. It
> would have been if you had installed the TSLS as a Domain LS on the
> DC, or as an Enterprise LS on a member server (which publishes it
> in Active Directory).
>
> This is documented here:
>
> 301932 - Terminal Services Licensing service discovery
> http://support.microsoft.com/?kbid=301932
>
> You can solve the problem by defining a preferred TSLS on both
> servers. This can be done:
> 1) in Terminal Services Configuration - Server settings
> 2) in the registry
> 279561 - How to Override the License Server Discovery Process in
> Windows Server 2003 Terminal Services
> http://support.microsoft.com/?kbid=279561
> 3) in a Group Policy:
> Computer Configuration - Administrative templates - Windows
> Components - Terminal Services
> "Use the specified Terminal Server license servers"
>
> Also make sure that you run SP2 on all servers, since it fixes a
> number of problems related to Terminal Server (Licensing).
>
> _________________________________________________________
> 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?SmFzb24=?= <Jason@discussions.microsoft.com> wrote on 18
> jul 2007 in microsoft.public.windows.terminal_services:
>
> > Configuring Terminal Services in a test lab just for the
> > practice of installation and configuration. Using Eval copy of
> > 03 from the MSPRESS self-paced training kit.
> >
> > Set up three servers-- one DC, two member servers. Configured
> > both severs as Term Servers. Installed Term Serv Licensing on
> > SRV1. From SRV2- I can terminal into SRV1 without issue.
> >
> > From SRV1- I cannot terminal into SRV2. I receive a lengthy
> > logon message relating to permissions and RDP membership. RDP
> > membership is fine, rights are fine, etc. If I install another
> > Term Serv Licensing server also on SRV2- error goes away.
> >
> > Did it again- one way. TSL was on SRV1, TS on SRV2. Could not
> > Terminal into SRV2 unless TSL was locally installed.
> >
> > Can someone explain to me why TSL needs to be local? All
> > machines are part of the same domain. Is this a name
> > resolution issue? DNS appears to be fine.
> >
> > Jason Yates
>
 
OK, you might have this problem:

895151 - Windows Server 2003-based or Windows 2000-based terminal
servers do not automatically discover a license server that is
designated as an enterprise license server
http://support.microsoft.com/?kbid=895151

_________________________________________________________
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?SmFzb24=?= <Jason@discussions.microsoft.com> wrote on 18
jul 2007 in microsoft.public.windows.terminal_services:

> Cool! This is good info . . . however, I installed it as an
> Enterprise LS-- I'm confident of this fact b/c I walked through
> this process about four times. All four times was the same
> single DC setup so no replication issues.
> The TLS servers were on member servers and part of the domain.
> I'll look in
> AD for the "publishing" info. I'm assuming it's on the
> properties of the server object.
>
> I'll look over the KB articles too! Thanks a bunch!
>
> Jason Yates
>
> "Vera Noest [MVP]" wrote:
>
>> No, it's not a name resolution problem, it's a TS Licensing
>> Service discovery problem.
>>
>> I assume that you installed your TS Licensing Server on SVR1 as
>> a Domain LS, correct?
>> If so, then it is by design that SVR2 cannot find it. A Domain
>> LS which does not run on a DC is not automatically discovered.
>> It would have been if you had installed the TSLS as a Domain LS
>> on the DC, or as an Enterprise LS on a member server (which
>> publishes it in Active Directory).
>>
>> This is documented here:
>>
>> 301932 - Terminal Services Licensing service discovery
>> http://support.microsoft.com/?kbid=301932
>>
>> You can solve the problem by defining a preferred TSLS on both
>> servers. This can be done:
>> 1) in Terminal Services Configuration - Server settings
>> 2) in the registry
>> 279561 - How to Override the License Server Discovery Process
>> in Windows Server 2003 Terminal Services
>> http://support.microsoft.com/?kbid=279561
>> 3) in a Group Policy:
>> Computer Configuration - Administrative templates - Windows
>> Components - Terminal Services
>> "Use the specified Terminal Server license servers"
>>
>> Also make sure that you run SP2 on all servers, since it fixes
>> a number of problems related to Terminal Server (Licensing).
>>
>> _________________________________________________________
>> 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?SmFzb24=?= <Jason@discussions.microsoft.com> wrote on
>> 18 jul 2007 in microsoft.public.windows.terminal_services:
>>
>> > Configuring Terminal Services in a test lab just for the
>> > practice of installation and configuration. Using Eval copy
>> > of 03 from the MSPRESS self-paced training kit.
>> >
>> > Set up three servers-- one DC, two member servers.
>> > Configured both severs as Term Servers. Installed Term Serv
>> > Licensing on SRV1. From SRV2- I can terminal into SRV1
>> > without issue.
>> >
>> > From SRV1- I cannot terminal into SRV2. I receive a lengthy
>> > logon message relating to permissions and RDP membership.
>> > RDP membership is fine, rights are fine, etc. If I install
>> > another Term Serv Licensing server also on SRV2- error goes
>> > away.
>> >
>> > Did it again- one way. TSL was on SRV1, TS on SRV2. Could
>> > not Terminal into SRV2 unless TSL was locally installed.
>> >
>> > Can someone explain to me why TSL needs to be local? All
>> > machines are part of the same domain. Is this a name
>> > resolution issue? DNS appears to be fine.
>> >
>> > Jason Yates
 
Cool. It certainly matches my symptoms. I'll try to test it out. Thanks!

"Vera Noest [MVP]" wrote:

> OK, you might have this problem:
>
> 895151 - Windows Server 2003-based or Windows 2000-based terminal
> servers do not automatically discover a license server that is
> designated as an enterprise license server
> http://support.microsoft.com/?kbid=895151
>
> _________________________________________________________
> 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?SmFzb24=?= <Jason@discussions.microsoft.com> wrote on 18
> jul 2007 in microsoft.public.windows.terminal_services:
>
> > Cool! This is good info . . . however, I installed it as an
> > Enterprise LS-- I'm confident of this fact b/c I walked through
> > this process about four times. All four times was the same
> > single DC setup so no replication issues.
> > The TLS servers were on member servers and part of the domain.
> > I'll look in
> > AD for the "publishing" info. I'm assuming it's on the
> > properties of the server object.
> >
> > I'll look over the KB articles too! Thanks a bunch!
> >
> > Jason Yates
> >
> > "Vera Noest [MVP]" wrote:
> >
> >> No, it's not a name resolution problem, it's a TS Licensing
> >> Service discovery problem.
> >>
> >> I assume that you installed your TS Licensing Server on SVR1 as
> >> a Domain LS, correct?
> >> If so, then it is by design that SVR2 cannot find it. A Domain
> >> LS which does not run on a DC is not automatically discovered.
> >> It would have been if you had installed the TSLS as a Domain LS
> >> on the DC, or as an Enterprise LS on a member server (which
> >> publishes it in Active Directory).
> >>
> >> This is documented here:
> >>
> >> 301932 - Terminal Services Licensing service discovery
> >> http://support.microsoft.com/?kbid=301932
> >>
> >> You can solve the problem by defining a preferred TSLS on both
> >> servers. This can be done:
> >> 1) in Terminal Services Configuration - Server settings
> >> 2) in the registry
> >> 279561 - How to Override the License Server Discovery Process
> >> in Windows Server 2003 Terminal Services
> >> http://support.microsoft.com/?kbid=279561
> >> 3) in a Group Policy:
> >> Computer Configuration - Administrative templates - Windows
> >> Components - Terminal Services
> >> "Use the specified Terminal Server license servers"
> >>
> >> Also make sure that you run SP2 on all servers, since it fixes
> >> a number of problems related to Terminal Server (Licensing).
> >>
> >> _________________________________________________________
> >> 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?SmFzb24=?= <Jason@discussions.microsoft.com> wrote on
> >> 18 jul 2007 in microsoft.public.windows.terminal_services:
> >>
> >> > Configuring Terminal Services in a test lab just for the
> >> > practice of installation and configuration. Using Eval copy
> >> > of 03 from the MSPRESS self-paced training kit.
> >> >
> >> > Set up three servers-- one DC, two member servers.
> >> > Configured both severs as Term Servers. Installed Term Serv
> >> > Licensing on SRV1. From SRV2- I can terminal into SRV1
> >> > without issue.
> >> >
> >> > From SRV1- I cannot terminal into SRV2. I receive a lengthy
> >> > logon message relating to permissions and RDP membership.
> >> > RDP membership is fine, rights are fine, etc. If I install
> >> > another Term Serv Licensing server also on SRV2- error goes
> >> > away.
> >> >
> >> > Did it again- one way. TSL was on SRV1, TS on SRV2. Could
> >> > not Terminal into SRV2 unless TSL was locally installed.
> >> >
> >> > Can someone explain to me why TSL needs to be local? All
> >> > machines are part of the same domain. Is this a name
> >> > resolution issue? DNS appears to be fine.
> >> >
> >> > Jason Yates
>
 
Back
Top