Re: First DC off over 24 hours
- From: "Paul Bergson [MVP-DS]" <pbergson@xxxxxxxxxxxxxxxxx>
- Date: Fri, 11 Apr 2008 08:55:28 -0500
See if this helps
http://support.microsoft.com/kb/325850
--
Paul Bergson
MVP - Directory Services
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.
"Irene" <Irene@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:4D3B5F4C-15E7-4545-8658-48BD7B840006@xxxxxxxxxxxxxxxx
Hi Paul,
Here is the log for dcdiag /e. DC2 is our first DC in the forest and
running
4 roles for AD, it was down over 24 hours, after we put it back on all the
other DCs can not replicate with DC2, I run repadmin /syncall on DC2,
there
were no error, but when I run on DC5, there was an error " error
contacting
server (GUID of DC2), the target principal name is incorrect'" , with
NtFrs
warning 13508 on both DC, please give some idea.
Thanks
Testing server: WGCCHQ\dc5
Starting test: Replications
[Replications Check,dc5] A recent replication attempt failed:
From dc2 to dc5
Naming Context: DC=ForestDnsZones,DC=XXX,DC=com
The replication generated an error (1256):
The remote system is not available. For information about
network troubleshooting, see Windows Help.
The failure occurred at 2008-04-10 12:54:29.
The last success occurred at 2008-04-08 11:53:05.
55 failures have occurred since the last success.
[Replications Check,dc5] A recent replication attempt failed:
From dc2 to dc5
Naming Context: DC=DomainDnsZones,DC=XXX,DC=com
The replication generated an error (1256):
The remote system is not available. For information about
network troubleshooting, see Windows Help.
The failure occurred at 2008-04-10 12:54:29.
The last success occurred at 2008-04-08 11:53:05.
53 failures have occurred since the last success.
[Replications Check,dc5] A recent replication attempt failed:
From dc2 to dc5
Naming Context: CN=Schema,CN=Configuration,DC=XXX,DC=com
The replication generated an error (-2146893022):
The target principal name is incorrect.
The failure occurred at 2008-04-10 12:54:29.
The last success occurred at 2008-04-08 11:53:04.
56 failures have occurred since the last success.
[Replications Check,dc5] A recent replication attempt failed:
From dc2 to dc5
Naming Context: CN=Configuration,DC=XXX,DC=com
The replication generated an error (-2146893022):
The target principal name is incorrect.
The failure occurred at 2008-04-10 13:27:53.
The last success occurred at 2008-04-08 12:00:14.
161 failures have occurred since the last success.
[Replications Check,dc5] A recent replication attempt failed:
From dc2 to dc5
Naming Context: DC=XXX,DC=com
The replication generated an error (-2146893022):
The target principal name is incorrect.
The failure occurred at 2008-04-10 13:31:36.
The last success occurred at 2008-04-08 12:05:48.
1259 failures have occurred since the last success.
[Replications Check,dc5] A recent replication attempt failed:
From dc2 to dc5
Naming Context: DC=WG1080,DC=XXX,DC=com
The replication generated an error (1256):
The remote system is not available. For information about
network troubleshooting, see Windows Help.
The failure occurred at 2008-04-10 12:54:29.
The last success occurred at 2008-04-08 11:53:05.
57 failures have occurred since the last success.
[Replications Check,dc5] A recent replication attempt failed:
From dc2 to dc5
Naming Context: DC=Pape,DC=XXX,DC=com
The replication generated an error (1256):
The remote system is not available. For information about
network troubleshooting, see Windows Help.
The failure occurred at 2008-04-10 12:54:29.
The last success occurred at 2008-04-08 11:53:05.
53 failures have occurred since the last success.
[Replications Check,dc5] A recent replication attempt failed:
From dc2 to dc5
Naming Context: DC=Danf,DC=XXX,DC=com
The replication generated an error (1256):
The remote system is not available. For information about
network troubleshooting, see Windows Help.
The failure occurred at 2008-04-10 12:54:29.
The last success occurred at 2008-04-08 11:53:05.
54 failures have occurred since the last success.
REPLICATION-RECEIVED LATENCY WARNING
dc5: Current time is 2008-04-10 13:31:27.
DC=DomainDnsZones,DC=XXX,DC=com
Last replication recieved from COSDC1 at 2008-04-08
10:59:19.
Last replication recieved from dc2 at 2008-04-08 11:59:20.
Last replication recieved from 1491DC1 at 2008-04-08
10:59:19.
DC=XXX,DC=com
Last replication recieved from COSDC1 at 2008-04-08
12:00:00.
Last replication recieved from dc2 at 2008-04-08 12:05:54.
Last replication recieved from 1491DC1 at 2008-04-08
12:00:00.
Last replication recieved from WGCCSWEB at 2008-04-08
12:00:00.
Last replication recieved from 1080DC2 at 2008-04-08
12:00:00.
......................... dc5 passed test Replications
Testing server: Pape\DC1
Starting test: Replications
[Replications Check,DC1] A recent replication attempt failed:
From dc2 to DC1
Naming Context: CN=Schema,CN=Configuration,DC=XXX,DC=com
The replication generated an error (1326):
Logon failure: unknown user name or bad password.
The failure occurred at 2008-04-10 12:51:01.
The last success occurred at 2008-04-08 11:47:33.
98 failures have occurred since the last success.
Kerberos Error.
The machine account is not present, or does not match on the.
destination, source or KDC servers.
Verify domain partition of KDC is in sync with rest of
enterprise.
The tool repadmin/syncall can be used for this purpose.
[Replications Check,DC1] A recent replication attempt failed:
From dc2 to DC1
Naming Context: CN=Configuration,DC=XXX,DC=com
The replication generated an error (1326):
Logon failure: unknown user name or bad password.
The failure occurred at 2008-04-10 12:51:00.
The last success occurred at 2008-04-08 11:47:31.
98 failures have occurred since the last success.
Kerberos Error.
The machine account is not present, or does not match on the.
destination, source or KDC servers.
Verify domain partition of KDC is in sync with rest of
enterprise.
The tool repadmin/syncall can be used for this purpose.
[Replications Check,DC1] A recent replication attempt failed:
From dc2 to DC1
Naming Context: DC=XXX,DC=com
The replication generated an error (1326):
Logon failure: unknown user name or bad password.
The failure occurred at 2008-04-10 12:51:03.
The last success occurred at 2008-04-08 11:47:34.
98 failures have occurred since the last success.
Kerberos Error.
The machine account is not present, or does not match on the.
destination, source or KDC servers.
Verify domain partition of KDC is in sync with rest of
enterprise.
The tool repadmin/syncall can be used for this purpose.
[Replications Check,DC1] A recent replication attempt failed:
From dc2 to DC1
Naming Context: DC=WG1080,DC=XXX,DC=com
The replication generated an error (1326):
Logon failure: unknown user name or bad password.
The failure occurred at 2008-04-10 12:51:04.
The last success occurred at 2008-04-08 11:47:35.
98 failures have occurred since the last success.
Kerberos Error.
The machine account is not present, or does not match on the.
destination, source or KDC servers.
Verify domain partition of KDC is in sync with rest of
enterprise.
The tool repadmin/syncall can be used for this purpose.
[Replications Check,DC1] A recent replication attempt failed:
From dc2 to DC1
Naming Context: DC=Danf,DC=XXX,DC=com
The replication generated an error (1326):
Logon failure: unknown user name or bad password.
The failure occurred at 2008-04-10 12:51:04.
The last success occurred at 2008-04-08 11:47:36.
98 failures have occurred since the last success.
Kerberos Error.
The machine account is not present, or does not match on the.
destination, source or KDC servers.
Verify domain partition of KDC is in sync with rest of
enterprise.
The tool repadmin/syncall can be used for this purpose.
......................... DC1 passed test Replications
Starting test: NCSecDesc
......................... DC1 passed test NCSecDesc
Starting test: NetLogons
[DC1] An net use or LsaPolicy operation failed with error 1203, No
network provider accepted the given network path..
......................... DC1 failed test NetLogons
"Paul Bergson [MVP-DS]" wrote:
No.
You will just have to post each individually if they have errors. Most
times people just post the errors, warnings, etc...
--
Paul Bergson
MVP - Directory Services
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.
"Irene" <Irene@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:F4DF0E2C-2A06-4EBF-B6BB-9EAC864EBF53@xxxxxxxxxxxxxxxx
Hi Paul, as the files are big, can I email to you?
thanks Irene
"Paul Bergson [MVP-DS]" wrote:
You haven't really provided much info. Are you getting any error
messages
in the event logs?
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
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.
"Irene" <Irene@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:D10E0F59-C88E-4439-8AFF-AFACA7B8490E@xxxxxxxxxxxxxxxx
Hi All, our first DC which hold Schema owner, Domain role owner, PDC
role,
and RID pool manager role, did not turn on over 24 hours, acitive
directory
can not replicate with this DC after we turn it on after 24 hours,
what
should I do to put this DC back on line and replicate with orther
DCs?
Thanks in advance
.
- References:
- First DC off over 24 hours
- From: Irene
- Re: First DC off over 24 hours
- From: Paul Bergson [MVP-DS]
- Re: First DC off over 24 hours
- From: Irene
- Re: First DC off over 24 hours
- From: Paul Bergson [MVP-DS]
- Re: First DC off over 24 hours
- From: Irene
- First DC off over 24 hours
- Prev by Date: Re: Error Accessing NativeObject
- Next by Date: Re: URGENT !
- Previous by thread: Re: First DC off over 24 hours
- Next by thread: Restore Active Directory appears on desktop after adding 2 DC´s
- Index(es):
Relevant Pages
|
