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

AD Authentification problem

Since I don't know where to post this problem, I've decided to post it here, since I want to use it with the proxy functionality in the end.

I have a user which can be authenticated against the AD if just use it plain and simple and try to do the test authentification on USER -> Authentication -> Servers.
But if I use the the "logon to" functionality within the AD to limit the logon capability to specific pc's it won't authenticate anymore, even if I enter the ASTARO AD name or the IP into the "logon to" selection.
We are useing Server 2003 Standard.
Does anyone experience the same problem?
I've contacted the support and they told me they can't follow this error on server 2008.
So it has eighter to do with server 2003 or there could be something wrong on our AD backend, but how to find out, what exactly?

Thank you in advance for any help some of you could give.

This thread was automatically locked due to age.

0 crusader over 14 years ago

Just in case someone has the same problem as I had:

The astaro box doesn't function as a joined client within the AD, you have to enter one of the DC's you use to authicate against on the astaro box.
After you entered the name of the DC's the authentication is working eventhough you have limited the accessibility of the specific user.
Cancel
Vote Up 0 Vote Down

Cancel
0 BAlfson over 14 years ago

Here's a guide to setting up AD-SSO for web security: HTTP/S Proxy Access with AD-SSO (Caution, the section "Configure User Authentication" should be eliminated as it has no effect on AD-SSO and can cause problems in larger organizations).

Cheers - Bob

Sophos UTM Community Moderator
Sophos Certified Architect - UTM
Sophos Certified Engineer - XG
Gold Solution Partner since 2005

MediaSoft, Inc. USA
Cancel
Vote Up 0 Vote Down

Cancel