The other day whenever we had a system wide crash. Instead of rebooting my host server, I simply started shutting down clients and bringing them back up. To my surprise, I began seeing Sessions #26, 27, 28, 29, etc in a 25 client lab. Session hijacking? Or did I simply not give it that minute to terminate the clients of those dropped sessions? Simply weird. Maybe I should have let it go to see if it came up to session #31 and beyond?

On NControl, it showed all of sessions disconnected prior to rebooting a few. On occassion, we've also experienced TS Exceeded Max Connections on one or two of the terminals when they just seem to erractically crash for no apparent reason. No output to see what's causing the random crashing. I think part of my hardware is going out on a brand new server. Or maybe the software is just buggy. Downloaded the new version .91 to see if that resolved along with firmware updates. Had it crash 3 times in 2 days.

Just thought it was weird. #26 session in a 25 client lab.

Did you check the session # after you had logged in the "extra" terminals.  If I get the boot here and log back in, I get session#6 (only 5 users)  but then the session actually logs into the old session, so it will then show 5 or less once logged in.

No I didn't. I made the mistake and didn't give it a minute to terminate the session after a disconnect because that's what we have it set to (1 minute). I just thought it was weird to see above my normal threshhold with a new number. Makes perfect sense though. What's double weird, is when I get a TS-Error on too many connections at the client end as if it's maxed out. We only have 25 clients.