Displaying 5 results from an estimated 5 matches for "thxi".
Did you mean:
thx
2014 Nov 26
2
Working with Active Directory on Windows Server 2012 R2
I?ve attempted the user Mail with the same password with the same result (binding as my own user was a last-ditch attempt).
aaron at aaron-Parallels-Virtual-Platform:/etc/sssd$ ldapsearch -x -H ldap://dc1.ad.automaton.uk -D CN=aaron.jenkins,CN=users,DC=ad,DC=automaton,DC=uk -W - -b CN=aaron.jenkins,CN=users,DC=ad,DC=automaton,DC=uk
Enter LDAP Password:
# extended LDIF
#
# LDAPv3
# base
2014 Nov 25
2
Working with Active Directory on Windows Server 2012 R2
Hi all,
I?m having issues getting Dovecot to work with AD on 2012 R2 in a test environment.
Background:
AD is running on dc1.ad.automaton.uk<http://dc1.ad.automaton.uk>, the domain is ad.automaton.uk<http://ad.automaton.uk>. The DNS server is running on ad.automaton.uk<http://ad.automaton.uk> and the automaton.uk<http://automaton.uk> DNS is set up correctly in the test
2014 Nov 25
0
Working with Active Directory on Windows Server 2012 R2
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Tue, 25 Nov 2014, Aaron Jenkins wrote:
> I?m having issues getting Dovecot to work with AD on 2012 R2 in a test environment.
> ?
> Nov 19 09:22:23 auth: Debug: auth client connected (pid=10345)
> Nov 19 09:22:23 auth: Debug: client in: AUTH 1 PLAIN service=imap secured session=pkJxdDkISwAK0zcd lip=10.211.55.33 rip=10.211.55.29lport=993
2014 Nov 26
0
Working with Active Directory on Windows Server 2012 R2
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Wed, 26 Nov 2014, Aaron Jenkins wrote:
> I?ve attempted the user Mail with the same password with the same result (binding as my own user was a last-ditch attempt).
OK, what about the:
> As I understand auth_bind_userdn, you do not need
> dn/dnpass anyway, because auth_bind_userdn prevents searching for the
>
2014 Nov 27
1
Working with Active Directory on Windows Server 2012 R2
I?ve removed the dn / dnpass.
When attempting with new user:
$ cat /var/log/dovecot-info.log
Nov 27 00:09:29 imap-login: Info: Internal login failure (pid=5553 id=1) (internal failure, 1 successful auths): user=<test.user>, method=PLAIN, rip=10.211.55.29, lip=10.211.55.33, mpid=5558, TLS, session=<rQXRqdIIZwAK0zcd>
Nov 27 00:09:29 imap-login: Info: Internal login failure (pid=5559