[THIN] Re: Logon Disabled
- From: "Henry Sieff" <hsieff@xxxxxxxxxxxx>
- To: <thin@xxxxxxxxxxxxx>, <thin@xxxxxxxxxxxxx>
- Date: Tue, 12 Apr 2005 17:59:38 -0500
People have mentioned the possibility that you are caching the connection info
in PM, which is possible. Check and make sure the clients in question are
completely out of the app.
It is also possible that your server isn't sending updates to the ZDC for
whatever reason, but in that case it rebooting the client wouldn't consistently
fix the problem.
For the record, disabling logons DOES stop the server from participating in LB
if it is able to tell the ZDC about it - if the server is unresponsive in
general, that is a different story.
Also, you don't say how your clients are getting to the application (PN, PNA,
WI) or if you're using CSG. All of these could conceivably have an effect.
Henry Sieff
PS just finished BriForum - let me be the first to report here that it was well
worth the price of admission and to thank all of the presenters and of course
the organizers.
________________________________
From: thin-bounce@xxxxxxxxxxxxx on behalf of Joe Shonk
Sent: Tue 4/12/2005 11:50 AM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Logon Disabled
Hmm... Interesting issue... If we disable logons to a server (from the console
or cmd line) it seems that some of the thin-clients try and connect to it and
error out even tho there are other servers that serving up this published
desktop. Even 10 minutes later the same problems persist until: The
thin-client is rebooted or logins are re-enabled. Rebooting the thin-client
is not an option.
Any ideas?
Joe
Other related posts:
