Hi,
We have set up an SSL VPN connection for our staff to use that authenticates them against Active Directory and this is working fine. We then needed to set up and Site to Site link for an externally hosted server to be able to connect to an internal server. The we set this up as a Site to Site SSL VPN as we already had the certificates and config in place from the staff SSL VPN. The external server is able to partially connect, the certs are passing validation, but the firewall generated username and password (AAAREF_User . . . .) is failing authentication. When I check the user auth log it seems the firewall is trying to authenticate it's own self generated account against Active Directory which obviously fails.
I've tried creating the account in Active Directory but that didn't work, I also tried prefetching the account from AD on the firewall, but it skips the account saying it's a locally authenticated account, if it knows it's a local account why is it checking against Active Directory?
Can someone tell me which tick box I've missed ticking to stop the Site to Site VPN trying to authenticate against AD.
BTW we are running an SG430 patch version 9.408-4.
Regards,
Nick
This thread was automatically locked due to age.