Filter
Top Products
Chapter 8: Troubleshooting
5536 PRI RAS Communications Controller Users Guide 129
Remote station
failed to connect
to the RAS Server
when SecurID
support is active
All the SecurID authentication attempts are registered
in the Windows NT Event Log. Use the Windows NT
Event Viewer to see the diagnostic. The possible
events are:
•
[bInitSIDDll] Cannot find aceclnt.dll: The
ACE/Agent is not installed. You must install it to
run the security feature.
•
[bInitSIDDll] Incomplete Dyna-link with
aceclnt.dll
: The ACE/Agent is not properly
installed.
•
Unable to dialog with ACE/Server: The Security
Dynamics ACE/Server is not accessible. You
should check whether the server is active and your
ACE/Agent is properly configured.
•
[vServiceMain] Unable to open the driver: The
IPHSIDDV SecurID driver did not start. Check the
driver status.
•
User xxx successfully authenticated: The user was
successfully authenticated by the SecurID
ACE/Server.
•
User xxx failed in authentication (ACCESS DENIED):
Either the SecurID username or the passcode is
incorrect. Check your value or maybe your token is
not synchronized with the ACE/Server.
•
User xxx failed in authentication (NEXT TOKEN
REQUIRED)
: Too many erroneous connections have
been processed and the ACE/Server wants to verify
that the remote client really owns the token. It
requires a new passcode value. This feature cannot
be supplied on digital connections. If you encounter
such a situation, only human intervention on the
ACE/Server can solve the problem.
Problem Possible Solution(s)