PASSCODE slow to appear in post dial terminal window after end user enters username (and domain name depending on the configuration of RSA ACE/Agent 5.5 for Windows)
Originally Published: 2004-07-02
Last Modified: 2023-10-06
Article Number
Applies To
PDC
BDC
Routing and Remote Access Service (RRAS)
NetServerEnum
Microsoft SDK
Issue
Cause
Resolution
The hot fix changes the logic in RSA ACE/Agent 5.5 for Windows, and in most circumstances, will cause the PASSCODE to appear sooner.
If the domain controller is still slow to respond, there may be an issue with the network (e.g. network congestion) or the domain controller is under a high workload. For performance or scalability of domain controllers, please contact Microsoft Support.
Related Articles
RSA Identity Governance and Lifecycle 6.9.1 and higher request stays in an Open state when trying to delete roles 183Number of Views Convert a file-based RSA SecurID software token from .sdtid (CTF) format to a QR code failed with error "Java is not recog… 190Number of Views How to close Open Violations for inactive Segregation of Duties (SoD) and User Access Rules in RSA Identity Governance & L… 92Number of Views Invalid tokencode failures and expired QR code alerts in RSA SecurID Authenticate app 262Number of Views Add a SAML Application 169Number of Views
Trending Articles
RSA Authentication Manager 8.9 Patches and Hotfixes Readme RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide RSA-2026-24: RSA Authentication Manager Security Update for Third-Party Component Vulnerabilities IDR SSO - Step 3: Deploy the Identity Router RSA Authentication Manager 8.9 Setup and Configuration Guide
Don't see what you're looking for?