Windows NT Win2K TS's can't connect to Win2k3 license server in remote subnet

  • Thread starter Thread starter Mizzleman
  • Start date Start date
M

Mizzleman

Hello,

I have 3 Win2k TS's that can cannot connect to a Win2k3 license server in a
remote subnet, same domain. It was working fine until yesterday. I have not
changed anything on the servers. Some patches were installed on 7/13/2007. I
have set the default license server registry key for the license server. I
ran a protocol analyzer when I run the TS Licensing tool on the TS as it
tries to find the license server. After looking throught the analysis, it
shows the LDAP query and getting the license server info, but the TS still
can't connect to it. What is going on? This is a major production outage so
a quick response is appreciated. Thanks.
 
Are there any errors or warnings in the EventLog on either the
terminal servers or the TS Licensing Server?
Do you also have Terminal Servers on the same subnet as the TS LS?
If so, can they connect?
Which SP is the TS LS running?
Is there a firewall between the TS and the TS LS?

_________________________________________________________
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?TWl6emxlbWFu?= <Mizzleman@discussions.microsoft.com>
wrote on 15 aug 2007 in
microsoft.public.windows.terminal_services:

> Hello,
>
> I have 3 Win2k TS's that can cannot connect to a Win2k3 license
> server in a remote subnet, same domain. It was working fine
> until yesterday. I have not changed anything on the servers.
> Some patches were installed on 7/13/2007. I have set the default
> license server registry key for the license server. I ran a
> protocol analyzer when I run the TS Licensing tool on the TS as
> it tries to find the license server. After looking throught the
> analysis, it shows the LDAP query and getting the license server
> info, but the TS still can't connect to it. What is going on?
> This is a major production outage so a quick response is
> appreciated. Thanks.
 
Re: Win2K TS's can't connect to Win2k3 license server in remote su

The TS is showing event id 1004. The license server is not showing any errors.
The TS and the license server are on the same subnet now. I was trying to
contact a license server on a remote subnet and that worked until yesterday
afternoon. We put a license server on the subnet to see if that would help. I
ran lsview before I put the license server in the subnet and it could not
find the license server. After putting the license server in the same subnet,
lsview can now find the license server. But the clients still cannot connect
and I get event 1004 in the event log of the TS. There are no firewalls in
between. The LS is Win2k3 SP2.

By the way, I was hoping you would respond. You've helped me in the past.
Anyway I can call you direct?

"Vera Noest [MVP]" wrote:

> Are there any errors or warnings in the EventLog on either the
> terminal servers or the TS Licensing Server?
> Do you also have Terminal Servers on the same subnet as the TS LS?
> If so, can they connect?
> Which SP is the TS LS running?
> Is there a firewall between the TS and the TS LS?
>
> _________________________________________________________
> 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?TWl6emxlbWFu?= <Mizzleman@discussions.microsoft.com>
> wrote on 15 aug 2007 in
> microsoft.public.windows.terminal_services:
>
> > Hello,
> >
> > I have 3 Win2k TS's that can cannot connect to a Win2k3 license
> > server in a remote subnet, same domain. It was working fine
> > until yesterday. I have not changed anything on the servers.
> > Some patches were installed on 7/13/2007. I have set the default
> > license server registry key for the license server. I ran a
> > protocol analyzer when I run the TS Licensing tool on the TS as
> > it tries to find the license server. After looking throught the
> > analysis, it shows the LDAP query and getting the license server
> > info, but the TS still can't connect to it. What is going on?
> > This is a major production outage so a quick response is
> > appreciated. Thanks.
>
 
Re: Win2K TS's can't connect to Win2k3 license server in remote su

OK, so now we have 2 problems :-)
Regarding the original LS in the remote subnet:
Can you ping it?
Have you verified that the TS Licensing Service is up and running?
Have you rebooted the server?
And:
> Do you also have Terminal Servers on the same subnet as the TS
> LS? If so, can they connect?

Regarding the new TS LS on the same subnet as the TS: did you
install any TS CALs on it? If not, it's not surprising that the
clients cannot connect, because they can't renew their licenses if
there aren't any.
Totally new clients should be able to get a temporary license,
though. To test if this works OK, you could delete the locally
stored license from a client which can't connect:

187614 - Removing Terminal Server Licenses from an RDP Client
http://support.microsoft.com/?kbid=187614

And no, I don't do private consulting, so no emails and no phone
calls, please.

_________________________________________________________
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?TWl6emxlbWFu?= <Mizzleman@discussions.microsoft.com>
wrote on 15 aug 2007 in
microsoft.public.windows.terminal_services:

> The TS is showing event id 1004. The license server is not
> showing any errors. The TS and the license server are on the
> same subnet now. I was trying to contact a license server on a
> remote subnet and that worked until yesterday afternoon. We put
> a license server on the subnet to see if that would help. I ran
> lsview before I put the license server in the subnet and it
> could not find the license server. After putting the license
> server in the same subnet, lsview can now find the license
> server. But the clients still cannot connect and I get event
> 1004 in the event log of the TS. There are no firewalls in
> between. The LS is Win2k3 SP2.
>
> By the way, I was hoping you would respond. You've helped me in
> the past. Anyway I can call you direct?
>
> "Vera Noest [MVP]" wrote:
>
>> Are there any errors or warnings in the EventLog on either the
>> terminal servers or the TS Licensing Server?
>> Do you also have Terminal Servers on the same subnet as the TS
>> LS? If so, can they connect?
>> Which SP is the TS LS running?
>> Is there a firewall between the TS and the TS LS?
>>
>> _________________________________________________________
>> 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?TWl6emxlbWFu?= <Mizzleman@discussions.microsoft.com>
>> wrote on 15 aug 2007 in
>> microsoft.public.windows.terminal_services:
>>
>> > Hello,
>> >
>> > I have 3 Win2k TS's that can cannot connect to a Win2k3
>> > license server in a remote subnet, same domain. It was
>> > working fine until yesterday. I have not changed anything on
>> > the servers. Some patches were installed on 7/13/2007. I have
>> > set the default license server registry key for the license
>> > server. I ran a protocol analyzer when I run the TS Licensing
>> > tool on the TS as it tries to find the license server. After
>> > looking throught the analysis, it shows the LDAP query and
>> > getting the license server info, but the TS still can't
>> > connect to it. What is going on? This is a major production
>> > outage so a quick response is appreciated. Thanks.
 
Re: Win2K TS's can't connect to Win2k3 license server in remote su

Vera,

I did a test. As the user that was having problems, I used my laptop to
start a RDP session to the TS and successfully logged on as the user.

I also did a test or two on the user's PC. I deleted the MSlicensing key and
rebooted. I was able to log on successfully once as the user, but can't
repeat it since. I can see where the license was issued from the TS License
server on the same subnet as the TS. Could this be strictly a client issue?
Do I have some corruption coming from somewhere on the TS's or TS license
server?

"Vera Noest [MVP]" wrote:

> OK, so now we have 2 problems :-)
> Regarding the original LS in the remote subnet:
> Can you ping it?
> Have you verified that the TS Licensing Service is up and running?
> Have you rebooted the server?
> And:
> > Do you also have Terminal Servers on the same subnet as the TS
> > LS? If so, can they connect?
>
> Regarding the new TS LS on the same subnet as the TS: did you
> install any TS CALs on it? If not, it's not surprising that the
> clients cannot connect, because they can't renew their licenses if
> there aren't any.
> Totally new clients should be able to get a temporary license,
> though. To test if this works OK, you could delete the locally
> stored license from a client which can't connect:
>
> 187614 - Removing Terminal Server Licenses from an RDP Client
> http://support.microsoft.com/?kbid=187614
>
> And no, I don't do private consulting, so no emails and no phone
> calls, please.
>
> _________________________________________________________
> 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?TWl6emxlbWFu?= <Mizzleman@discussions.microsoft.com>
> wrote on 15 aug 2007 in
> microsoft.public.windows.terminal_services:
>
> > The TS is showing event id 1004. The license server is not
> > showing any errors. The TS and the license server are on the
> > same subnet now. I was trying to contact a license server on a
> > remote subnet and that worked until yesterday afternoon. We put
> > a license server on the subnet to see if that would help. I ran
> > lsview before I put the license server in the subnet and it
> > could not find the license server. After putting the license
> > server in the same subnet, lsview can now find the license
> > server. But the clients still cannot connect and I get event
> > 1004 in the event log of the TS. There are no firewalls in
> > between. The LS is Win2k3 SP2.
> >
> > By the way, I was hoping you would respond. You've helped me in
> > the past. Anyway I can call you direct?
> >
> > "Vera Noest [MVP]" wrote:
> >
> >> Are there any errors or warnings in the EventLog on either the
> >> terminal servers or the TS Licensing Server?
> >> Do you also have Terminal Servers on the same subnet as the TS
> >> LS? If so, can they connect?
> >> Which SP is the TS LS running?
> >> Is there a firewall between the TS and the TS LS?
> >>
> >> _________________________________________________________
> >> 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?TWl6emxlbWFu?= <Mizzleman@discussions.microsoft.com>
> >> wrote on 15 aug 2007 in
> >> microsoft.public.windows.terminal_services:
> >>
> >> > Hello,
> >> >
> >> > I have 3 Win2k TS's that can cannot connect to a Win2k3
> >> > license server in a remote subnet, same domain. It was
> >> > working fine until yesterday. I have not changed anything on
> >> > the servers. Some patches were installed on 7/13/2007. I have
> >> > set the default license server registry key for the license
> >> > server. I ran a protocol analyzer when I run the TS Licensing
> >> > tool on the TS as it tries to find the license server. After
> >> > looking throught the analysis, it shows the LDAP query and
> >> > getting the license server info, but the TS still can't
> >> > connect to it. What is going on? This is a major production
> >> > outage so a quick response is appreciated. Thanks.
>
 
Re: Win2K TS's can't connect to Win2k3 license server in remote su

Vera,

Here is a little more information. If I delete the mslicensing registry key
off of the client, the client can connect. But if I try to connect again, it
won't work. If I delete the key again, it will work again.

"Mizzleman" wrote:

> Vera,
>
> I did a test. As the user that was having problems, I used my laptop to
> start a RDP session to the TS and successfully logged on as the user.
>
> I also did a test or two on the user's PC. I deleted the MSlicensing key and
> rebooted. I was able to log on successfully once as the user, but can't
> repeat it since. I can see where the license was issued from the TS License
> server on the same subnet as the TS. Could this be strictly a client issue?
> Do I have some corruption coming from somewhere on the TS's or TS license
> server?
>
> "Vera Noest [MVP]" wrote:
>
> > OK, so now we have 2 problems :-)
> > Regarding the original LS in the remote subnet:
> > Can you ping it?
> > Have you verified that the TS Licensing Service is up and running?
> > Have you rebooted the server?
> > And:
> > > Do you also have Terminal Servers on the same subnet as the TS
> > > LS? If so, can they connect?
> >
> > Regarding the new TS LS on the same subnet as the TS: did you
> > install any TS CALs on it? If not, it's not surprising that the
> > clients cannot connect, because they can't renew their licenses if
> > there aren't any.
> > Totally new clients should be able to get a temporary license,
> > though. To test if this works OK, you could delete the locally
> > stored license from a client which can't connect:
> >
> > 187614 - Removing Terminal Server Licenses from an RDP Client
> > http://support.microsoft.com/?kbid=187614
> >
> > And no, I don't do private consulting, so no emails and no phone
> > calls, please.
> >
> > _________________________________________________________
> > 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?TWl6emxlbWFu?= <Mizzleman@discussions.microsoft.com>
> > wrote on 15 aug 2007 in
> > microsoft.public.windows.terminal_services:
> >
> > > The TS is showing event id 1004. The license server is not
> > > showing any errors. The TS and the license server are on the
> > > same subnet now. I was trying to contact a license server on a
> > > remote subnet and that worked until yesterday afternoon. We put
> > > a license server on the subnet to see if that would help. I ran
> > > lsview before I put the license server in the subnet and it
> > > could not find the license server. After putting the license
> > > server in the same subnet, lsview can now find the license
> > > server. But the clients still cannot connect and I get event
> > > 1004 in the event log of the TS. There are no firewalls in
> > > between. The LS is Win2k3 SP2.
> > >
> > > By the way, I was hoping you would respond. You've helped me in
> > > the past. Anyway I can call you direct?
> > >
> > > "Vera Noest [MVP]" wrote:
> > >
> > >> Are there any errors or warnings in the EventLog on either the
> > >> terminal servers or the TS Licensing Server?
> > >> Do you also have Terminal Servers on the same subnet as the TS
> > >> LS? If so, can they connect?
> > >> Which SP is the TS LS running?
> > >> Is there a firewall between the TS and the TS LS?
> > >>
> > >> _________________________________________________________
> > >> 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?TWl6emxlbWFu?= <Mizzleman@discussions.microsoft.com>
> > >> wrote on 15 aug 2007 in
> > >> microsoft.public.windows.terminal_services:
> > >>
> > >> > Hello,
> > >> >
> > >> > I have 3 Win2k TS's that can cannot connect to a Win2k3
> > >> > license server in a remote subnet, same domain. It was
> > >> > working fine until yesterday. I have not changed anything on
> > >> > the servers. Some patches were installed on 7/13/2007. I have
> > >> > set the default license server registry key for the license
> > >> > server. I ran a protocol analyzer when I run the TS Licensing
> > >> > tool on the TS as it tries to find the license server. After
> > >> > looking throught the analysis, it shows the LDAP query and
> > >> > getting the license server info, but the TS still can't
> > >> > connect to it. What is going on? This is a major production
> > >> > outage so a quick response is appreciated. Thanks.
> >
 
Re: Win2K TS's can't connect to Win2k3 license server in remote su

Mizzleman, I can't help you if you don't answer my questions.

>> Regarding the new TS LS on the same subnet as the TS: did you
>> install any TS CALs on it? If not, it's not surprising that the
>> clients cannot connect, because they can't renew their licenses
>> if there aren't any.

_________________________________________________________
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?TWl6emxlbWFu?= <Mizzleman@discussions.microsoft.com>
wrote on 16 aug 2007 in
microsoft.public.windows.terminal_services:

> Vera,
>
> I did a test. As the user that was having problems, I used my
> laptop to start a RDP session to the TS and successfully logged
> on as the user.
>
> I also did a test or two on the user's PC. I deleted the
> MSlicensing key and rebooted. I was able to log on successfully
> once as the user, but can't repeat it since. I can see where the
> license was issued from the TS License server on the same subnet
> as the TS. Could this be strictly a client issue? Do I have some
> corruption coming from somewhere on the TS's or TS license
> server?
>
> "Vera Noest [MVP]" wrote:
>
>> OK, so now we have 2 problems :-)
>> Regarding the original LS in the remote subnet:
>> Can you ping it?
>> Have you verified that the TS Licensing Service is up and
>> running? Have you rebooted the server?
>> And:
>> > Do you also have Terminal Servers on the same subnet as the
>> > TS LS? If so, can they connect?
>>
>> Regarding the new TS LS on the same subnet as the TS: did you
>> install any TS CALs on it? If not, it's not surprising that the
>> clients cannot connect, because they can't renew their licenses
>> if there aren't any.
>> Totally new clients should be able to get a temporary license,
>> though. To test if this works OK, you could delete the locally
>> stored license from a client which can't connect:
>>
>> 187614 - Removing Terminal Server Licenses from an RDP Client
>> http://support.microsoft.com/?kbid=187614
>>
>> And no, I don't do private consulting, so no emails and no
>> phone calls, please.
>>
>> _________________________________________________________
>> 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?TWl6emxlbWFu?= <Mizzleman@discussions.microsoft.com>
>> wrote on 15 aug 2007 in
>> microsoft.public.windows.terminal_services:
>>
>> > The TS is showing event id 1004. The license server is not
>> > showing any errors. The TS and the license server are on the
>> > same subnet now. I was trying to contact a license server on
>> > a remote subnet and that worked until yesterday afternoon. We
>> > put a license server on the subnet to see if that would help.
>> > I ran lsview before I put the license server in the subnet
>> > and it could not find the license server. After putting the
>> > license server in the same subnet, lsview can now find the
>> > license server. But the clients still cannot connect and I
>> > get event 1004 in the event log of the TS. There are no
>> > firewalls in between. The LS is Win2k3 SP2.
>> >
>> > By the way, I was hoping you would respond. You've helped me
>> > in the past. Anyway I can call you direct?
>> >
>> > "Vera Noest [MVP]" wrote:
>> >
>> >> Are there any errors or warnings in the EventLog on either
>> >> the terminal servers or the TS Licensing Server?
>> >> Do you also have Terminal Servers on the same subnet as the
>> >> TS LS? If so, can they connect?
>> >> Which SP is the TS LS running?
>> >> Is there a firewall between the TS and the TS LS?
>> >>
>> >> _________________________________________________________
>> >> 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?TWl6emxlbWFu?=
>> >> <Mizzleman@discussions.microsoft.com> wrote on 15 aug 2007
>> >> in microsoft.public.windows.terminal_services:
>> >>
>> >> > Hello,
>> >> >
>> >> > I have 3 Win2k TS's that can cannot connect to a Win2k3
>> >> > license server in a remote subnet, same domain. It was
>> >> > working fine until yesterday. I have not changed anything
>> >> > on the servers. Some patches were installed on 7/13/2007.
>> >> > I have set the default license server registry key for the
>> >> > license server. I ran a protocol analyzer when I run the
>> >> > TS Licensing tool on the TS as it tries to find the
>> >> > license server. After looking throught the analysis, it
>> >> > shows the LDAP query and getting the license server info,
>> >> > but the TS still can't connect to it. What is going on?
>> >> > This is a major production outage so a quick response is
>> >> > appreciated. Thanks.
 
Re: Win2K TS's can't connect to Win2k3 license server in remote su

See my reply to your previous post.
_________________________________________________________
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?TWl6emxlbWFu?= <Mizzleman@discussions.microsoft.com>
wrote on 16 aug 2007 in
microsoft.public.windows.terminal_services:

> Vera,
>
> Here is a little more information. If I delete the mslicensing
> registry key off of the client, the client can connect. But if I
> try to connect again, it won't work. If I delete the key again,
> it will work again.
>
> "Mizzleman" wrote:
>
>> Vera,
>>
>> I did a test. As the user that was having problems, I used my
>> laptop to start a RDP session to the TS and successfully logged
>> on as the user.
>>
>> I also did a test or two on the user's PC. I deleted the
>> MSlicensing key and rebooted. I was able to log on successfully
>> once as the user, but can't repeat it since. I can see where
>> the license was issued from the TS License server on the same
>> subnet as the TS. Could this be strictly a client issue? Do I
>> have some corruption coming from somewhere on the TS's or TS
>> license server?
>>
>> "Vera Noest [MVP]" wrote:
>>
>> > OK, so now we have 2 problems :-)
>> > Regarding the original LS in the remote subnet:
>> > Can you ping it?
>> > Have you verified that the TS Licensing Service is up and
>> > running? Have you rebooted the server?
>> > And:
>> > > Do you also have Terminal Servers on the same subnet as the
>> > > TS LS? If so, can they connect?
>> >
>> > Regarding the new TS LS on the same subnet as the TS: did you
>> > install any TS CALs on it? If not, it's not surprising that
>> > the clients cannot connect, because they can't renew their
>> > licenses if there aren't any.
>> > Totally new clients should be able to get a temporary
>> > license, though. To test if this works OK, you could delete
>> > the locally stored license from a client which can't connect:
>> >
>> > 187614 - Removing Terminal Server Licenses from an RDP Client
>> > http://support.microsoft.com/?kbid=187614
>> >
>> > And no, I don't do private consulting, so no emails and no
>> > phone calls, please.
>> >
>> > _________________________________________________________
>> > 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?TWl6emxlbWFu?=
>> > <Mizzleman@discussions.microsoft.com> wrote on 15 aug 2007 in
>> > microsoft.public.windows.terminal_services:
>> >
>> > > The TS is showing event id 1004. The license server is not
>> > > showing any errors. The TS and the license server are on
>> > > the same subnet now. I was trying to contact a license
>> > > server on a remote subnet and that worked until yesterday
>> > > afternoon. We put a license server on the subnet to see if
>> > > that would help. I ran lsview before I put the license
>> > > server in the subnet and it could not find the license
>> > > server. After putting the license server in the same
>> > > subnet, lsview can now find the license server. But the
>> > > clients still cannot connect and I get event 1004 in the
>> > > event log of the TS. There are no firewalls in between. The
>> > > LS is Win2k3 SP2.
>> > >
>> > > By the way, I was hoping you would respond. You've helped
>> > > me in the past. Anyway I can call you direct?
>> > >
>> > > "Vera Noest [MVP]" wrote:
>> > >
>> > >> Are there any errors or warnings in the EventLog on either
>> > >> the terminal servers or the TS Licensing Server?
>> > >> Do you also have Terminal Servers on the same subnet as
>> > >> the TS LS? If so, can they connect?
>> > >> Which SP is the TS LS running?
>> > >> Is there a firewall between the TS and the TS LS?
>> > >>
>> > >> _________________________________________________________
>> > >> 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?TWl6emxlbWFu?=
>> > >> <Mizzleman@discussions.microsoft.com> wrote on 15 aug 2007
>> > >> in microsoft.public.windows.terminal_services:
>> > >>
>> > >> > Hello,
>> > >> >
>> > >> > I have 3 Win2k TS's that can cannot connect to a Win2k3
>> > >> > license server in a remote subnet, same domain. It was
>> > >> > working fine until yesterday. I have not changed
>> > >> > anything on the servers. Some patches were installed on
>> > >> > 7/13/2007. I have set the default license server
>> > >> > registry key for the license server. I ran a protocol
>> > >> > analyzer when I run the TS Licensing tool on the TS as
>> > >> > it tries to find the license server. After looking
>> > >> > throught the analysis, it shows the LDAP query and
>> > >> > getting the license server info, but the TS still can't
>> > >> > connect to it. What is going on? This is a major
>> > >> > production outage so a quick response is appreciated.
>> > >> > Thanks.
 
Re: Win2K TS's can't connect to Win2k3 license server in remote su

Vera,

Did not need to. We use the builtin unlimited Windows 2000 Terminal Server
CALs.

However, I did get the problem fixed. I worked with MS PSS to determine
there was black hole router somewhere on the network that wasn't passing 1472
bytes. I used the EnablePMTUBH (1) setting for
HKLM\System\Services\TCPIP\Parameters to detect it and have the client adjust
for it. The clients can connect with no problem now.

Thanks, Vera. You are always very helpful!



"Vera Noest [MVP]" wrote:

> Mizzleman, I can't help you if you don't answer my questions.
>
> >> Regarding the new TS LS on the same subnet as the TS: did you
> >> install any TS CALs on it? If not, it's not surprising that the
> >> clients cannot connect, because they can't renew their licenses
> >> if there aren't any.
>
> _________________________________________________________
> 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?TWl6emxlbWFu?= <Mizzleman@discussions.microsoft.com>
> wrote on 16 aug 2007 in
> microsoft.public.windows.terminal_services:
>
> > Vera,
> >
> > I did a test. As the user that was having problems, I used my
> > laptop to start a RDP session to the TS and successfully logged
> > on as the user.
> >
> > I also did a test or two on the user's PC. I deleted the
> > MSlicensing key and rebooted. I was able to log on successfully
> > once as the user, but can't repeat it since. I can see where the
> > license was issued from the TS License server on the same subnet
> > as the TS. Could this be strictly a client issue? Do I have some
> > corruption coming from somewhere on the TS's or TS license
> > server?
> >
> > "Vera Noest [MVP]" wrote:
> >
> >> OK, so now we have 2 problems :-)
> >> Regarding the original LS in the remote subnet:
> >> Can you ping it?
> >> Have you verified that the TS Licensing Service is up and
> >> running? Have you rebooted the server?
> >> And:
> >> > Do you also have Terminal Servers on the same subnet as the
> >> > TS LS? If so, can they connect?
> >>
> >> Regarding the new TS LS on the same subnet as the TS: did you
> >> install any TS CALs on it? If not, it's not surprising that the
> >> clients cannot connect, because they can't renew their licenses
> >> if there aren't any.
> >> Totally new clients should be able to get a temporary license,
> >> though. To test if this works OK, you could delete the locally
> >> stored license from a client which can't connect:
> >>
> >> 187614 - Removing Terminal Server Licenses from an RDP Client
> >> http://support.microsoft.com/?kbid=187614
> >>
> >> And no, I don't do private consulting, so no emails and no
> >> phone calls, please.
> >>
> >> _________________________________________________________
> >> 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?TWl6emxlbWFu?= <Mizzleman@discussions.microsoft.com>
> >> wrote on 15 aug 2007 in
> >> microsoft.public.windows.terminal_services:
> >>
> >> > The TS is showing event id 1004. The license server is not
> >> > showing any errors. The TS and the license server are on the
> >> > same subnet now. I was trying to contact a license server on
> >> > a remote subnet and that worked until yesterday afternoon. We
> >> > put a license server on the subnet to see if that would help.
> >> > I ran lsview before I put the license server in the subnet
> >> > and it could not find the license server. After putting the
> >> > license server in the same subnet, lsview can now find the
> >> > license server. But the clients still cannot connect and I
> >> > get event 1004 in the event log of the TS. There are no
> >> > firewalls in between. The LS is Win2k3 SP2.
> >> >
> >> > By the way, I was hoping you would respond. You've helped me
> >> > in the past. Anyway I can call you direct?
> >> >
> >> > "Vera Noest [MVP]" wrote:
> >> >
> >> >> Are there any errors or warnings in the EventLog on either
> >> >> the terminal servers or the TS Licensing Server?
> >> >> Do you also have Terminal Servers on the same subnet as the
> >> >> TS LS? If so, can they connect?
> >> >> Which SP is the TS LS running?
> >> >> Is there a firewall between the TS and the TS LS?
> >> >>
> >> >> _________________________________________________________
> >> >> 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?TWl6emxlbWFu?=
> >> >> <Mizzleman@discussions.microsoft.com> wrote on 15 aug 2007
> >> >> in microsoft.public.windows.terminal_services:
> >> >>
> >> >> > Hello,
> >> >> >
> >> >> > I have 3 Win2k TS's that can cannot connect to a Win2k3
> >> >> > license server in a remote subnet, same domain. It was
> >> >> > working fine until yesterday. I have not changed anything
> >> >> > on the servers. Some patches were installed on 7/13/2007.
> >> >> > I have set the default license server registry key for the
> >> >> > license server. I ran a protocol analyzer when I run the
> >> >> > TS Licensing tool on the TS as it tries to find the
> >> >> > license server. After looking throught the analysis, it
> >> >> > shows the LDAP query and getting the license server info,
> >> >> > but the TS still can't connect to it. What is going on?
> >> >> > This is a major production outage so a quick response is
> >> >> > appreciated. Thanks.
>
 
Re: Win2K TS's can't connect to Win2k3 license server in remote su

OK, I'm glad that your problem is solved, and thanks for reporting
back here!
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
*----------- Please reply in newsgroup -------------*

=?Utf-8?B?TWl6emxlbWFu?= <Mizzleman@discussions.microsoft.com>
wrote on 17 aug 2007:

> Vera,
>
> Did not need to. We use the builtin unlimited Windows 2000
> Terminal Server CALs.
>
> However, I did get the problem fixed. I worked with MS PSS to
> determine there was black hole router somewhere on the network
> that wasn't passing 1472 bytes. I used the EnablePMTUBH (1)
> setting for HKLM\System\Services\TCPIP\Parameters to detect it
> and have the client adjust for it. The clients can connect with
> no problem now.
>
> Thanks, Vera. You are always very helpful!
>
>
>
> "Vera Noest [MVP]" wrote:
>
>> Mizzleman, I can't help you if you don't answer my questions.
>>
>> >> Regarding the new TS LS on the same subnet as the TS: did
>> >> you install any TS CALs on it? If not, it's not surprising
>> >> that the clients cannot connect, because they can't renew
>> >> their licenses if there aren't any.
>>
>> _________________________________________________________
>> 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?TWl6emxlbWFu?= <Mizzleman@discussions.microsoft.com>
>> wrote on 16 aug 2007 in
>> microsoft.public.windows.terminal_services:
>>
>> > Vera,
>> >
>> > I did a test. As the user that was having problems, I used my
>> > laptop to start a RDP session to the TS and successfully
>> > logged on as the user.
>> >
>> > I also did a test or two on the user's PC. I deleted the
>> > MSlicensing key and rebooted. I was able to log on
>> > successfully once as the user, but can't repeat it since. I
>> > can see where the license was issued from the TS License
>> > server on the same subnet as the TS. Could this be strictly a
>> > client issue? Do I have some corruption coming from somewhere
>> > on the TS's or TS license server?
>> >
>> > "Vera Noest [MVP]" wrote:
>> >
>> >> OK, so now we have 2 problems :-)
>> >> Regarding the original LS in the remote subnet:
>> >> Can you ping it?
>> >> Have you verified that the TS Licensing Service is up and
>> >> running? Have you rebooted the server?
>> >> And:
>> >> > Do you also have Terminal Servers on the same subnet as
>> >> > the TS LS? If so, can they connect?
>> >>
>> >> Regarding the new TS LS on the same subnet as the TS: did
>> >> you install any TS CALs on it? If not, it's not surprising
>> >> that the clients cannot connect, because they can't renew
>> >> their licenses if there aren't any.
>> >> Totally new clients should be able to get a temporary
>> >> license, though. To test if this works OK, you could delete
>> >> the locally stored license from a client which can't
>> >> connect:
>> >>
>> >> 187614 - Removing Terminal Server Licenses from an RDP
>> >> Client http://support.microsoft.com/?kbid=187614
>> >>
>> >> And no, I don't do private consulting, so no emails and no
>> >> phone calls, please.
>> >>
>> >> _________________________________________________________
>> >> 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?TWl6emxlbWFu?=
>> >> <Mizzleman@discussions.microsoft.com> wrote on 15 aug 2007
>> >> in microsoft.public.windows.terminal_services:
>> >>
>> >> > The TS is showing event id 1004. The license server is not
>> >> > showing any errors. The TS and the license server are on
>> >> > the same subnet now. I was trying to contact a license
>> >> > server on a remote subnet and that worked until yesterday
>> >> > afternoon. We put a license server on the subnet to see if
>> >> > that would help. I ran lsview before I put the license
>> >> > server in the subnet and it could not find the license
>> >> > server. After putting the license server in the same
>> >> > subnet, lsview can now find the license server. But the
>> >> > clients still cannot connect and I get event 1004 in the
>> >> > event log of the TS. There are no firewalls in between.
>> >> > The LS is Win2k3 SP2.
>> >> >
>> >> > By the way, I was hoping you would respond. You've helped
>> >> > me in the past. Anyway I can call you direct?
>> >> >
>> >> > "Vera Noest [MVP]" wrote:
>> >> >
>> >> >> Are there any errors or warnings in the EventLog on
>> >> >> either the terminal servers or the TS Licensing Server?
>> >> >> Do you also have Terminal Servers on the same subnet as
>> >> >> the TS LS? If so, can they connect?
>> >> >> Which SP is the TS LS running?
>> >> >> Is there a firewall between the TS and the TS LS?
>> >> >>
>> >> >> _________________________________________________________
>> >> >> 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?TWl6emxlbWFu?=
>> >> >> <Mizzleman@discussions.microsoft.com> wrote on 15 aug
>> >> >> 2007 in microsoft.public.windows.terminal_services:
>> >> >>
>> >> >> > Hello,
>> >> >> >
>> >> >> > I have 3 Win2k TS's that can cannot connect to a Win2k3
>> >> >> > license server in a remote subnet, same domain. It was
>> >> >> > working fine until yesterday. I have not changed
>> >> >> > anything on the servers. Some patches were installed on
>> >> >> > 7/13/2007. I have set the default license server
>> >> >> > registry key for the license server. I ran a protocol
>> >> >> > analyzer when I run the TS Licensing tool on the TS as
>> >> >> > it tries to find the license server. After looking
>> >> >> > throught the analysis, it shows the LDAP query and
>> >> >> > getting the license server info, but the TS still can't
>> >> >> > connect to it. What is going on? This is a major
>> >> >> > production outage so a quick response is appreciated.
>> >> >> > Thanks.
 
Back
Top