Announcement

Collapse
No announcement yet.

Replication problem

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Replication problem

    Hi folks,
    its getting usual that I have strange problems.
    This time is replication. Since recent power failure I am getting numerous errors 1030 and 1097 in app log and 5774 in system log. After I analyzed problem I fond out that replication is not performing right. I have replication from PDC to secundary DC but not the other way round.
    I checked DNS and it seem ok. Also checked SYSVOL share and permisions and it seem ok. DCdiag test passed all except some errors in repl test. There is also statement that some SRV records are not registered but in DNS I can see they are registered. One of those error logs said that machine account could not be found and the logon attempt failed.

    Any ideas or suggestions?
    Tnx a lot!
    The chase is better than the catch

  • #2
    Re: Replication problem

    The following tools help in identifying replication problems....

    From command prompt - c:\repadmin /showreps

    or using c:\replmon

    Was this how you identified the replication issue?

    Just checking - this is a 2003 environment????

    http://support.microsoft.com/kb/284963
    For error 5574
    Are you sure about your DNS settings?

    1097 & 1030
    http://support.microsoft.com/kb/832215
    Check all your services are starting correctly.
    Last edited by fergie; 29th December 2009, 11:27.
    MCP 2003, XP, MCP Exchange 2003, Sonicwall CSSA, ITIL V3

    Comment


    • #3
      Re: Replication problem

      Hi fergie,
      actualy I noticed repl problems from dcdiag and then tried it from AD sites and services, NTDS settings wont replicate. but that is not important.
      I ran repadmin /showreps and get couple of Access is denied and couple of The remote system is not available.
      I did double check DNS and everything is ok.
      I already red those articles and checked all steps in there. Nothing.
      It is 2003 enviroment. 2 DCs, identical software and hardware.
      in dcdiag.exe /fix output, besides repl errors there are also frsevent and kccevent failed.
      The main problem is that i get access denied and I dont know why. Does the machine account get the access denied or what?
      Checked permisions on SYSVOL share, everything ok.
      The chase is better than the catch

      Comment


      • #4
        Re: Replication problem

        Have you tried resetting the machine account password?

        This resolves some of the replication issues I get, and it would be consistent with the type of issue you are having.....

        Netdom resetpwd /server:Replication_Partner_Server_Name /userd:domainname\administrator_id /passwordd:*



        http://support.microsoft.com/kb/260575 for further information.
        MCP 2003, XP, MCP Exchange 2003, Sonicwall CSSA, ITIL V3

        Comment


        • #5
          Re: Replication problem

          To be honest it did cross my mind but I am not sure what consequences can be.
          I didnt do that before and my fear is that I dont make things worse...
          The chase is better than the catch

          Comment


          • #6
            Re: Replication problem

            I have not had a negative experience when resetting the account before and I do believe this will resolve your issue.

            If you want to research if further look here.....

            http://support.microsoft.com/kb/325850/en-us
            MCP 2003, XP, MCP Exchange 2003, Sonicwall CSSA, ITIL V3

            Comment


            • #7
              Re: Replication problem

              Yes I red that...
              but you realize that I have to reset pwd on PDC?
              Its like I am disjoining it from domain and then rejoin again.
              The chase is better than the catch

              Comment


              • #8
                Re: Replication problem

                No its not.
                MCP 2003, XP, MCP Exchange 2003, Sonicwall CSSA, ITIL V3

                Comment


                • #9
                  Re: Replication problem

                  ok.
                  thank you a lot.
                  I will notify you what I did.
                  The chase is better than the catch

                  Comment


                  • #10
                    Re: Replication problem

                    What does DCDIAG and NETDIAG show???

                    Can you post an IPCONFIG /ALL???

                    Comment


                    • #11
                      Re: Replication problem

                      First thing..
                      Fergie I did pwd reset and that didnt help. everything is the same.

                      Here are outputs from dcdiag, netdiag and repadmin

                      DCDiag output.txt

                      Repadmin.txt

                      NetDiag.txt


                      C:\Documents and Settings\root>ipconfig /all

                      Windows IP Configuration

                      Host Name . . . . . . . . . . . . : dc
                      Primary Dns Suffix . . . . . . . : int.s-leasing.co.yu
                      Node Type . . . . . . . . . . . . : Hybrid
                      IP Routing Enabled. . . . . . . . : No
                      WINS Proxy Enabled. . . . . . . . : No
                      DNS Suffix Search List. . . . . . : int.s-leasing.co.yu
                      s-leasing.co.yu
                      co.yu

                      Ethernet adapter LAN:

                      Connection-specific DNS Suffix . :
                      Description . . . . . . . . . . . : HP NC373i Multifunction Gigabit Server Ad
                      apter #2
                      Physical Address. . . . . . . . . : 00-21-5A-EE-DD-F2
                      DHCP Enabled. . . . . . . . . . . : No
                      IP Address. . . . . . . . . . . . : 192.168.0.2
                      Subnet Mask . . . . . . . . . . . : 255.255.255.0
                      Default Gateway . . . . . . . . . : 192.168.0.90
                      DNS Servers . . . . . . . . . . . : 192.168.0.2
                      192.168.0.5
                      Primary WINS Server . . . . . . . : 192.168.0.2
                      The chase is better than the catch

                      Comment


                      • #12
                        Re: Replication problem

                        On the server that is not replicating you need to open replmon again and force replication.....
                        And you ran the password reset on "Print" the secondary DC?

                        Expand your DC right click your other DC and select Synchronise with this replication partner.....

                        If its missing goto to add sevrer and add it.

                        Then check the follwoing.....

                        Also is your NetLogon service running ok?

                        I take it 192.168.0.5 is Hostname "PRINT", the server thats not replicating?
                        Which is also a DNS server, am I right?

                        When you ping one server to the other both resolve IP's ok?
                        Last edited by fergie; 30th December 2009, 11:00.
                        MCP 2003, XP, MCP Exchange 2003, Sonicwall CSSA, ITIL V3

                        Comment


                        • #13
                          Re: Replication problem

                          ok this is the explanation:
                          DC(192.168.0.2) is the primary domain controler and it holds DNS role.
                          Print(192.168.0.5) is secondary controler and holds secondary DNS.
                          I ran pwd reset on Print,secondary.
                          replication goes this way: when I expand DC in replmon and right click on DefFirstSiteName\Print and click synchronize I get access denied.
                          When I expand Print and right click DefFirstSiteName\Dc and synchronize everything is ok.
                          Ping is ok.
                          But funny thing happened when I ran nltest /SC_QUERY \domainname on PDC.
                          I got no_such_domain error!
                          on print the same thing is working just fine.
                          NetLogon is started and automatic.
                          I hope I succeeded to explain my situation.
                          Thnx for helping mate
                          The chase is better than the catch

                          Comment


                          • #14
                            Re: Replication problem

                            Routine checks to make.....for now...
                            No Firewall rules changed recently?
                            Also clocks on both servers ok.
                            MCP 2003, XP, MCP Exchange 2003, Sonicwall CSSA, ITIL V3

                            Comment


                            • #15
                              Re: Replication problem

                              dont use firewalls between servers.
                              time synced.
                              The chase is better than the catch

                              Comment

                              Working...
                              X