Re: sys vol check
- From: Scott Sendelbach <ScottSendelbach@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 28 Aug 2006 15:02:02 -0700
We have three different DNS servers, 1 in each office. I have modified the
DNS FORWARDERS per your suggestion. I have several questions about that.
1. How do I know when it will be safe to remove them from the DHCP device
that is handing out licenses?
2. Why don't I want the ISP DNS servers listed? We have a hard time
accessing the internet without them there.
3. All three offices are serviced by COX, but each office has their own ISP
DNS server addresses because of their geographic location. Will doing this
step ruin the connection to the internet?
"Jorge Silva" wrote:
Hi.
First remove the ISP DNS servers from your NIC configuration.
(68.2.16.30;68.1.208.30)
To resolve internet names configure Forwarding
http://support.microsoft.com/kb/323380/
Second sounds like your server isn't resolving the parent domain, to solve
that make sure that your server can resolve the FQDN of the DCs at Root
domain. You can configure Conditional forwarding, Secondary zones or you can
replicate the root DNS Zone at forest level. Attention the _msdcs.domain.tld
contain information about Global catalog and other domain/forest important
records and they only exist in parent (root) DNS server (this zone contains
information that IS ONLY AVAILABLE IN THE ROOT), so is always a good
practice to replicate the root _msdcs.domain.tld across the forest.
How to Create a Child Domain in Active Directory and Delegate the DNS
Namespace to the Child Domain
http://support.microsoft.com/kb/255248/
Conditional Forwarding in Windows Server 2003
http://support.microsoft.com/default.aspx?scid=kb;en-us;304491
How to Delegate All Internet Top-Level Domains on an Internal Root DNS
Server
http://support.microsoft.com/default.aspx?scid=kb;en-us;294906&sd=RMVP
--
I hope that the information above helps you
Good Luck
Jorge Silva
MCSA
Systems Administrator
"Scott Sendelbach" <ScottSendelbach@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:94A1B9A9-6943-4A47-8CF3-ACA26F85AD86@xxxxxxxxxxxxxxxx
Here is the DCDIAG Test results. Yes this DC is a DNS server.
Doing initial required tests
Testing server: PHOENIX\ADMINSERVER
Starting test: Connectivity
* Active Directory LDAP Services Check
The host
1ea9b77e-235f-470b-9dff-390786e1077d._msdcs.CORP.DLECINC.com c
ould not be resolved to an
IP address. Check the DNS server, DHCP, server name, etc
......................... ADMINSERVER failed test Connectivity
Testing server: PHOENIX\SERVER
Starting test: Connectivity
* Active Directory LDAP Services Check
The host
857bd24b-6e5b-416f-9c15-912bd3767259._msdcs.CORP.DLECINC.com c
ould not be resolved to an
IP address. Check the DNS server, DHCP, server name, etc
Although the Guid DNS name
(857bd24b-6e5b-416f-9c15-912bd3767259._msdcs.CORP.DLECINC.com)
couldn't be resolved, the server name (server.CORP.DLECINC.COM)
resolved to the IP address (192.168.168.5) and was pingable.
Check
that the IP address is registered correctly with the DNS server.
......................... SERVER failed test Connectivity
Testing server: LASVEGAS\HENDERSON
Starting test: Connectivity
* Active Directory LDAP Services Check
The host
480ce73a-6788-4c5b-9bd3-23978bf8245f._msdcs.CORP.DLECINC.com c
ould not be resolved to an
IP address. Check the DNS server, DHCP, server name, etc
......................... HENDERSON failed test Connectivity
Testing server: IRVINE\IRVINE
Starting test: Connectivity
* Active Directory LDAP Services Check
The host
18633bd7-ee97-4eeb-a17b-a53a207df394._msdcs.CORP.DLECINC.com c
ould not be resolved to an
IP address. Check the DNS server, DHCP, server name, etc
......................... IRVINE failed test Connectivity
Testing server: PHOENIX\MESA
Starting test: Connectivity
* Active Directory LDAP Services Check
The host
a0814bcc-59c0-4c09-9cc8-65b920bb9cad._msdcs.CORP.DLECINC.com c
ould not be resolved to an
IP address. Check the DNS server, DHCP, server name, etc
Although the Guid DNS name
(a0814bcc-59c0-4c09-9cc8-65b920bb9cad._msdcs.CORP.DLECINC.com)
couldn't be resolved, the server name (mesa.CORP.DLECINC.COM)
resolved
to the IP address (192.168.168.3) and was pingable. Check that
the
IP
address is registered correctly with the DNS server.
......................... MESA failed test Connectivity
Doing primary tests
Testing server: PHOENIX\ADMINSERVER
Skipping all tests, because server ADMINSERVER is
not responding to directory service requests
Testing server: PHOENIX\SERVER
Skipping all tests, because server SERVER is
not responding to directory service requests
Testing server: LASVEGAS\HENDERSON
Skipping all tests, because server HENDERSON is
not responding to directory service requests
Testing server: IRVINE\IRVINE
Skipping all tests, because server IRVINE is
not responding to directory service requests
Testing server: PHOENIX\MESA
Skipping all tests, because server MESA is
not responding to directory service requests
DNS Tests are running and not hung. Please wait a few minutes...
Running partition tests on : Schema
Starting test: CrossRefValidation
For the partition
(CN=Schema,CN=Configuration,DC=CORP,DC=DLECINC,DC=com) we
encountered the following error retrieving the cross-ref's
(CN=Enterprise
Schema,CN=Partitions,CN=Configuration,DC=CORP,DC=DLEC
INC,DC=com)
information:
LDAP Error 0x3a (58).
......................... Schema failed test CrossRefValidation
Starting test: CheckSDRefDom
......................... Schema passed test CheckSDRefDom
Running partition tests on : Configuration
Starting test: CrossRefValidation
For the partition (CN=Configuration,DC=CORP,DC=DLECINC,DC=com)
we
encountered the following error retrieving the cross-ref's
(CN=Enterprise
Configuration,CN=Partitions,CN=Configuration,DC=CORP,
DC=DLECINC,DC=com)
information:
LDAP Error 0x3a (58).
......................... Configuration failed test
CrossRefValidation
Starting test: CheckSDRefDom
......................... Configuration passed test CheckSDRefDom
Running partition tests on : CORP
Starting test: CrossRefValidation
For the partition (DC=CORP,DC=DLECINC,DC=com) we encountered
the
following error retrieving the cross-ref's
(CN=CORP,CN=Partitions,CN=Configuration,DC=CORP,DC=DLECINC,DC=com)
information:
LDAP Error 0x3a (58).
......................... CORP failed test CrossRefValidation
Starting test: CheckSDRefDom
......................... CORP passed test CheckSDRefDom
Running enterprise tests on : CORP.DLECINC.com
Starting test: Intersite
Doing intersite inbound replication test on site PHOENIX:
Locating & Contacting Intersite Topology Generator (ISTG) ...
The ISTG for site PHOENIX is: MESA.
Checking for down bridgeheads ...
Bridghead LASVEGAS\HENDERSON is up and replicating fine.
Remote bridgehead LASVEGAS\HENDERSON also couldn't be
contacted
by dcdiag. Check this server.
Bridghead PHOENIX\ADMINSERVER is up and replicating fine.
Remote bridgehead PHOENIX\ADMINSERVER also couldn't be
contacted
by dcdiag. Check this server.
Bridghead IRVINE\IRVINE is up and replicating fine.
Remote bridgehead IRVINE\IRVINE also couldn't be contacted
by
dcdiag. Check this server.
Doing in depth site analysis ...
Remote site LASVEGAS is replicating to the local site
PHOENIX
the writeable NC Schema correctly.
Remote site LASVEGAS is replicating to the local site
PHOENIX
the writeable NC Configuration correctly.
Remote site LASVEGAS is replicating to the local site
PHOENIX
the writeable NC CORP correctly.
Remote site IRVINE is replicating to the local site PHOENIX
the
writeable NC Schema correctly.
Remote site IRVINE is replicating to the local site PHOENIX
the
writeable NC Configuration correctly.
Remote site IRVINE is replicating to the local site PHOENIX
the
writeable NC CORP correctly.
Doing intersite inbound replication test on site LASVEGAS:
Locating & Contacting Intersite Topology Generator (ISTG) ...
[HENDERSON] LDAP search failed with error 58,
The specified server cannot perform the requested
operation..
[HENDERSON] DsBindWithSpnEx() failed with error 1722,
The RPC server is unavailable..
Printing RPC Extended Error Info:
Error Record 1, ProcessID is 824 (DcDiag)
System Time is: 8/25/2006 14:58:7:314
Generating component is 8 (winsock)
Status is 1722: The RPC server is unavailable.
Detection location is 322
Error Record 2, ProcessID is 824 (DcDiag)
System Time is: 8/25/2006 14:58:7:314
Generating component is 8 (winsock)
Status is 11001: No such host is known.
Detection location is 320
NumberOfParameters is 1
Unicode string:
480ce73a-6788-4c5b-9bd3-23978bf8245f._msdcs.CO
RP.DLECINC.com
*Warning: Currest ISTG (HENDERSON) is down. Looking for a
new
ISTG.
***Error: The current ISTG is down in site LASVEGAS and
further
dcdiag could not contact any other servers in the site that
could take the ISTG role. Ensure there is at least one up
DC.
Must abandon inbound intersite replication test for this
site.
Doing intersite inbound replication test on site IRVINE:
Locating & Contacting Intersite Topology Generator (ISTG) ...
[IRVINE] LDAP search failed with error 58,
The specified server cannot perform the requested
operation..
[IRVINE] DsBindWithSpnEx() failed with error 1722,
The RPC server is unavailable..
Printing RPC Extended Error Info:
Error Record 1, ProcessID is 824 (DcDiag)
System Time is: 8/25/2006 14:58:7:330
Generating component is 8 (winsock)
Status is 1722: The RPC server is unavailable.
Detection location is 322
Error Record 2, ProcessID is 824 (DcDiag)
System Time is: 8/25/2006 14:58:7:330
Generating component is 8 (winsock)
Status is 11001: No such host is known.
Detection location is 320
NumberOfParameters is 1
Unicode string:
18633bd7-ee97-4eeb-a17b-a53a207df394._msdcs.CO
RP.DLECINC.com
*Warning: Currest ISTG (IRVINE) is down. Looking for a new
ISTG.
***Error: The current ISTG is down in site IRVINE and
further
dcdiag could not contact any other servers in the site that
could take the ISTG role. Ensure there is at least one up
DC.
Must abandon inbound intersite replication test for this
site.
......................... CORP.DLECINC.com failed test Intersite
Starting test: FsmoCheck
[ADMINSERVER] LDAP search failed with error 58,
The specified server cannot perform the requested operation..
Warning: Couldn't verify this server as a GC in this servers AD.
GC Name: \\adminserver.CORP.DLECINC.COM
Locator Flags: 0xe00001fd
PDC Name: \\adminserver.CORP.DLECINC.COM
Locator Flags: 0xe00001fd
Time Server Name: \\mesa.CORP.DLECINC.COM
Locator Flags: 0xe00001f8
Preferred Time Server Name: \\mesa.CORP.DLECINC.COM
Locator Flags: 0xe00001f8
KDC Name: \\mesa.CORP.DLECINC.COM
Locator Flags: 0xe00001f8
......................... CORP.DLECINC.com passed test FsmoCheck
Starting test: DNS
Test results for domain controllers:
DC: adminserver.CORP.DLECINC.COM
Domain: CORP.DLECINC.com
TEST: Authentication (Auth)
Authentication test: Successfully completed
TEST: Basic (Basc)
Error: No LDAP connectivity
- Follow-Ups:
- Re: sys vol check
- From: Jorge Silva
- Re: sys vol check
- References:
- sys vol check
- From: Scott Sendelbach
- Re: sys vol check
- From: Jorge Silva
- Re: sys vol check
- From: Scott Sendelbach
- Re: sys vol check
- From: Jorge Silva
- sys vol check
- Prev by Date: Re: Moving/exporting users from one AD to another
- Next by Date: Re: Syncing groups between forests
- Previous by thread: Re: sys vol check
- Next by thread: Re: sys vol check
- Index(es):
Relevant Pages
|
