AD not available on one Domain Controller

  • Thread starter Thread starter John
  • Start date Start date
J

John

We have two Windows 2000 SP3 DC's and when they first start up everything is
fine. Then after some days, if I try to start the Active Directory Users and
Computers tool on one of the DC's, I receive the following error message:

Naming Information cannot be located because:
The Server is not operational.
Contact your system administrator to verify that your domain is properly
configured and is currently online.

Starting this Tool on the other DC works fine. Restarting the problem server
overcomes the problem but I would like to resolve the issue causing it.

Any suggestions anyone?

Thanks,

John
 
Thank you for your reply.

The only one which may be relevant in our case is the third regarding Port
389. We do not use TCP/IP filtering but have found another server
application which reports that it cannot start because a port (not 389) is
not available. Restarting the server allows this application to start as
well.

I have used the Portqry tool to check port 389 when the problem exists, but
it just shows its status as listening.

If you have any other suggestions I would appreciate hearing them.

John
 
What is this server application ? Domain controllers need port 389 for LDAP
and this is a must. If there is another application on your server that
requires port 389, then you will have to change that port or move
application to another server.

--
Regards

Matjaz Ladava, MCSE (NT4 & 2000), Windows MVP
(e-mail address removed)
http://ladava.com
 
Check the application event log on this DC and see if it is logging any
Event ID 1704's from SecCli.
Also, check your RUN key in the registry and make sure the applications in
there are legit.
 
Back
Top