Re: adc error 5719

Tech-Archive recommends: Fix windows errors by optimizing your registry



Run diagnostics against your Active Directory domain.

If you don't have the support tools installed, install them from your server
install disk.
d:\support\tools\setup.exe

Run dcdiag, netdiag and repadmin in verbose mode.
-> DCDIAG /V /C /D /E /s:yourdcname > c:\dcdiag.log
-> netdiag.exe /v > c:\netdiag.log (On each dc)
-> repadmin.exe /showrepl dc* /verbose /all /intersite > c:\repl.txt
-> dnslint /ad /s "ip address of your dc"

**Note: Using the /E switch in dcdiag will run diagnostics against ALL dc's
in the forest. If you have significant numbers of DC's this test could
generate significant detail and take a long time. You also want to take
into account slow links to dc's will also add to the testing time.

If you download a gui script I wrote it should be simple to set and run
(DCDiag and NetDiag). It also has the option to run individual tests
without having to learn all the switch options. The details will be output
in notepad text files that pop up automagically.

The script is located on my website at
http://www.pbbergs.com/windows/downloads.htm

Just select both dcdiag and netdiag make sure verbose is set. (Leave the
default settings for dcdiag as set when selected)

When complete search for fail, error and warning messages.

Description and download for dnslint
http://support.microsoft.com/kb/321045


--
Paul Bergson
MVP - Directory Services
MCTS, MCT, MCSE, MCSA, Security+, BS CSci
2008, 2003, 2000 (Early Achiever), NT4

http://www.pbbergs.com

Please no e-mails, any questions should be posted in the NewsGroup
This posting is provided "AS IS" with no warranties, and confers no rights.

"EmreCAN" <EmreCAN@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:38DA4944-877A-42B9-BF7B-6D0FAB0F3EC0@xxxxxxxxxxxxxxxx
I have setup additional dc but did not transfer fsmo roles to it.
and when i closed the pdc i got error from adc like this


This computer was not able to set up a secure session with a domain
controller in domain NETSERV due to the following:
There are currently no logon servers available to service the logon
request.
This may lead to authentication problems. Make sure that this computer is
connected to the network. If the problem persists, please contact your
domain
administrator.

ADDITIONAL INFO
If this computer is a domain controller for the specified domain, it sets
up
the secure session to the primary domain controller emulator in the
specified
domain. Otherwise, this computer sets up the secure session to any domain
controller in the specified domain.

does it mean that pdc is logging from pdc and clients are logging from pdc
or not?



.



Relevant Pages

  • Re: migration from win 2000 to Win2k8 server Ent - URGENT
    ... If you don't have the support tools installed, ... Run dcdiag, netdiag and repadmin in verbose mode. ... Name Resolution/Network Connectivity to the current domain controller. ...
    (microsoft.public.windows.server.active_directory)
  • Re: NTDS KCC 1308
    ... If you don't have the support tools installed, ... Run dcdiag, netdiag and repadmin in verbose mode. ... attempts to replicate with the following domain controller has ...
    (microsoft.public.windows.server.active_directory)
  • Re: Issues with New Additional Domain Controller
    ... If you don't have the support tools installed, ... Run dcdiag, netdiag and repadmin in verbose mode. ... Connections in our Head Office Domain Controller. ...
    (microsoft.public.windows.server.active_directory)
  • Re: migration from win 2000 to Win2k8 server Ent - URGENT
    ... Win2k8 Ent Server does not run dcdisg and netdiag giving following error ... Domain Controller Diagnosis ... Connecting to directory service on server mediaphoneplus.com. ... DcDiag: a dcdiag exception raised, ...
    (microsoft.public.windows.server.active_directory)
  • Re: W2K Cannot Seize RID and Schema roles
    ... If you don't have the support tools installed, install them from your server ... Run dcdiag, netdiag and repadmin in verbose mode. ...
    (microsoft.public.windows.server.active_directory)