Thread Info
  • State Suggested Answer
  • Locked Locked
  • Replies 13 replies
  • Answers 1 answer
  • Subscribers 6 subscribers
  • Views 5009 views
  • Users 0 members are here
Options
Suggested
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

Active Directory Authentication is not working

Georg Zoeller

Hi Community,

i have a problem with one of our customers setups, they're running a windows server 2012 Domain controller and i'm trying to connect the sophos utm 9.716 to it, however it always says failed to bind with this dn and password, server exists and accepts connections. 

Then i take a look at the event viewer on the domain controller and it says account logged off, logon type 3, i already tried every thinkable combination and the account is also being recognised by the active directory. So now i'm thinking where could be the problem, is it a server problem or a sophos problem since every other client and account seems to be working in the environment.

I'm also thinking perhaps a reboot of ether the sophos of the server might fix it ?

Greetings, 

George



This thread was automatically locked due to age.
Parents
  • 0

    I don't know how it is with Windows Server 2012 but we had to switch from port 389 to 636 in 2020 because Microsoft started enforcing LDAPS (we use Windows Server 2019). These are our settings on the UTM now:

    If you use recipient verification in the SMTP proxy you also have to change a config file in the UTM via SSH: www.frankysweb.de/.../

Reply
  • 0

    I don't know how it is with Windows Server 2012 but we had to switch from port 389 to 636 in 2020 because Microsoft started enforcing LDAPS (we use Windows Server 2019). These are our settings on the UTM now:

    If you use recipient verification in the SMTP proxy you also have to change a config file in the UTM via SSH: www.frankysweb.de/.../

Children
Unfiltered HTML