Re: One DC crashed and the other didn't take over - Please assist
- From: DY <DY@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 11 Oct 2007 16:29:01 -0700
Both DC's are GC's with AD Integrated DNS. All clients are set to point to
both of these servers. As I stated above, we didn't notice a problem until
DC1 went down. At that point, no one was able to log onto the domain.
Authentication was not available until DC1 came back online.
I again ran this test and received the same results (I do not see anything
in the eventlog at the time of this test on either of the DC's):
C:\>dcdiag /e /q
An Error Event occured. EventID: 0x00000457
Time Generated: 10/11/2007 18:12:03
(Event String could not be retrieved)
An Error Event occured. EventID: 0x00000457
Time Generated: 10/11/2007 18:12:03
(Event String could not be retrieved)
An Error Event occured. EventID: 0x00000457
Time Generated: 10/11/2007 18:12:05
(Event String could not be retrieved)
......................... SERVER-DC2 failed test systemlog
..
..
..
..
Next I tried this command:
J:\>dcdiag /e /q /c
** Did not run Outbound Secure Channels test
because /testdomain: was not entered
An Error Event occured. EventID: 0x00000457
Time Generated: 10/11/2007 18:12:03
(Event String could not be retrieved)
An Error Event occured. EventID: 0x00000457
Time Generated: 10/11/2007 18:12:03
(Event String could not be retrieved)
An Error Event occured. EventID: 0x00000457
Time Generated: 10/11/2007 18:12:05
(Event String could not be retrieved)
......................... SERVER-DC2 failed test systemlog
[SERVER-DC2] No security related replication errors were found on
this DC! To target the connection to a specific
source DC use /ReplSource:<DC>.
** Did not run Outbound Secure Channels test
because /testdomain: was not entered
[SSERVER-DC1] No security related replication errors were found on
this DC! To target the connection to a specific
source DC use /ReplSource:<DC>.
DNS Tests are running and not hung. Please wait a few minutes...
Test results for domain controllers:
DC: SERVER-DC1.OURDOMAIN.com
Domain: OURDOMAIN.com
TEST: Forwarders/Root hints (Forw)
Error: Root hints list has invalid root hint server:
a.root-servers.net. (198.41.0.4)
Error: Root hints list has invalid root hint server:
c.root-servers.net. (192.33.4.12)
Error: Root hints list has invalid root hint server:
d.root-servers.net. (128.8.10.90)
Error: Root hints list has invalid root hint server:
e.root-servers.net. (192.203.230.10)
Error: Root hints list has invalid root hint server:
f.root-servers.net. (192.5.5.241)
Error: Root hints list has invalid root hint server:
g.root-servers.net. (192.112.36.4)
Error: Root hints list has invalid root hint server:
h.root-servers.net. (128.63.2.53)
Error: Root hints list has invalid root hint server:
i.root-servers.net. (192.36.148.17)
Error: Root hints list has invalid root hint server:
j.root-servers.net. (192.58.128.30)
Error: Root hints list has invalid root hint server:
k.root-servers.net. (193.0.14.129)
Error: Root hints list has invalid root hint server:
l.root-servers.net. (198.32.64.12)
Error: Root hints list has invalid root hint server:
m.root-servers.net. (202.12.27.33)
DC: SERVER-DC2.OURDOMAIN.com
Domain: OURDOMAIN.com
TEST: Forwarders/Root hints (Forw)
Error: Root hints list has invalid root hint server:
a.root-servers.net. (198.41.0.4)
Error: Root hints list has invalid root hint server:
c.root-servers.net. (192.33.4.12)
Error: Root hints list has invalid root hint server:
d.root-servers.net. (128.8.10.90)
Error: Root hints list has invalid root hint server:
e.root-servers.net. (192.203.230.10)
Error: Root hints list has invalid root hint server:
f.root-servers.net. (192.5.5.241)
Error: Root hints list has invalid root hint server:
g.root-servers.net. (192.112.36.4)
Error: Root hints list has invalid root hint server:
h.root-servers.net. (128.63.2.53)
Error: Root hints list has invalid root hint server:
i.root-servers.net. (192.36.148.17)
Error: Root hints list has invalid root hint server:
j.root-servers.net. (192.58.128.30)
Error: Root hints list has invalid root hint server:
k.root-servers.net. (193.0.14.129)
Error: Root hints list has invalid root hint server:
l.root-servers.net. (198.32.64.12)
Error: Root hints list has invalid root hint server:
m.root-servers.net. (202.12.27.33)
Summary of test results for DNS servers used by the above domain
controllers:
DNS server: 128.63.2.53 (h.root-servers.net.)
2 test failures on this DNS server
This is not a valid DNS server. PTR record query for the
1.0.0.127.in-addr.arpa. failed on the DNS server
128.63.2.53
DNS server: 128.8.10.90 (d.root-servers.net.)
2 test failures on this DNS server
This is not a valid DNS server. PTR record query for the
1.0.0.127.in-addr.arpa. failed on the DNS server
128.8.10.90
DNS server: 192.112.36.4 (g.root-servers.net.)
2 test failures on this DNS server
This is not a valid DNS server. PTR record query for the
1.0.0.127.in-addr.arpa. failed on the DNS server
192.112.36.4
DNS server: 192.203.230.10 (e.root-servers.net.)
2 test failures on this DNS server
This is not a valid DNS server. PTR record query for the
1.0.0.127.in-addr.arpa. failed on the DNS server
192.203.230.10
DNS server: 192.33.4.12 (c.root-servers.net.)
2 test failures on this DNS server
This is not a valid DNS server. PTR record query for the
1.0.0.127.in-addr.arpa. failed on the DNS server
192.33.4.12
DNS server: 192.36.148.17 (i.root-servers.net.)
2 test failures on this DNS server
This is not a valid DNS server. PTR record query for the
1.0.0.127.in-addr.arpa. failed on the DNS server
192.36.148.17
DNS server: 192.5.5.241 (f.root-servers.net.)
2 test failures on this DNS server
This is not a valid DNS server. PTR record query for the
1.0.0.127.in-addr.arpa. failed on the DNS server
192.5.5.241
DNS server: 192.58.128.30 (j.root-servers.net.)
2 test failures on this DNS server
This is not a valid DNS server. PTR record query for the
1.0.0.127.in-addr.arpa. failed on the DNS server
192.58.128.30
DNS server: 193.0.14.129 (k.root-servers.net.)
2 test failures on this DNS server
This is not a valid DNS server. PTR record query for the
1.0.0.127.in-addr.arpa. failed on the DNS server
193.0.14.129
DNS server: 198.32.64.12 (l.root-servers.net.)
2 test failures on this DNS server
This is not a valid DNS server. PTR record query for the
1.0.0.127.in-addr.arpa. failed on the DNS server
198.32.64.12
DNS server: 198.41.0.4 (a.root-servers.net.)
2 test failures on this DNS server
This is not a valid DNS server. PTR record query for the
1.0.0.127.in-addr.arpa. failed on the DNS server
198.41.0.4
DNS server: 202.12.27.33 (m.root-servers.net.)
2 test failures on this DNS server
This is not a valid DNS server. PTR record query for the
1.0.0.127.in-addr.arpa. failed on the DNS server
202.12.27.33
C:\>
Does that help with anything? Thanks again in advanced!!
~~
DY
"Paul Bergson [MVP-DS]" wrote:
Is this other dc a Global Catalog server? What about dns, where do the.
clients get dns? If it is AD integrated dns then clients should point to
both dc's for dns services.
Global Catalog
http://support.microsoft.com/default.aspx?scid=kb;en-us;313994
--
Paul Bergson
MVP - Directory Services
MCT, MCSE, MCSA, Security+, BS CSci
2003, 2000 (Early Achiever), NT
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.
"DY" <DY@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:4CA65DE9-3714-4F38-B3A3-8411A6782534@xxxxxxxxxxxxxxxx
All,
We had a DC crash due to memory problems and our other didn't take over as
it should have. It seems like we have been running off of only one DC for
a
while. The one that locked up held all FSMO rolls. The good thing was
that
rebooting the locked-up server (an applying a patch that caused the
problem)
brought this server back on line.
When looking into why the other DC didn't work properly I ran the
following
and got this result. Can you guide me on where I should look next?
c:\>dcdiag /e /q
An Error Event occured. EventID: 0x00000457
Time Generated: 10/10/2007 10:45:10
(Event String could not be retrieved)
An Error Event occured. EventID: 0x00000457
Time Generated: 10/10/2007 10:45:11
(Event String could not be retrieved)
An Error Event occured. EventID: 0x00000457
Time Generated: 10/10/2007 10:45:11
(Event String could not be retrieved)
......................... SERVER-DC2 failed test systemlog
- Follow-Ups:
- Re: One DC crashed and the other didn't take over - Please assist
- From: Paul Bergson [MVP-DS]
- Re: One DC crashed and the other didn't take over - Please assist
- References:
- One DC crashed and the other didn't take over - Please assist
- From: DY
- Re: One DC crashed and the other didn't take over - Please assist
- From: Paul Bergson [MVP-DS]
- One DC crashed and the other didn't take over - Please assist
- Prev by Date: Re: Seeking Tool
- Next by Date: Re: AD and trusted root certificates, how to?
- Previous by thread: Re: One DC crashed and the other didn't take over - Please assist
- Next by thread: Re: One DC crashed and the other didn't take over - Please assist
- Index(es):
Relevant Pages
|
Loading
