Score:0

Can connect but not bind using ldp when creating new Domain Controller

in flag

I'm using ldp.exe..... I can connect fine via ldap to my new domain controller by doing this (the Server Name here is a dns alias pointing to the IP of the server)

enter image description here

enter image description here

.....but when I attempt to bind using the credentials that I am actually currently logged into the new domain controller with ......like this.....

enter image description here

....it actually gives me the following error (btw, my username and password are correct and not locked or expired or anything)

enter image description here

Has anybody seen this behavior before? Can someone explain it? The same thing happens when I try to bind on 636 and click the SSL button by the way

BTW I raised the same thing yesterday and closed it because I thought I'd got it working but I was mistaken

...However...when I do a simple bind AND the format of the username as @ it binds just fine

enter image description here

I sit in a Tesla and translated this thread with Ai:

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.