Score:0

Can't bind to ldaps 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?

Massimo avatar
ng flag
Are you using LDAP o LDAPS? If the second (as the name seems to imply), you should use TCP port 636 and SSL; also, the server must have a valid certificate. Otherwise you are using plain LDAP, and the name is just confusing.
Mick8695 avatar
in flag
@Massimo..thanks for getting back to me but I've solved it...it was a Group Policy thing....I'd put the server in the wrong OU...hopes this helps anybody else though
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.