- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.
02-17-2026 04:00 AM
02-18-2026 08:44 AM
Hey @Sameer Telikicherla If generating a new RDP file doesn't resolve it - you can disable "Client IP enforcement for MFA caching" in Settings (for testing purposes), and see if it still occurs.
In some environments, outbound IP for HTTP traffic (generating the RDP file + token) is different from the outbound IP for RDP (launching the RDP file to establish the session). The mismatch in IP causes a token error.
02-23-2026 03:36 AM
Hello @Patrick Booth
Thanks for the solution. It had worked when i disabled the setting "Client IP enforcement for MFA caching". I could establish a session successfully, any impact will it have on other users / teams using CyberArk, when this setting is disabled. If yes, we have to enable it again.
Thanks in advance
Sam
02-23-2026 08:09 AM
If testing with disabling was successful, you'll need to work with your networking team to ensure the HTTP and RDP traffic are originating from the same outbound IP address to use Client IP enforcement for MFA caching. Functionally, there should be no impact disabling the enforcement, but from a security perspective it's not recommended.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!

