This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Authentication failure

Hello all,

We recently changed our DNS server along with its IP.  I've input in the Astaro under "Authentiction Servers" the new settings and confirmed the setting work by testing it with the test Server, and the example user test.  The problem we have now, is any one under our proxy is getting an authentication error.  Are we missing some other Spot for DNA entries and authentication?  I have The DNS set as "any" in the network Services aswell..

Even weirder, we remove any instance of the older DNS IP addres in the Authentication server settings,  As soon as we turn on the DNS server, we no loger have Authentication errors!

We must be missing some crucial setting that is causeing this.   any info would be appreciated.

Thanks

This thread was automatically locked due to age.

0 BAlfson over 13 years ago

Even weirder, we remove any instance of the older DNS IP addres in the Authentication server settings, As soon as we turn on the DNS server, we no loger have Authentication errors!

Is this a question about athentication by "Active Directory - SSO" in Web Filtering? If so, then changing the AD server on the 'Servers' tab has no effect. AD-SSO depends on domain membership on the 'Single Sign-On' tab.

Cheers - Bob
Cancel
Vote Up 0 Vote Down

Cancel
0 ngoodine over 13 years ago in reply to BAlfson

Is this a question about athentication by "Active Directory - SSO" in Web Filtering? If so, then changing the AD server on the 'Servers' tab has no effect. AD-SSO depends on domain membership on the 'Single Sign-On' tab.

Cheers - Bob

Yes it is Active Director-SSO, i've resolved my issue by joining the domain again after it finally acepted the credentials.

Thanks for your help.
Cancel
Vote Up 0 Vote Down

Cancel