Help! new ICA session hijacking another ICA session?

[thesleepylizard]

Sorry, has been an issue for ages, users are constantly screaming at me, and I have no training or official experience with Citrix, and my Citrix support guy is too busy to look at it right away. =sob=

But here's the problem. One ICA client logs onto the server, and hey presto - they get someone else's screen instead! And I think the other person's session gets shut down. This way sucks and is causing massive disruption. I've affectionately labeled it "accidental session-hijacking".

Now here's what I tried.

1) Went to ICA-tcp properties under Session and ticked "override user settings" for "Allow reconnection" and made it "From previous client".

This was a week ago, and they still have the problem. So last night I:


2) Overrode user settings for "End a disconnected session": Set to 1 minute


3) Overrode user settings for "When session limit is reached or connection is broken": set to End Session


But I really don't know if this will help or not. Can you guys help?


Here's what we'd like: we'd like it _guaranteed_ that whenever someone connected through ICA, that they would a _brand_new_session_. Always. Regardless of disconnection or other users or even machine name (though we've tried to keep them unique).

It doesn't matter if they do get disconnected and lose stuff sinec it wipes the session clean, we just want to ensure they get new sessions.

Thanks in advance for your time.
-lizard

 

[thesleepylizard]

Oh by the way - we have the ICA deployed in different offices throughout the internet and stuff.

Plus, we're near our client license limit (not sure if we may be getting bumped over it and that's causing the problems or something...)

 

[TonyFal]

This is the part that really worries me:

"Regardless of disconnection or other users or even machine name (though we've tried to keep them unique)"

You MUST keep the client names unique. While I'm just guessing I'd bet those effected by this hijacking have identical ICA client names.

This is the first thing to verify before changing server settings.

Tony

http://www.ccaheaven.com

Tony

http://www.ccaheaven.com