Forum Discussion
RDP via a LTM not maintaining persistence
We are using an LTM as a hardware load balancer for Windows Server 2008R2 for Remote Desktop Services. There are two Servers, one is the session broker and both are the Session hosts within the same Farm. I have configured a Single RDP Virtual server and Pool, both servers are in that pool. I have used the Persistence MSRDP profile.
Sessions are not been maintained to the same server, so when a user closes the RDP session (without logging out) the session is not always returned to the same server.
[Q1] Does anyone have any idea why this is not working?
[Q2] One thought I have is the persistence profile has the default timeout of 300 seconds, should I increase this or does the fact that the RDP token (routing token) contains the IP of the destination server mean that the timeout becomes irrelevant?
Any advice or guidance will be gratefully received
- natheCirrocumulusNZ_David
- Nick_T_68319Nimbostratusis your session broker working? That should always return the user to the same session whether your LTM persistence is working or not.
- NZ_David_20489NimbostratusHi Nick and Nathan, Thanks for your responses.
- NZ_David_20489NimbostratusI've increased the persistence timeout without any change to the current situation - the session does nto always persist to the same server
- sachin_80710Nimbostratus
Hi NZ_David, This issue got solved? We are also having same issue.
- NZ_David_20489Nimbostratus
No there is still an issue but we have bypassed it. General users of the server work ok via the LTM VIP. These users are not concerned which server services their connectivity. However if it is necessary that users maintain perisstence (following closing the session) the user accesses the server directly.
Recent Discussions
Related Content
* 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