patmoli
asked on
Fix credentials after domain admin password change on Exchange server 2003 ("LDAP Bind was unsuccessful on directory..")
I recently changed our admin password for our domain and keep getting a MSADC error in my application logs on my Exchange 2003 server. Event ID 8026, see below.
LDAP Bind was unsuccessful on directory servername for distinguished name 'domainname\Administrator'
I went into my Active Director Connector Services and changed the credentials in my Connection Agreements, but the event keeps popping up. I didn't "replicate now" and am not sure what the replication schedule is. Am I missing something, or do I just need a little patience?
LDAP Bind was unsuccessful on directory servername for distinguished name 'domainname\Administrator'
I went into my Active Director Connector Services and changed the credentials in my Connection Agreements, but the event keeps popping up. I didn't "replicate now" and am not sure what the replication schedule is. Am I missing something, or do I just need a little patience?
aramirezomni
It sure sounds like a replication issue. Do you have a big domain? or any reason why you can't just replicate now? I always throw in a GPupdate with my replications. Don't know why, habit I guess.
ASKER
I did a replication, to no avail on the ADC...
have you tried loggin on and off on both machines using the right credentials?
ADC? Do you have Exchange 5.5 servers or anything else legacy? NT4 for example? If not then you don't need any ADCs.
Simon.
--
Once your question has been answered, please remember to accept an answer and close the question.
Simon.
--
Once your question has been answered, please remember to accept an answer and close the question.
hey, routing around through the internet I found that most people showing this error have DNS improperly configured on their servers. You need to make sure that the DNS server on the NIC is the internal IP. 192 or 172 or 10. Then in the DNS services you setup the forwarded. See the article below:
http://support.microsoft.com/kb/300202
http://support.microsoft.com/kb/300202
ASKER
We migrated from 5.5 a while ago, havent removed it. Logging off/on the dc's and Exchange didn't resolve it, DNS is internal addy's, outside stuff comes in through firewall.
your next step is to load up the old exchange box and remove it from the server list. It no longer needs to be there. Maybe it's screwing with your AD
ASKER
That server no lomger exists.... thus my fear of just removing it
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I have yet to have the time to try this, I will award points & close as soon as I get a chance.... I promise I won't take too long.