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@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

  • RE: Event 1004 Terminal Server Cannot issue a client license
    ... by default Windows 2000 client/XP does not require license to connect ... MCSE, CCEA, Microsoft MVP - Terminal Server ... Per User TS CALs, so don't buy those. ... is issued to the client, which is good for 30 days. ...
    (microsoft.public.win2000.termserv.apps)
  • Re: What doesnt lend itself to OO?
    ... >> proxy and instructs the server to constuct the real object. ... rather than client code. ... If 'clock' is instantiated in the server, ... > for the server interface at the OOA level. ...
    (comp.object)
  • This is going straight to the pool room
    ... or not the client has privilege to do what they're trying to do, ... The server environment is this: ... 3GL User action Routines that Tier3 will execute on your behalf during the ... Routine Name: USER_INIT ...
    (comp.os.vms)
  • [Full-Disclosure] R: Full-Disclosure Digest, Vol 3, Issue 42
    ... Full-Disclosure Digest, Vol 3, Issue 42 ... SD Server 4.0.70 Directory Traversal Bug ... Arkeia Network Backup Client Remote Access ...
    (Full-Disclosure)
  • Re: What doesnt lend itself to OO?
    ... > rather than client code. ... no way to do that without also touching the object with clock semantics ... will not encapsulate both clock semantics and network semantics. ... The server can do whatever it wants ...
    (comp.object)