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
Convert a file-based RSA SecurID software token from .sdtid (CTF) format to a QR code failed with error "Java is not recog… Number of Views Invalid tokencode failures and expired QR code alerts in RSA SecurID Authenticate app Number of Views Dynamic Seed provisioning using QR Code Number of Views Authentication Manager token assigned to <no access> or <unknown> after user in an external identity source is deleted fro… Number of Views Assign a Software Token to a User Number of Views
Trending Articles
RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide User Application Portal Unable to Resolve User by Login ID and/or Alias or Authenticator Not Assigned to User When Attempting to Authenticate via … Download RSA SecurID Access Cloud User Event audit logs using Cloud Administration REST API CLU Manage Users for Cloud Access Service
Don't see what you're looking for?
