danthomas

I seem to have solved this now. There was an issue with our kerberos5 config file, I basically removed a couple of lines from it to make it look like the config in this post (obviously with 'mydomain.local' replaced with our actual domain). I then restarted the server and then re-joined it to the domain. And to be clear, I DIDN'T use the format DOMAIN\<username> to login, I literally just put in my username and it worked. If I did put the domain prefix in, it doesn't work.....

Ok thanks, I'll wait for @MartinK to reply and hopefully get this resolved. This is the last few lines from my last attempted login...

Tried that a million times and still no luck. Shall I share the trace.log in a PM to you?

I am having this issue that not even the ESET support team cannot resolve for me and I am at a bit of a loss! We used to be able to login using our domain admin AD credentials that are members of the mapped domain security group 'esetv6 admin'. Now when I look in the 'Domain Users' list I don't see any members, almost as if the ESET server is not pulling in the list of users from this group. The directory synchronization works fine, all computers/servers connect fine, I can browse our directory structure from within the remote administration console and I can even see my username when running a domain user sync. So why is it not populating this mapped group? Suffice to say, if I try to login I just get the 'Login Failed' message. I am running the latest version of the ESMC (version 7.7.1908).