Re: No DC in Active Directory
- From: Preston <Preston@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 1 Aug 2007 09:00:02 -0700
Thanks for respons.
Only two of them are DCs. The third is a member server hosting Exchange
Server 2007. The primary DC points to itself as the DNS. The second server
points to an outside DNS server1st, itself second, and the primary third (I
have no idea why). My concern with your suggestion is that the primary DC is
the one that does not show any computers or DCs in AD computers and users,
but the second one shows both. They both show up as GCs in both servers. I
will try your suggestions, thanks.
My next question is whether it is safe to perform these functions during
working hours with users logged onto the servers or is this something that
will require a system restart and knock everyon off? Thanks again for help.
Awaiting reply.
Preston
"Harj" wrote:
On Aug 1, 1:06 am, Preston <Pres...@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:.
I have 3 servers of which the newest is an Exchange Server 2007 running on
Windows 2003 x64 Server. The other two are Windows 2003 Server 2003 w/SP1.
I just installed the Exchange Server. Prior to that, things seemed to be ok.
However, the first server (Srvr1) now shows no DCs in the Active Directory
when I go to AD users and computers. Also, no computers show up in that
display either. On Srvr2 which is in a different city connected via a
SonicWall VPN, both servers, DCs and computers show up in the AD users and
computers display. When I restart Srvr1, I get the following message: Net
Service Configuration. The specified service does not exist as an installed
service. The even log has two items of interest. They are below. Any help
is appreciated.
Event Type: Warning
Event Source: NtFrs
Event Category: None
Event ID: 13509
Date: 7/30/2007
Time: 3:00:21 PM
User: N/A
Computer: NSRSRVR1
Description:
The File Replication Service has enabled replication from NSRSRVR2 to
NSRSRVR1 for c:\windows\sysvol\domain after repeated retries.
and
Event Type: Error
Event Source: NTDS Replication
Event Category: DS RPC Client
Event ID: 2087
Date: 7/29/2007
Time: 7:58:23 PM
User: NT AUTHORITY\ANONYMOUS LOGON
Computer: NSRSRVR1
Description:
Active Directory could not resolve the following DNS host name of the source
domain controller to an IP address. This error prevents additions, deletions
and changes in Active Directory from replicating between one or more domain
controllers in the forest. Security groups, group policy, users and computers
and their passwords will be inconsistent between domain controllers until
this error is resolved, potentially affecting logon authentication and access
to network resources.
Source domain controller:
nsrsrvr2
Failing DNS host name:
569aeef5-961f-4b7c-b524-b908d6402b77._msdcs.nsrnet.local
NOTE: By default, only up to 10 DNS failures are shown for any given 12 hour
period, even if more than 10 failures occur. To log all individual failure
events, set the following diagnostics registry value to 1:
Registry Path:
HKLM\System\CurrentControlSet\Services\NTDS\Diagnostics\22 DS RPC Client
User Action:
1) If the source domain controller is no longer functioning or its
operating system has been reinstalled with a different computer name or
NTDSDSA object GUID, remove the source domain controller's metadata with
ntdsutil.exe, using the steps outlined in MSKB article 216498.
2) Confirm that the source domain controller is running Active directory
and is accessible on the network by typing "net view \\<source DC name>" or
"ping <source DC name>".
3) Verify that the source domain controller is using a valid DNS server for
DNS services, and that the source domain controller's host record and CNAME
record are correctly registered, using the DNS Enhanced version of DCDIAG.EXE
available onhttp://www.microsoft.com/dns
dcdiag /test:dns
4) Verify that that this destination domain controller is using a valid DNS
server for DNS services, by running the DNS Enhanced version of DCDIAG.EXE
command on the console of the destination domain controller, as follows:
dcdiag /test:dns
5) For further analysis of DNS error failures see KB 824449:
http://support.microsoft.com/?kbid=824449
Additional Data
Error value:
11004 The requested name is valid, but no data of the requested type was
found.
Hi,
Where are the three DC's pointed to for DNS?
Event 13509 is no biggie as it states it has finally enabled
replication. We would just want to find out why it takes time between
the 13508 and the 13509.
Three DC's I would point all of them to the PDC for primary and
themselfs for secondary. Flush and reregister dns and restart the net
logon service on all of them.
Verify they are all Global Catalog servers also
Good Luck
Harj Singh
Power Your Active Directory Investment
www.specopssoft.com
- Follow-Ups:
- Re: No DC in Active Directory
- From: Harj
- Re: No DC in Active Directory
- References:
- No DC in Active Directory
- From: Preston
- Re: No DC in Active Directory
- From: Harj
- No DC in Active Directory
- Prev by Date: Re: Synchronize only attributes you want ADAMSync
- Next by Date: Re: Ever since I promoted this server to a DC I get this error:
- Previous by thread: Re: No DC in Active Directory
- Next by thread: Re: No DC in Active Directory
- Index(es):
Relevant Pages
|
Loading
