Re: PDC Is not replicating !!

Hi Ace,
Do you have a messenger on?

Here are the step I have done.

1. Ghosted 2 domain controller from HP DL320 G2 to G3 Server.
2. Manage to change the Driver issue to boot the server.
3. IP address all remain the same.
4. Istall rollup service pack 1
5. I manage to ping each other with IP address and hostname.
6 Issue DCDIAG on PDC
C:\WINNT\Profiles\Administrator>dcdiag

Domain Controller Diagnosis

Performing initial setup:
Done gathering initial info.

Doing initial required tests

Testing server: Redbus\SERVER01
Starting test: Connectivity
......................... SERVER01 passed test Connectivity

Doing primary tests

Testing server: Redbus\SERVER01
Starting test: Replications
......................... SERVER01 passed test Replications
Starting test: NCSecDesc
......................... SERVER01 passed test NCSecDesc
Starting test: NetLogons
......................... SERVER01 passed test NetLogons
Starting test: Advertising
......................... SERVER01 passed test Advertising
Starting test: KnowsOfRoleHolders
......................... SERVER01 passed test KnowsOfRoleHolders
Starting test: RidManager
......................... SERVER01 passed test RidManager
Starting test: MachineAccount
......................... SERVER01 passed test MachineAccount
Starting test: Services
IsmServ Service is stopped on [SERVER01]
......................... SERVER01 failed test Services
Starting test: ObjectsReplicated
......................... SERVER01 passed test ObjectsReplicated
Starting test: frssysvol
There are errors after the SYSVOL has been shared.
The SYSVOL can prevent the AD from starting.
......................... SERVER01 passed test frssysvol
Starting test: kccevent
......................... SERVER01 passed test kccevent
Starting test: systemlog
......................... SERVER01 passed test systemlog

Running enterprise tests on : server.dr
Starting test: Intersite
......................... server.dr passed test Intersite
Starting test: FsmoCheck
......................... server.dr passed test FsmoCheck

7. DCDIAG on BDC

C:\>dcdiag

Domain Controller Diagnosis

Performing initial setup:
Done gathering initial info.

Doing initial required tests

Testing server: Redbus\SERVER02
Starting test: Connectivity
......................... SERVER02 passed test Connectivity

Doing primary tests

Testing server: Redbus\SERVER02
Starting test: Replications
[SERVER01] DsBind() failed with error -2146893022,
Win32 Error -2146893022.
......................... SERVER02 passed test Replications
Starting test: NCSecDesc
......................... SERVER02 passed test NCSecDesc
Starting test: NetLogons
......................... SERVER02 passed test NetLogons
Starting test: Advertising
Warning: SERVER02 is not advertising as a time server.
......................... SERVER02 failed test Advertising
Starting test: KnowsOfRoleHolders
Warning: SERVER01 is the Schema Owner, but is not responding to DS
RPC Bind.
[SERVER01] LDAP bind failed with error 31,
Win32 Error 31.
Warning: SERVER01 is the Schema Owner, but is not responding to
LDAP Bind.
Warning: SERVER01 is the Domain Owner, but is not responding to DS
RPC Bind.
Warning: SERVER01 is the Domain Owner, but is not responding to
LDAP Bind.
Warning: SERVER01 is the PDC Owner, but is not responding to DS RPC
Bind.
Warning: SERVER01 is the PDC Owner, but is not responding to LDAP
Bind.
Warning: SERVER01 is the Rid Owner, but is not responding to DS RPC
Bind.
Warning: SERVER01 is the Rid Owner, but is not responding to LDAP
Bind.
Warning: SERVER01 is the Infrastructure Update Owner, but is not
responding to DS RPC Bind.
Warning: SERVER01 is the Infrastructure Update Owner, but is not
responding to LDAP Bind.
......................... SERVER02 failed test KnowsOfRoleHolders
Starting test: RidManager
[SERVER02] DsBindWithCred() failed with error -2146893022. Win32
Error -2146893022
......................... SERVER02 failed test RidManager
Starting test: MachineAccount
......................... SERVER02 passed test MachineAccount
Starting test: Services
w32time Service is stopped on [SERVER02]
......................... SERVER02 failed test Services
Starting test: ObjectsReplicated
......................... SERVER02 passed test ObjectsReplicated
Starting test: frssysvol
There are errors after the SYSVOL has been shared.
The SYSVOL can prevent the AD from starting.
......................... SERVER02 passed test frssysvol
Starting test: kccevent
......................... SERVER02 passed test kccevent
Starting test: systemlog
......................... SERVER02 passed test systemlog

Running enterprise tests on : SERVER.dr
Starting test: Intersite
......................... SERVER.dr passed test Intersite
Starting test: FsmoCheck
......................... SERVER.dr passed test FsmoCheck


Hope It helps you to solve my issue..
Many Thanks.




Basically I have check all ipconfig /all. Everything is normal. However
when my BDC try to browse the PDC via hostname. It come out error message.

"Ace Fekay [MVP]" wrote:

> In news:7F85F448-735F-4D19-A043-F1874DFA65FB@xxxxxxxxxxxxx,
> Quefz <Quefz@xxxxxxxxxxxxxxxxxxxxxxxxx> made this post, which I then
> commented about below:
> > Hi Ace,
> >
> > I think I have fix the replicating issue.
> > somehow I have another error in the event log.
> >
> > Event Type: Warning
> > Event Source: NtFrs
> > Event Category: None
> > Event ID: 13508
> > Date: 07/09/2005
> > Time: 17:45:06
> > User: N/A
> > Computer: HEDGECONNECT01
> > Description:
> > The File Replication Service is having trouble enabling replication
> > from SERVER02 to SERVERT01 for c:\winnt\sysvol\domain using the DNS
> > name server02.server.dr. FRS will keep retrying.
> > Following are some of the reasons you would see this warning.
> >
> > [1] FRS can not correctly resolve the DNS name server02.server.dr
> > from this computer.
> > [2] FRS is not running on server02.server.dr.
> > [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.
> > Data:
> > 0000: 00 00 00 00 ....
>
> I'm glad you believe you fixed the issue, but the above error is evident
> that the problem still exists.
>
> Can you answer my previous questions so I can understand exactly what you
> did?
>
> Can you also provide an unedited ipconfig /all from both machines please?
>
> Thanks
>
> Ace
>
>
>
.

Relevant Pages

  • Re: DNS Access Denied
    ... I believed that the replications are not happening from this both ... ILSAS1 is the Schema Owner, but is not responding to DS RPC Bind. ... > problems have their origin in DNS issues. ... you mean the MMC cannot add the other DNS server. ...
    (microsoft.public.windows.server.dns)
  • [UNIX] Hardening the BIND DNS Server
    ... Hardening the BIND DNS Server ... Your Domain Name Service is the road sign to your systems on the Internet. ...
    (Securiteam)
  • Re: Mail server security - best practices?
    ... Both BIND and qmail are pretty secure, ... and mail on a server that's 'half-internal' in that you seem not to ... I still employ IMAP-SSL on the private server, ...
    (comp.unix.bsd.openbsd.misc)
  • Re: Active Directory Replication error
    ... > The primary DC that is rejecting the other one is this server is called ... > Starting test: Replications ... >> If you don't have the tools installed, ... >> Paul Bergson MCT, MCSE, MCSA, CNE, CNA, CCA ...
    (microsoft.public.windows.server.active_directory)
  • Re: DNS Poisoning, pharming, pollution
    ... running Windows 2003 and have the "secure cache against pollution" setting ... the next thing to look for would be a malicious program on the server. ... >> Every server is configured with our ISP's DNS resolvers as forwarders. ... but I don't think we're running BIND. ...
    (microsoft.public.windows.server.dns)