000019036 - ACE/Server stops authenticating completely when the Default Gateway defined under Control Panel->TCP/IP/Properties is either non-existent or becomes unavailable on the network.

Document created by RSA Customer Support Employee on Jun 14, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 4Show Document
  • View in full screen mode

Article Content

Article Number000019036
Applies ToRSA ACE/Server 5.0 (no longer supported as of 8-15-2004)
Microsoft Windows 2000
Microsoft Windows NT 4.0
UNIX (AIX, HP-UX, Solaris)
IssueACE/Server stops authenticating completely when the Default Gateway defined under Control Panel->TCP/IP/Properties is either non-existent or becomes unavailable on the network.
CauseACE/Server 5.0 listens for authentication requests on the network in a different way to prior versions of ACE/Server. This method takes advantage of an application-specific cache which is maintained by the Operating System in this scenario. Since it is a cache, the information is wrong when the Default Gateway becomes unavailable and authentication stops.
ResolutionAs a workaround, restart the ACE/Server from the Control Panel applet. The cache is rebuilt on startup and ACE/Server should start authenticating again.

RSA Security has built a fix for a separate problem which addresses this issue. This fix will be included in the next maintenance release of ACE/Server but is also available from the Technical Support Department. Please quote defect number tst00020613 when you contact RSA Security.

The fix remedies a problem with installing ACE/Server 5.0 on multi-homed machines. How to install RSA Authentication Manager 6.1 on a multi-homed server
Legacy Article IDa5286

Attachments

    Outcomes