Client disconnected problem

  • Thread starter Thread starter LostGoose
  • Start date Start date
L

LostGoose

Guest
I need help diagnosing problem at a customer's site. They are running Win
2003 Server. They have a couple of Pocket PC devices that run the TS client.
Terminal Services is set to auto logon clients and launch an application.
This has worked fine for a couple of years. Now one PPC gets the message
"Terminal services client disconnected. The connection to the server has
timed out". The other PPC still works fine.
I can ping the server and open the server in Windows Explorer on the PPC.
Hard reset the PPC. No change. No message in the event log of the server.
I can take my laptop (running W2K server) and run the TS client and connect
fine. I can take another PPC of mine and open TS client and I get the same
error msg.
The license server is running. Rebooted server - no change. Deactivated
and reactivated license server - no change.
What am I missing?
 
Re: Client disconnected problem

Do you have free TS CALs available on your TS Licensing Server?

_________________________________________________________
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?TG9zdEdvb3Nl?= <LostGoose@discussions.microsoft.com>
wrote on 12 sep 2007 in
microsoft.public.windows.terminal_services:

> I need help diagnosing problem at a customer's site. They are
> running Win 2003 Server. They have a couple of Pocket PC
> devices that run the TS client.
> Terminal Services is set to auto logon clients and launch an
> application.
> This has worked fine for a couple of years. Now one PPC gets
> the message "Terminal services client disconnected. The
> connection to the server has timed out". The other PPC still
> works fine. I can ping the server and open the server in Windows
> Explorer on the PPC. Hard reset the PPC. No change. No
> message in the event log of the server. I can take my laptop
> (running W2K server) and run the TS client and connect fine. I
> can take another PPC of mine and open TS client and I get the
> same error msg.
> The license server is running. Rebooted server - no change.
> Deactivated and reactivated license server - no change.
> What am I missing?
 
Re: Client disconnected problem

The license server shows 2 Win 2003 TS CALS total, 2 Issued. Which should be
right since they only have 2 Pocket PCs. Both of the issued CALs showed they
expired at the end of Oct. There were also 2 Win 2000 TS CALs on the server.
None issued.
I thought that when the CALs could not be verified, you got a message like
"the server ended the connection" plus you got a line in the event viewer of
the server about not able to give a CAL. No message like that on the server.
I could also see the temporary CAL that was given to my laptop when I tested
it's connection.
Thanks for the input. Anything else I could be missing. I'm pulling my
hair out.

"Vera Noest [MVP]" wrote:

> Do you have free TS CALs available on your TS Licensing Server?
>
> _________________________________________________________
> 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?TG9zdEdvb3Nl?= <LostGoose@discussions.microsoft.com>
> wrote on 12 sep 2007 in
> microsoft.public.windows.terminal_services:
>
> > I need help diagnosing problem at a customer's site. They are
> > running Win 2003 Server. They have a couple of Pocket PC
> > devices that run the TS client.
> > Terminal Services is set to auto logon clients and launch an
> > application.
> > This has worked fine for a couple of years. Now one PPC gets
> > the message "Terminal services client disconnected. The
> > connection to the server has timed out". The other PPC still
> > works fine. I can ping the server and open the server in Windows
> > Explorer on the PPC. Hard reset the PPC. No change. No
> > message in the event log of the server. I can take my laptop
> > (running W2K server) and run the TS client and connect fine. I
> > can take another PPC of mine and open TS client and I get the
> > same error msg.
> > The license server is running. Rebooted server - no change.
> > Deactivated and reactivated license server - no change.
> > What am I missing?
>
 
Re: Client disconnected problem

Yes, I just wanted to rule out licensing as the source of the
problem.
Were any changes made to the server or the client (including
ServicePacks or Windows Update) immediately prior to the start of
this problem? Is the server running SP2?
_________________________________________________________
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?TG9zdEdvb3Nl?= <LostGoose@discussions.microsoft.com>
wrote on 12 sep 2007 in
microsoft.public.windows.terminal_services:

> The license server shows 2 Win 2003 TS CALS total, 2 Issued.
> Which should be right since they only have 2 Pocket PCs. Both
> of the issued CALs showed they expired at the end of Oct. There
> were also 2 Win 2000 TS CALs on the server.
> None issued.
> I thought that when the CALs could not be verified, you got a
> message like "the server ended the connection" plus you got a
> line in the event viewer of the server about not able to give a
> CAL. No message like that on the server. I could also see the
> temporary CAL that was given to my laptop when I tested it's
> connection. Thanks for the input. Anything else I could be
> missing. I'm pulling my hair out.
>
> "Vera Noest [MVP]" wrote:
>
>> Do you have free TS CALs available on your TS Licensing Server?
>>
>> _________________________________________________________
>> 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?TG9zdEdvb3Nl?= <LostGoose@discussions.microsoft.com>
>> wrote on 12 sep 2007 in
>> microsoft.public.windows.terminal_services:
>>
>> > I need help diagnosing problem at a customer's site. They
>> > are running Win 2003 Server. They have a couple of Pocket PC
>> > devices that run the TS client.
>> > Terminal Services is set to auto logon clients and launch an
>> > application.
>> > This has worked fine for a couple of years. Now one PPC gets
>> > the message "Terminal services client disconnected. The
>> > connection to the server has timed out". The other PPC still
>> > works fine. I can ping the server and open the server in
>> > Windows Explorer on the PPC. Hard reset the PPC. No change.
>> > No message in the event log of the server. I can take my
>> > laptop (running W2K server) and run the TS client and connect
>> > fine. I can take another PPC of mine and open TS client and
>> > I get the same error msg.
>> > The license server is running. Rebooted server - no change.
>> > Deactivated and reactivated license server - no change.
>> > What am I missing?
 
Re: Client disconnected problem

They claim there were no changes to the server. While checking the server I
noticed that Active Directory was not running and appeared to have never been
installed. I thought this might cause a problem finding the License Server
but since there is only one server and the License Server is on the same box
as Terminal Services it appears to be OK. I base that on the fact that the
License Server seemed to give my laptop a temporary license when I connected
to it.
The server is still running service pack 1.

"Vera Noest [MVP]" wrote:

> Yes, I just wanted to rule out licensing as the source of the
> problem.
> Were any changes made to the server or the client (including
> ServicePacks or Windows Update) immediately prior to the start of
> this problem? Is the server running SP2?
> _________________________________________________________
> 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?TG9zdEdvb3Nl?= <LostGoose@discussions.microsoft.com>
> wrote on 12 sep 2007 in
> microsoft.public.windows.terminal_services:
>
> > The license server shows 2 Win 2003 TS CALS total, 2 Issued.
> > Which should be right since they only have 2 Pocket PCs. Both
> > of the issued CALs showed they expired at the end of Oct. There
> > were also 2 Win 2000 TS CALs on the server.
> > None issued.
> > I thought that when the CALs could not be verified, you got a
> > message like "the server ended the connection" plus you got a
> > line in the event viewer of the server about not able to give a
> > CAL. No message like that on the server. I could also see the
> > temporary CAL that was given to my laptop when I tested it's
> > connection. Thanks for the input. Anything else I could be
> > missing. I'm pulling my hair out.
> >
> > "Vera Noest [MVP]" wrote:
> >
> >> Do you have free TS CALs available on your TS Licensing Server?
> >>
> >> _________________________________________________________
> >> 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?TG9zdEdvb3Nl?= <LostGoose@discussions.microsoft.com>
> >> wrote on 12 sep 2007 in
> >> microsoft.public.windows.terminal_services:
> >>
> >> > I need help diagnosing problem at a customer's site. They
> >> > are running Win 2003 Server. They have a couple of Pocket PC
> >> > devices that run the TS client.
> >> > Terminal Services is set to auto logon clients and launch an
> >> > application.
> >> > This has worked fine for a couple of years. Now one PPC gets
> >> > the message "Terminal services client disconnected. The
> >> > connection to the server has timed out". The other PPC still
> >> > works fine. I can ping the server and open the server in
> >> > Windows Explorer on the PPC. Hard reset the PPC. No change.
> >> > No message in the event log of the server. I can take my
> >> > laptop (running W2K server) and run the TS client and connect
> >> > fine. I can take another PPC of mine and open TS client and
> >> > I get the same error msg.
> >> > The license server is running. Rebooted server - no change.
> >> > Deactivated and reactivated license server - no change.
> >> > What am I missing?
>
 
Re: Client disconnected problem

Have you considered installing SP2? It has been out for a while now
:-).
I can't promise that it solves the issue, but it will make it
easier for you to get support. At least I have already forgotten
most of the pre-SP2 problems and their solutions. And if you call
Microsoft Support, it will be their first requirement.
I'm inclined to believe that the problem has nothing to do with
licensing, since your clients seem to hold a valid license. On the
other hand, the behaviour of the TS (refusing some clients, but not
others) does point to a licensing problem.
Did you have a hard look at those two PPCs which can't connect? Has
anything changed 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?TG9zdEdvb3Nl?= <LostGoose@discussions.microsoft.com>
wrote on 13 sep 2007 in
microsoft.public.windows.terminal_services:

> They claim there were no changes to the server. While checking
> the server I noticed that Active Directory was not running and
> appeared to have never been installed. I thought this might
> cause a problem finding the License Server but since there is
> only one server and the License Server is on the same box as
> Terminal Services it appears to be OK. I base that on the fact
> that the License Server seemed to give my laptop a temporary
> license when I connected to it.
> The server is still running service pack 1.
>
> "Vera Noest [MVP]" wrote:
>
>> Yes, I just wanted to rule out licensing as the source of the
>> problem.
>> Were any changes made to the server or the client (including
>> ServicePacks or Windows Update) immediately prior to the start
>> of this problem? Is the server running SP2?
>> _________________________________________________________
>> 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?TG9zdEdvb3Nl?= <LostGoose@discussions.microsoft.com>
>> wrote on 12 sep 2007 in
>> microsoft.public.windows.terminal_services:
>>
>> > The license server shows 2 Win 2003 TS CALS total, 2 Issued.
>> > Which should be right since they only have 2 Pocket PCs.
>> > Both of the issued CALs showed they expired at the end of
>> > Oct. There were also 2 Win 2000 TS CALs on the server.
>> > None issued.
>> > I thought that when the CALs could not be verified, you got a
>> > message like "the server ended the connection" plus you got a
>> > line in the event viewer of the server about not able to give
>> > a CAL. No message like that on the server. I could also see
>> > the temporary CAL that was given to my laptop when I tested
>> > it's connection. Thanks for the input. Anything else I
>> > could be missing. I'm pulling my hair out.
>> >
>> > "Vera Noest [MVP]" wrote:
>> >
>> >> Do you have free TS CALs available on your TS Licensing
>> >> Server?
>> >>
>> >> _________________________________________________________
>> >> 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?TG9zdEdvb3Nl?=
>> >> <LostGoose@discussions.microsoft.com> wrote on 12 sep 2007
>> >> in microsoft.public.windows.terminal_services:
>> >>
>> >> > I need help diagnosing problem at a customer's site. They
>> >> > are running Win 2003 Server. They have a couple of Pocket
>> >> > PC devices that run the TS client.
>> >> > Terminal Services is set to auto logon clients and launch
>> >> > an application.
>> >> > This has worked fine for a couple of years. Now one PPC
>> >> > gets the message "Terminal services client disconnected.
>> >> > The connection to the server has timed out". The other
>> >> > PPC still works fine. I can ping the server and open the
>> >> > server in Windows Explorer on the PPC. Hard reset the
>> >> > PPC. No change.
>> >> > No message in the event log of the server. I can take my
>> >> > laptop (running W2K server) and run the TS client and
>> >> > connect fine. I can take another PPC of mine and open TS
>> >> > client and I get the same error msg.
>> >> > The license server is running. Rebooted server - no
>> >> > change. Deactivated and reactivated license server - no
>> >> > change. What am I missing?
 
Re: Client disconnected problem

I'll get them to upgrade to SP2. I'm sure they don't even know how to change
anything on the PPC. And to be honest, I wouldn't know how to change
anything related to the Terminal Service Client on the PPC. There appears to
be no configuration for it.
I'm curious how the licensing handles the PPCs. I think the server expects
the client to give it info about the CAL it has. But with PPCs they can lose
everything easily if the battery goes completely dead. It cold starts back
with factory defaults. How does the license server identify this PPC as one
that had a CAL before.

"Vera Noest [MVP]" wrote:

> Have you considered installing SP2? It has been out for a while now
> :-).
> I can't promise that it solves the issue, but it will make it
> easier for you to get support. At least I have already forgotten
> most of the pre-SP2 problems and their solutions. And if you call
> Microsoft Support, it will be their first requirement.
> I'm inclined to believe that the problem has nothing to do with
> licensing, since your clients seem to hold a valid license. On the
> other hand, the behaviour of the TS (refusing some clients, but not
> others) does point to a licensing problem.
> Did you have a hard look at those two PPCs which can't connect? Has
> anything changed 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?TG9zdEdvb3Nl?= <LostGoose@discussions.microsoft.com>
> wrote on 13 sep 2007 in
> microsoft.public.windows.terminal_services:
>
> > They claim there were no changes to the server. While checking
> > the server I noticed that Active Directory was not running and
> > appeared to have never been installed. I thought this might
> > cause a problem finding the License Server but since there is
> > only one server and the License Server is on the same box as
> > Terminal Services it appears to be OK. I base that on the fact
> > that the License Server seemed to give my laptop a temporary
> > license when I connected to it.
> > The server is still running service pack 1.
> >
> > "Vera Noest [MVP]" wrote:
> >
> >> Yes, I just wanted to rule out licensing as the source of the
> >> problem.
> >> Were any changes made to the server or the client (including
> >> ServicePacks or Windows Update) immediately prior to the start
> >> of this problem? Is the server running SP2?
> >> _________________________________________________________
> >> 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?TG9zdEdvb3Nl?= <LostGoose@discussions.microsoft.com>
> >> wrote on 12 sep 2007 in
> >> microsoft.public.windows.terminal_services:
> >>
> >> > The license server shows 2 Win 2003 TS CALS total, 2 Issued.
> >> > Which should be right since they only have 2 Pocket PCs.
> >> > Both of the issued CALs showed they expired at the end of
> >> > Oct. There were also 2 Win 2000 TS CALs on the server.
> >> > None issued.
> >> > I thought that when the CALs could not be verified, you got a
> >> > message like "the server ended the connection" plus you got a
> >> > line in the event viewer of the server about not able to give
> >> > a CAL. No message like that on the server. I could also see
> >> > the temporary CAL that was given to my laptop when I tested
> >> > it's connection. Thanks for the input. Anything else I
> >> > could be missing. I'm pulling my hair out.
> >> >
> >> > "Vera Noest [MVP]" wrote:
> >> >
> >> >> Do you have free TS CALs available on your TS Licensing
> >> >> Server?
> >> >>
> >> >> _________________________________________________________
> >> >> 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?TG9zdEdvb3Nl?=
> >> >> <LostGoose@discussions.microsoft.com> wrote on 12 sep 2007
> >> >> in microsoft.public.windows.terminal_services:
> >> >>
> >> >> > I need help diagnosing problem at a customer's site. They
> >> >> > are running Win 2003 Server. They have a couple of Pocket
> >> >> > PC devices that run the TS client.
> >> >> > Terminal Services is set to auto logon clients and launch
> >> >> > an application.
> >> >> > This has worked fine for a couple of years. Now one PPC
> >> >> > gets the message "Terminal services client disconnected.
> >> >> > The connection to the server has timed out". The other
> >> >> > PPC still works fine. I can ping the server and open the
> >> >> > server in Windows Explorer on the PPC. Hard reset the
> >> >> > PPC. No change.
> >> >> > No message in the event log of the server. I can take my
> >> >> > laptop (running W2K server) and run the TS client and
> >> >> > connect fine. I can take another PPC of mine and open TS
> >> >> > client and I get the same error msg.
> >> >> > The license server is running. Rebooted server - no
> >> >> > change. Deactivated and reactivated license server - no
> >> >> > change. What am I missing?
>
 
Re: Client disconnected problem

I don't know. Resetting a thin client to the factory default is
equivalent to deleting the locally stored license from a standard
client. That would lead to the issueing of a new license (the
client would be regarded as a completely new client).
And that could in theory cause your problem (since you have only 2
TS CALs), except for the fact that you would see an expired
temporary license for these devices. So that doesn't fit the bill
either.

_________________________________________________________
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?TG9zdEdvb3Nl?= <LostGoose@discussions.microsoft.com>
wrote on 13 sep 2007 in
microsoft.public.windows.terminal_services:

> I'll get them to upgrade to SP2. I'm sure they don't even know
> how to change anything on the PPC. And to be honest, I wouldn't
> know how to change anything related to the Terminal Service
> Client on the PPC. There appears to be no configuration for it.
> I'm curious how the licensing handles the PPCs. I think the
> server expects the client to give it info about the CAL it has.
> But with PPCs they can lose everything easily if the battery
> goes completely dead. It cold starts back with factory
> defaults. How does the license server identify this PPC as one
> that had a CAL before.
>
> "Vera Noest [MVP]" wrote:
>
>> Have you considered installing SP2? It has been out for a while
>> now
>> :-).
>> I can't promise that it solves the issue, but it will make it
>> easier for you to get support. At least I have already
>> forgotten most of the pre-SP2 problems and their solutions. And
>> if you call Microsoft Support, it will be their first
>> requirement. I'm inclined to believe that the problem has
>> nothing to do with licensing, since your clients seem to hold a
>> valid license. On the other hand, the behaviour of the TS
>> (refusing some clients, but not others) does point to a
>> licensing problem. Did you have a hard look at those two PPCs
>> which can't connect? Has anything changed 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?TG9zdEdvb3Nl?= <LostGoose@discussions.microsoft.com>
>> wrote on 13 sep 2007 in
>> microsoft.public.windows.terminal_services:
>>
>> > They claim there were no changes to the server. While
>> > checking the server I noticed that Active Directory was not
>> > running and appeared to have never been installed. I thought
>> > this might cause a problem finding the License Server but
>> > since there is only one server and the License Server is on
>> > the same box as Terminal Services it appears to be OK. I
>> > base that on the fact that the License Server seemed to give
>> > my laptop a temporary license when I connected to it.
>> > The server is still running service pack 1.
>> >
>> > "Vera Noest [MVP]" wrote:
>> >
>> >> Yes, I just wanted to rule out licensing as the source of
>> >> the problem.
>> >> Were any changes made to the server or the client (including
>> >> ServicePacks or Windows Update) immediately prior to the
>> >> start of this problem? Is the server running SP2?
>> >> _________________________________________________________
>> >> 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?TG9zdEdvb3Nl?=
>> >> <LostGoose@discussions.microsoft.com> wrote on 12 sep 2007
>> >> in microsoft.public.windows.terminal_services:
>> >>
>> >> > The license server shows 2 Win 2003 TS CALS total, 2
>> >> > Issued. Which should be right since they only have 2
>> >> > Pocket PCs. Both of the issued CALs showed they expired at
>> >> > the end of Oct. There were also 2 Win 2000 TS CALs on the
>> >> > server.
>> >> > None issued.
>> >> > I thought that when the CALs could not be verified, you
>> >> > got a message like "the server ended the connection" plus
>> >> > you got a line in the event viewer of the server about not
>> >> > able to give a CAL. No message like that on the server. I
>> >> > could also see the temporary CAL that was given to my
>> >> > laptop when I tested it's connection. Thanks for the
>> >> > input. Anything else I could be missing. I'm pulling my
>> >> > hair out.
>> >> >
>> >> > "Vera Noest [MVP]" wrote:
>> >> >
>> >> >> Do you have free TS CALs available on your TS Licensing
>> >> >> Server?
>> >> >>
>> >> >> _________________________________________________________
>> >> >> 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?TG9zdEdvb3Nl?=
>> >> >> <LostGoose@discussions.microsoft.com> wrote on 12 sep
>> >> >> 2007 in microsoft.public.windows.terminal_services:
>> >> >>
>> >> >> > I need help diagnosing problem at a customer's site.
>> >> >> > They are running Win 2003 Server. They have a couple
>> >> >> > of Pocket PC devices that run the TS client.
>> >> >> > Terminal Services is set to auto logon clients and
>> >> >> > launch an application.
>> >> >> > This has worked fine for a couple of years. Now one
>> >> >> > PPC gets the message "Terminal services client
>> >> >> > disconnected. The connection to the server has timed
>> >> >> > out". The other PPC still works fine. I can ping the
>> >> >> > server and open the server in Windows Explorer on the
>> >> >> > PPC. Hard reset the PPC. No change.
>> >> >> > No message in the event log of the server. I can take
>> >> >> > my
>> >> >> > laptop (running W2K server) and run the TS client and
>> >> >> > connect fine. I can take another PPC of mine and open
>> >> >> > TS client and I get the same error msg.
>> >> >> > The license server is running. Rebooted server - no
>> >> >> > change. Deactivated and reactivated license server - no
>> >> >> > change. What am I missing?
 
Back
Top