Forum Discussion
John_Masgalas_4
Nimbostratus
Mar 22, 2007Load balancing terminal servers w/o Session Directory
We are having trouble with load balancing 2 terminal servers without Session Directory enabled. User will disconnect. When they log on again the big ip will not always send them to the same server so ...
Mark_Harris_608
Cirrus
Mar 22, 2007Changing the timeout option may help a little bit, but the basic issue is still not solved. With Session Directory disabled, msrdp persistence will persist to the same server during the same session. Once you disconnect (but *don't log out*), the next time you log in, you are a new user. There is no token to connect you with a session that is running on a particular terminal server. Your experience proves validates this behavior. If you enable Session Persistence it will work. So if you want it to reconnect to an already establish connection, you have to enable Session Persistence, or find a way to replicate the functionality of session directory. It's not that the session times out too early, it's that you have no way of knowing the existence of an existing session. Increasing the timeout will actually aggrevate the problem more. In fact, if the timeout is too long, ALL available servers could theoretically be "tied up" and no user could connect to either terminal servers. If anything, lower the timeout.
Recent Discussions
Related Content
DevCentral Quicklinks
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com
Discover DevCentral Connects