Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 754
  • Last Modified:

[Critical] Please Help, LDAP Bind was unsuccessful

Dear Experts,

We original have 2 domain controller both running windows 2000,sp4 , one is the pdc,
now we build a new server with windows 2003 r2, sp1 and promote it as our new pdc, I transfer all fsmo roles to the new server already
make it as global calalog list already, now we shutdown our old pdc (win2000), on our exchange server we using exchange server 2003 with sp2
I changed the domain controller in the recipient update service to the new one and rebuild the list already, if check in exchange system manager on the exchange server domain controller list, all DC,GC and config (auto) pointing to the new PDC,

I got this error like every 2-3 hour then it return to normal the I got this error again while this error occured the email unable to send out,

"LDAP Bind was unsuccessful on directory DOMAIN1.com for distinguished name ''. Directory returned error:[0x51] Server Down. "

I checked our server it's running ok,

another one is

Process MAD.EXE (PID=1608). All Domain Controller Servers in use are not responding:
DOMAIN1.com
DOMAIN2.com  << this one running windows server 2000, it's a dc, with gc

I also get this error in the event log

Process IISIPM09EB298D-66A4-41D6-8489-FFBA6E6F2B58 -AP "EXCHANGEAPPLICATIONPOOL (PID=5836). Topology Discovery failed, error 0x80040a02.

another one I got is

The Win32 API call 'DsGetDCNameW' returned error code [0x54b] The specified domain either does not exist or could not be contacted.  The service could not be initialized.  Make sure that the operating system was installed properly.

please advice,

thank you

0
npanprome
Asked:
npanprome
  • 2
  • 2
1 Solution
 
SembeeCommented:
It is struggling to find the domain controller.
Make sure that the DNS is set correctly on the network card. It should be pointing at valid domain controllers ONLY for DNS. I would also suggest restarting the Exchange server as well, which forces it to look for a valid DC.
If you are using WINS, ensure that is set correctly as well.

When you shutdown the other domain controller, did you DCPROMO out first? If not you should. A domain controller shouldn't be shutdown for any length of time, as you will get replication errors and the domain will presume that it is still there.

Simon.
0
 
npanpromeAuthor Commented:
the dns on the exchange server is pointing to the new pdc also as wins
but we didn't demote our old dc yet, and one more thing that i read up said I have to run setup /domainprep on exchange server again is that right?
please advice
0
 
SembeeCommented:
Where did you read that?
If wasn't on a Microsoft site then the information cannot be trusted.

Domainprep and Forestprep on have to be run once.
Domain prep is a domain setting, not a server setting. Once it has been run it doesn't have to be run again. It can be run as a troubleshooting process, but doesn't normally need to be run in these circumstances.

Simon.
0
 
npanpromeAuthor Commented:
This problem is solve it's the problem on the symantec appliance firewall, the dns still pointing to the old server, after we changed it to the new one everything look good so far but well i'm still on monitoring it, thanks for your help
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Get expert help—faster!

Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now