Re: Client disconnected problem

Tech-Archive recommends: Fix windows errors by optimizing your registry

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@xxxxxxxxxxxxxxxxxxxxxxxxx>
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@xxxxxxxxxxxxxxxxxxxxxxxxx>
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@xxxxxxxxxxxxxxxxxxxxxxxxx> 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?
.

Relevant Pages

  • [NT] Microsoft RDP Man in the Middle Vulnerability
    ... Windows Server 2003) and Windows XP's Remote Desktop, provide an easy, ... * Terminal Server software: Microsoft Windows Terminal Services using RDP ... * Terminal Server Client software: ... The server sends it's public key and a random salt, in clear text, ...
    (Securiteam)
  • Re: Licensing Protocol Error
    ... It looks as though one client is ... Here are the error message on the terminal server: ... A terminal services license server is required for continuous ... A terminal server can operate w/o a license for 90 days after initial ...
    (microsoft.public.win2000.termserv.clients)
  • RE: Re: Remote connections
    ... the TSWeb client is a simple and ActiveX based terminal server ... management remote control programs ...
    (Focus-Microsoft)
  • Re: Event Viewer Warning
    ... appears to apply only to a License Server in a Windows 2003-based ... MCSE, CCEA, Microsoft MVP - Terminal Server ... Event Viewer entry. ...
    (microsoft.public.windows.terminal_services)
  • Re: Running multiple instances of the same program simultaneously
    ... Can this be achieved using Terminal Server? ... Everything that can run the rdp client (or Internet Explorer if you ... Edition, Windows Me, Windows NT 4.0, Windows 2000, and Windows XP. ...
    (microsoft.public.windows.terminal_services)