exchange 2003 problems after new DC.

[karmic]

I recently added a 2003 DC to an existing 2000 DC network, the 2000 DC is still carrying the GC, the 2003 is a secondary server. Now there's problems with the exchange server, it's a 2003 server on the domain, it does nothing else.

Ran adprep and forestprep on the 2000 DC and it went fine, no errors or warnings. Ran DCPROMO on the 2003, again no problems. Everything replicated just fine, DNS is running on both servers happily and so on. I've checked and the GC is on the 2000 server, RUS is hitting the 2000 DC etc.

I've run dcdiag on the 2000 DC and all tests came back as pass. Can ping anywhere on the network from the exchange, nslookup returns the 2000dc.mycompany.local. It seems DNS is just fine.

I cannot run the system attendant or open the AD users and computers. Get an error "naming information cannot be located for the following reason: the server is not operational.

Errors so far are:

Process MAD.EXE (PID=3144). Topology Discovery failed, error 0xffffffff.
This comes first then:

LDAP Bind was unsuccessful on directory dcserver.mycompany.LOCAL for distinguished name ''. Directory returned error:[0x51] Server Down.
That's happening 4 to 6 times a second.

Would running dcpromo on the 2000 server fix things? It's coming off later this week for an upgrade to 2003 anyway.

Thanks.


~ K.I.S.S - Don't make it any more complex than it has to be ~