Re: Also to add> Re: Ex2k services couln't start!!!!!

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

From: Ace Fekay [MVP] (PleaseSubstituteMyActualFirstName&LastNameHere_at_hotmail.com)
Date: 06/05/04


Date: Sat, 5 Jun 2004 14:27:06 -0400

In news:187fb01c44ab8$e7a2f1b0$a501280a@phx.gbl,
Charisma <anonymous@discussions.microsoft.com> posted their thoughts, then I
offered mine
> Hi Ace,these are the errors on two dc's:
> The eventviewer of first DC:testserver
> Event Type: Warning
> Event Source: NtFrs
> Event Category: None
> Event ID: 13508
> Date: 2004/06/01
> Time: 03:31:14 ?.?
> User: N/A
> Computer: testserver
> Description:
> The File Replication Service is having trouble enabling
> replication from NOTEBOOK-7 to testserver
> for c:\winnt\sysvol\domain using the DNS name notebook-
> 7.test-new.com. FRS will keep retrying.
> Following are some of the reasons you would see this
> warning.
>
> [1] FRS can not correctly resolve the DNS name notebook-
> 7.test-new.com from this computer.
> [2] FRS is not running on notebook-7.test-new.com.
> [3] The topology information in the Active Directory for
> this replica has not yet replicated to
> all the Domain Controllers.
>
> This event log message will appear once per connection,
> After the problem is fixed you will see
> another event log message indicating that the connection
> has been established.
>
>
> Event Type: Error
> Event Source: DNS
> Event Category: None
> Event ID: 6702
> Date: 2004/05/29
> Time: 01:37:35 ?.?
> User: N/A
> Computer: testserver
> Description:
> DNS Server has updated its own host (A) records. In order
> to insure that its DS-integrated peer
> DNS servers are able to replicate with this server, an
> attempt was made to update them with the
> new records through dynamic update. An error was
> encountered during this update, the record data
> is the error code.
>
> If this DNS server does not have any DS-integrated peers,
> then this error
> should be ignored.
>
> If this DNS server's ActiveDirectory replication partners
> do not have the correct IP address(es)
> for this server, they will be unable to replicate with it.
>
> To insure proper replication:
> 1) Find this server's ActiveDirectory replication partners
> that run the DNS server.
> 2) Open DnsManager and connect in turn to each of the
> replication partners.
> 3) On each server, check the host (A record) registration
> for THIS server.
> 4) Delete any A records that do NOT correspond to IP
> addresses of this server.
> 5) If there are no A records for this server, add at least
> one A record corresponding to an
> address on this server, that the replication partner can
> contact. (In other words, if there
> multiple IP addresses for this DNS server, add at least
> one that is on the same network as the
> ActiveDirectory DNS server you are updating.)
> 6) Note, that is not necessary to update EVERY replication
> partner. It is only necessary that
> the records are fixed up on enough replication partners so
> that every server that replicates
> with this server will receive (through replication) the
> new data.
> Data:
> 0000: 2d 23 00 00 -#..
>
> Event Type: Error
> Event Source: NETLOGON
> Event Category: None
> Event ID: 5790
> Date: 2004/06/02
> Time: 08:52:19 ?.?
> User: N/A
> Computer: testserver
> Description:
> The description for Event ID ( 5790 ) in Source (
> NETLOGON ) cannot be found. The local computer
> may not have the necessary registry information or message
> DLL files to display messages from a
> remote computer. The following information is part of the
> event: NOTEBOOK-7; Access is denied. .
> Data:
> 0000: 22 00 00 c0 "..À
>
> notebook-7 eventviewererrors:
>
> Event Type: Warning
> Event Source: NtFrs
> Event Category: None
> Event ID: 13562
> Date: 6/2/2004
> Time: 8:52:57 AM
> User: N/A
> Computer: NOTEBOOK-7
> Description:
> Following is the summary of warnings and errors
> encountered by File Replication Service
> while polling the Domain Controller notebook-7.test-
> new.com for FRS replica set
> configuration information.
>
> Could not bind to a Domain Controller. Will try again at
> next polling cycle.
>
>
>
>
>
> Event Type: Error
> Event Source: NETLOGON
> Event Category: None
> Event ID: 5721
> Date: 6/2/2004
> Time: 3:07:21 PM
> User: N/A
> Computer: NOTEBOOK-7
> Description:
> The session setup to the Windows NT or Windows 2000 Domain
> Controller \\testserver.test-new.com
> for the domain testdomain failed because the Domain
> Controller does not have an account for the
> computer NOTEBOOK-7.
> Data:
> 0000: 8b 01 00 c0 ?..À
> -------------------
> Thank you very very much Ace,I think I bored you.
> ---
> Regards
> Charisma
>

Have you checked the SRV records to ensure that both machines are registered
in DNS?

Try this:
Delete all of the SRV records in DNS.
Then delete the system32\config\netlogon.dns and dnb files
THen delete any reference to the two machines' A records in DNS
Then ipconfig /registerdns
Then net stop netlogon
THen net start netlogon

And then run netdiag /v /fix
Then run dcdiag /v

Otherwise, is everything is registered, then theres something else going on
that I cannot see. That is why I offered to remote in.

-- 
Regards,
Ace
Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS-IS" with no warranties and confers no
rights.
Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
HAM AND EGGS: A day's work for a chicken; A lifetime commitment for a
pig. -- 
=================================


Relevant Pages

  • Re: Active directory replication problems
    ... I've had replication succeed in the past. ... The DNS server has encountered a critical error from the Active ... If this DNS server's ActiveDirectory replication partners do not have the ...
    (microsoft.public.windows.server.sbs)
  • Re: Replication problems
    ... w2k3 DNS Server Log ... If this DNS server does not have any DS-integrated peers, ... If this DNS server's Active Directory replication partners do not have ... Find this server's Active Directory replication partners that run the ...
    (microsoft.public.windows.server.active_directory)
  • Re: AD Policy Errors 1054, 1053
    ... you can choose add server and use the name of the new one. ... with an additional DNS server as secondary server, so that it not only points ... Latency information for 4 entries in the vector were ... Replication Site Latency Check ...
    (microsoft.public.windows.server.active_directory)
  • Re: SA hungs on starting
    ... Testing server: Corporate\MORPHEUS ... The replication generated an error: ... Event Type: Warning ... Event Source: MSExchangeMU ...
    (microsoft.public.exchange2000.admin)
  • Re: Replication Issues
    ... > the 2003 server. ... > Event Type: Warning ... > Event Category: Replication Errors ... > on Public Folder Store "First Storage Group\Public Folder Store ...
    (microsoft.public.exchange2000.information.store)