RE: Domain Controller - Derver not operational

• Previous message: Simon Geary: "Re: modify the SRV weightings"
• In reply to: OrphicFireball: "RE: Domain Controller - Derver not operational"
• Next in thread: OrphicFireball: "RE: Domain Controller - Derver not operational"
• Reply: OrphicFireball: "RE: Domain Controller - Derver not operational"
• Messages sorted by: [ date ] [ thread ]

Date: Mon, 13 Sep 2004 01:00:44 -0700

Thanks for your response, same error with opening any
active directory component. I have ran the DCDIAG command
as suggested and the response was as below;
----------------------------------------
C:\Program Files\Support Tools>dcdiag /s:SANDPIT-
SERVER /test:knowsofroleholders

Domain Controller Diagnosis

Performing initial setup:
   [SANDPIT-SERVER] LDAP connection failed with error 58,
   Win32 Error 58.
   ***Error: The machine, SANDPIT-SERVER could not be
contacted, because of a bad net response. Check to make
sure
   that this machine is a Domain Controller.
--------------------------------------------------------

I have network activity, as I can connect to the internet
and other machines.

Not sure where to go to from here !

Regards

Steve

>-----Original Message-----
>I just fixed error, it was twofold for us, so I wonder
which problem is
>causing it for you. I don't claim to be an expert in
troubleshooting Active
>Directory, but I have some things to try. First, look in
Active Directory
>Sites and Services and look to see if your server is
referencing any
>computers that no longer exist (which ours were). The
second thing that was
>wrong with our server is that the time was set
incorrectly, which made
>absolutely nothing work. I noticed that the server's
time was 20 minutes
>behind so I corrected it not knowing the trouble that
would cause. Kerberos
>requires all clocks in the forest to be within 5 minutes
of each other for
>just about everything. Lastly, run If you haven't
already try restarting it
>too.
>
>If all that seems well it is likely that your server
cannot locate the one
>the servers holding one of the FSMO roles. Try running
DCDIAG from the
>command prompt and see if it says anything that stands
out. If that doesn't
>work you can run this specific string to be really
specific about it.
>Replace NAME with the name of your DC: "DCDAIG /s:NAME
>/test:knowsofroleholders". DCDAIG is on the windows
server 2003 CD if it
>isn't already installed.
>
>"Steve" wrote:
>
>> Hello All,
>>
>> We have a Win 2003 Domain controller in our lab that
was
>> working just fine until recently, not sure whats
broken.
>> We can log into this machine locally, but when you try
to
>> access and Active Directory functions, we get an error
>> saying 'Naming Information cannot be located for the
>> following reason - The server in not operational'. Even
>> though we can still use the server and even log in
>> locally, all of the Active Directory functions don't
work.
>> I also found some info regarding end point errors
relating
>> to LDAP on port 389, well our machine is not listening
on
>> port 389, could this be related.
>>
>> Any help would be appreciated.
>>
>> Regards
>>
>> Steve
>>
>.
>

• Previous message: Simon Geary: "Re: modify the SRV weightings"
• In reply to: OrphicFireball: "RE: Domain Controller - Derver not operational"
• Next in thread: OrphicFireball: "RE: Domain Controller - Derver not operational"
• Reply: OrphicFireball: "RE: Domain Controller - Derver not operational"
• Messages sorted by: [ date ] [ thread ]