Forum Discussion
JRahm
Mar 01, 2005Admin
Terminal Server Persistence
I have msrdp persistence working without a rule, but only within a single vip. Globally, I don't have persistence to the client, so a client could potentially be assigned to the wrong vip, and even t...
JRahm
Mar 01, 2005Admin
For clarity,
Vip 1->Pool 1->Server 1
Vip 2->Pool 2->Server 2
MSRDP persistence with session directory is configured to persist across services, pools, and vips.
1. Login to Vip 1, which creates Terminal Server Session on Server 1.
2. Close the window, but remain logged in
3. Login to Vip 2, credentials supplied to Server 2, but server 2 checks session directory and sends routing token to client, which then redirects back to Vip 2. BigIP sends back to Server 2, instead of to Server 1 as expected.
If I uncheck session directory in the persistence and send the username credentials with my session request, the persistence works fine across vips. Since this doesn't work with the routing token, I was hoping I could do something with a rule.
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