|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
Re: Terminal Server
David Heine (david.heine
TELECOMPUTING.NET)
Tue, 23 Nov 1999 10:53:34 -0500
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
- Next message: Russ: "SP6a now available from Microsoft - here's why you shouldn't down load it...yet!"
- Previous message: Jeremy Collake: "Re: hard-coded windows exploits"
- In reply to: Peter Gutmann: "Re: hard-coded windows exploits"
I have seen a bug/glitch with Terminal Server using MetaFrame 1.8 during
application reviews that might be related. The user does not appear to have
an active or disconnected session under Terminal/MetaFrame Server
Administrator, yet has a process running (sometimes several) of an
application if you look in Task Manager. This behavior is usually a result
of an application gone awry and Terminal/MetaFrame Server is unable to
terminate the application. Even if you try to manually terminate the hung
process using Task Manager, the application that the user was running is in
such a strange state that it cannot be terminated without a reboot. Not all
applications behave very well running under Terminal Server, some do. This
is the main reason why there is a push to have programs certified to run
correctly under Terminal/MetaFrame Server.
Not knowing how your Terminal/MetaFrame Server is configured or what
software you are running, my guess is that at the time you had renamed the
account, Chartest3 was in a hung process (probably pointing to the same
application Ande was in when he got knocked off). If this is the case, it
might explain why the user Ande got knocked off when you had manually
terminated the process of Chartest3 within Task Manager.
Also, I can see how this might be a problem if Terminal/MetaFrame server is
configured to re-establish a users disconnected session the next time he
logs in. Configured in this way, it leaves the program open and can waste
memory if the user is not able to re-establish his old session upon
subsequent logins. This is a known issue yet some administrators are not
aware of this. Citrix has released several patches for this.
My initial recommendation is that you may want to re-evaluate the
configuration of your MetaFrame Server and the applications that you are
running on it. It is also a good idea to periodically watch for hung
sessions (wait until everyone is logged off and open Task Manager and sort
by username).
Again without knowing more details, my guesses are what they are.
Speculation.
David Heine
TeleComputing
www.telecomputing.net
- Next message: Russ: "SP6a now available from Microsoft - here's why you shouldn't down load it...yet!"
- Previous message: Jeremy Collake: "Re: hard-coded windows exploits"
- In reply to: Peter Gutmann: "Re: hard-coded windows exploits"
This archive was generated by hypermail 2.0b3 on Tue Nov 23 1999 - 13:08:11 CST