No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.


The Slave AD Server cannot Take Over the Services on the Saster AD Server When the Master AD Server Becomes Faulty

Publication Date:  2012-07-20 Views:  420 Downloads:  0

Issue Description

A customer could not log in to the SVN3000 virtual gateway, though the AD domain user name and password were correct. The SVN3000 warned that the user name and password were incorrect. The customer attempted to log in with the VPNDB user and password of the SVN3000. The login still failed.
AD authentication and AD authorization were configured with the first-level priority on the SVN3000, and VPNDB authentication and VPNDB authorization were configured with the second-level priority.

Alarm Information


Handling Process

1.      The R&D will develop a new version which removes the problem.
2.    Workaround:
Configure only the information about the master AD server. In this way, the SVN3000 uses the VPNDB authentication and authorization when the master AD server fails.