Announcement

Collapse
No announcement yet.

Win 2000 network failure and dilema on how to proceed [was: First Post In Forum]

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

  • Win 2000 network failure and dilema on how to proceed [was: First Post In Forum]

    HI FORUM,

    this is my 1st post here, even though I have been in this great site before visiting, a couple of times.I have had great success as well as failures with information and help I got from this site.

    It is one of the best site, outside of Microsoft that handles Microsoft platform products well.

    KUDOS TO ALL OF YOU AND ESPECIALLY DANIEL.

    Having said that, I am experiencing numerous problems all occuring at once in my network.

    Briefly here is how it is setup.

    At first there was just one NT 4 server.
    It was replace d by a 2000 server USAHOST. The server ran great Plains dynamics 7.5 sofware, and was used for other uses as print server, dns, file serving etc.

    Then I added two more servers. USAHOST2 to dedicatedly run great plains (now microsoft ) Dynamics application, with SQL loaded.
    USAHOST4 to act as DNS server for clients internet connection. Also to help with printing and files. At first all went ok. But the
    on the event viewer things started to fail one by one

    -Replication of topology failed
    -NTFRS failed
    -Netlogon No domain controller to service log ons
    -GPO objetcs/GPT.INI missing, so no account creation allowed
    -Journal wraps
    -dns failed occasionally to resolve names
    -sysvol unavailable
    -sql database on USAHOST2 backup jobs failed because it cannot tell whether administrator exists or has security priviledges to access database.
    -etc

    I am just wondering what steps should i do first.
    I am also thinking maybe I should just cut my losses and upgrade to server 2003 and recreate same name domain on all three servers?

    Will the clients be able to log in/map drives using credentials on their stations IF I CREATE similar accounts in servers/computers/users.

    The biggest problem for me is that a 3rd party company installed and maintains DYNAMICS software the main app the company depends on. I have no problem formatting the servers and creating things afresh. But do i have to

    Please consider the log for errors I have experienced.
    I have used lots of advice from this forum to ry control the situation but looks like i am failing.
    Thanks for your consideration
    ============================
    SERVER LOGS


    =======DUMFSMOS ON USAHOST ======5/8/2008============

    C:\Program Files>cd resource kit
    C:\Program Files\Resource Kit>dumpfsmos.cmd

    Please provide the name of a domain controller (i.e. dumpfsmos MYDC)


    C:\Program Files\Resource Kit>dumpfsmos.cmd USAHOST
    ntdsutil: roles
    fsmo maintenance: Connections
    server connections: Connect to server USAHOST
    Binding to USAHOST ...
    Connected to USAHOST using credentials of locally logged on user
    server connections: Quit
    fsmo maintenance: select Operation Target
    select operation target: List roles for connected server
    Server "USAHOST" knows about 5 roles
    Schema - CN="NTDS Settings
    DEL:c7f85dc0-14ff-4b6e-839a-dd872b4a93e1",CN=USAHOST,CN=Servers,CN=Default-First
    -Site,CN=Sites,CN=Configuration,DC=USA2K,DC=local
    Domain - CN="NTDS Settings
    DEL:c7f85dc0-14ff-4b6e-839a-dd872b4a93e1",CN=USAHOST,CN=Servers,CN=Default-First
    -Site,CN=Sites,CN=Configuration,DC=USA2K,DC=local
    PDC - CN="NTDS Settings
    DEL:c7f85dc0-14ff-4b6e-839a-dd872b4a93e1",CN=USAHOST,CN=Servers,CN=Default-First
    -Site,CN=Sites,CN=Configuration,DC=USA2K,DC=local
    RID - CN="NTDS Settings
    DEL:c7f85dc0-14ff-4b6e-839a-dd872b4a93e1",CN=USAHOST,CN=Servers,CN=Default-First
    -Site,CN=Sites,CN=Configuration,DC=USA2K,DC=local
    Infrastructure - CN="NTDS Settings
    DEL:c7f85dc0-14ff-4b6e-839a-dd872b4a93e1",CN=USAHOST,CN=Servers,CN=Default-First
    -Site,CN=Sites,CN=Configuration,DC=USA2K,DC=local
    select operation target: Quit
    fsmo maintenance: Quit
    ntdsutil: Quit
    Disconnecting from USAHOST ...
    C:\Program Files\Resource Kit>dumpfsmos.cmd

    C:\Program Files\Resource Kit>



    =================dc diag============

    Domain Controller Diagnosis
    Performing initial setup:
    Done gathering initial info.
    Doing initial required tests
    Testing server: Default-First-Site\USAHOST
    Starting test: Connectivity
    ......................... USAHOST passed test Connectivity
    Doing primary tests
    Testing server: Default-First-Site\USAHOST
    Starting test: Replications
    [Replications Check,USAHOST] A recent replication attempt failed:
    From USAHOST2 to USAHOST
    Naming Context: CN=Schema,CN=Configuration,DC=USA2K,DC=local
    The replication generated an error (8456):
    The source server is currently rejecting replication requests.
    The failure occurred at 2008-05-08 12:54.46.
    The last success occurred at 2007-06-29 13:46.48.
    7909 failures have occurred since the last success.
    Replication has been explicitly disabled through the server options.
    [Replications Check,USAHOST] A recent replication attempt failed:
    From USAHOST2 to USAHOST
    Naming Context: CN=Configuration,DC=USA2K,DC=local
    The replication generated an error (8456):
    The source server is currently rejecting replication requests.
    The failure occurred at 2008-05-08 13:36.51.
    The last success occurred at 2007-07-02 07:19.19.
    67450 failures have occurred since the last success.
    Replication has been explicitly disabled through the server options.
    [Replications Check,USAHOST] A recent replication attempt failed:
    From USAHOST2 to USAHOST
    Naming Context: DC=USA2K,DC=local
    The replication generated an error (8456):
    The source server is currently rejecting replication requests.
    The failure occurred at 2008-05-08 13:32.04.
    The last success occurred at 2007-07-02 07:18.19.
    15494 failures have occurred since the last success.
    Replication has been explicitly disabled through the server options.
    ......................... USAHOST passed test Replications
    Starting test: NCSecDesc
    ......................... USAHOST passed test NCSecDesc
    Starting test: NetLogons
    ......................... USAHOST passed test NetLogons
    Starting test: Advertising
    ......................... USAHOST passed test Advertising
    Starting test: KnowsOfRoleHolders
    Warning: CN="NTDS Settings
    DEL:c7f85dc0-14ff-4b6e-839a-dd872b4a93e1",CN=USAHOST,CN=Servers,CN=Default-First
    -Site,CN=Sites,CN=Configuration,DC=USA2K,DC=local is the Schema Owner, but is de
    leted.
    Warning: CN="NTDS Settings
    DEL:c7f85dc0-14ff-4b6e-839a-dd872b4a93e1",CN=USAHOST,CN=Servers,CN=Default-First
    -Site,CN=Sites,CN=Configuration,DC=USA2K,DC=local is the Domain Owner, but is de
    leted.
    Warning: CN="NTDS Settings
    DEL:c7f85dc0-14ff-4b6e-839a-dd872b4a93e1",CN=USAHOST,CN=Servers,CN=Default-First
    -Site,CN=Sites,CN=Configuration,DC=USA2K,DC=local is the PDC Owner, but is delet
    ed.
    Warning: CN="NTDS Settings
    DEL:c7f85dc0-14ff-4b6e-839a-dd872b4a93e1",CN=USAHOST,CN=Servers,CN=Default-First
    -Site,CN=Sites,CN=Configuration,DC=USA2K,DC=local is the Rid Owner, but is delet
    ed.
    Warning: CN="NTDS Settings
    DEL:c7f85dc0-14ff-4b6e-839a-dd872b4a93e1",CN=USAHOST,CN=Servers,CN=Default-First
    -Site,CN=Sites,CN=Configuration,DC=USA2K,DC=local is the Infrastructure Update O
    wner, but is deleted.
    ......................... USAHOST failed test KnowsOfRoleHolders
    Starting test: RidManager
    Warning: FSMO Role Owner is deleted.
    Warning: attribute rIdSetReferences missing from CN=USAHOST,OU=Domain C
    ontrollers,DC=USA2K,DC=local
    Could not get Rid set Reference :failed with 8481: The search failed to
    retrieve attributes from the database.
    ......................... USAHOST failed test RidManager
    Starting test: MachineAccount
    ......................... USAHOST passed test MachineAccount
    Starting test: Services
    ......................... USAHOST passed test Services
    Starting test: ObjectsReplicated
    ......................... USAHOST passed test ObjectsReplicated
    Starting test: frssysvol
    There are errors after the SYSVOL has been shared.
    The SYSVOL can prevent the AD from starting.
    ......................... USAHOST passed test frssysvol
    Starting test: kccevent
    ......................... USAHOST passed test kccevent
    Starting test: systemlog
    An Error Event occured. EventID: 0x0000410A
    Time Generated: 05/08/2008 13:25:44
    (Event String could not be retrieved)
    An Error Event occured. EventID: 0x0000410A
    Time Generated: 05/08/2008 13:27:44
    (Event String could not be retrieved)
    An Error Event occured. EventID: 0x0000410A
    Time Generated: 05/08/2008 13:29:44
    (Event String could not be retrieved)
    An Error Event occured. EventID: 0x0000410A
    Time Generated: 05/08/2008 13:39:44
    (Event String could not be retrieved)
    ......................... USAHOST failed test systemlog
    Running enterprise tests on : USA2K.local
    Starting test: Intersite
    ......................... USA2K.local passed test Intersite
    Starting test: FsmoCheck
    Warning: DcGetDcName(GC_SERVER_REQUIRED) call failed, error 1355
    A Global Catalog Server could not be located - All GC's are down.
    Warning: DcGetDcName(PDC_REQUIRED) call failed, error 1355
    A Primary Domain Controller could not be located.
    The server holding the PDC role is down.

  • #2
    "No logonserver found" -and- Replication failures [was: First Post In Forum]

    Welcome USAHOST.

    Can you think of a better title for you question please, so we can change it.


    \Rems


    note:
    New to the forum? Read this BEFORE you post!

    This posting is provided "AS IS" with no warranties, and confers no rights.

    __________________

    ** Remember to give credit where credit's due **
    and leave Reputation Points for meaningful posts

    Comment


    • #3
      Win 2000 network failure - s

      Hi Rems,

      Thanks for your quick response.
      I guess "Win 2000 network failure and dilema on how to proceed." is the best that sums up my sitution.

      I have numerous failures, and i am not sure where it is an active directory failure or a domain controller failure. It actually has both of those plus more i think.

      If you can figure out a better titling, please feel free to retitle,
      regards,

      patrick

      Comment


      • #4
        Re: First Post In Forum

        The failure occurred at 2008-05-08 12:54.46.
        The last success occurred at 2007-06-29 13:46.48.

        Replication has been explicitly disabled through the server options.

        These looks worrying. It seems likely you will need to dcpromo the other server back out and in again as it hasn't replicated for over 60 days.

        What is USA2K ?

        DC=USA2K,DC=local is the Rid Owner, but is deleted.
        cheers
        Andy

        Please read this before you post:


        Quis custodiet ipsos custodes?

        Comment


        • #5
          Re: "No logonserver found" -and- Replication failures [was: First Post In Forum]

          Originally posted by AndyJG247 View Post
          The failure occurred at 2008-05-08 12:54.46.
          The last success occurred at 2007-06-29 13:46.48.

          Replication has been explicitly disabled through the server options.

          These looks worrying. It seems likely you will need to dcpromo the other server back out and in again as it hasn't replicated for over 60 days.
          Before doing dcpromo the other server back in again, read:
          http://forums.petri.com/showthread.php?t=20715

          Does all severs run Windows 2000?
          How many Domain Controllers are there on the network?


          \Rems

          This posting is provided "AS IS" with no warranties, and confers no rights.

          __________________

          ** Remember to give credit where credit's due **
          and leave Reputation Points for meaningful posts

          Comment


          • #6
            Win 2000 network failure - s

            Hi Andy

            Thanks for your reply.

            USA2K is the active directory domain name everyone logs in into.

            USAHOST
            USAHOST2
            USAHOST4

            are the servers.

            I had tried to dcpromo the 1st server (pdc) usahost out and back in.
            It still found no domain controller to service log ins.

            same thing for the other server usahost4
            usahost2 would not allow a dcpromo.

            Given that there is no dc or global catalog am i doomed regardless of any dcpromo move i make?

            Comment


            • #7
              Win 2000 network failure - s

              Rems,

              That article you pointed me to seems very promising.

              All three servers are win 2000.
              Originally USAHOST, and USAHOST4 were DC, nad at some point I promoted USAHOST 2 also to be a DC. They all seem to have lost the ability to function as dc's.

              I know the metadata is all messy and need a clean up.
              When I had tried to do that after connecting to the servers, on the last server i was asked about the availability of a global catalog. it failed at that point.

              If i do a metadata clean up on all servers and then the dc promo won't there have to be a global catalog if I am prompted to identify whether the server being dcpromoted is the LAST one?
              I am asking this because my GC is also missing.

              Starting test: FsmoCheck
              Warning: DcGetDcName(GC_SERVER_REQUIRED) call failed, error 1355
              A Global Catalog Server could not be located - All GC's are down.
              Warning: DcGetDcName(PDC_REQUIRED) call failed, error 1355
              A Primary Domain Controller could not be located.
              The server holding the PDC role is down.





              I am curious as to how the AD will reconstitute after i connected all servers and power on.




              --------------------article you refered to--------------------------
              Rems
              Moderator
              Join Date: Mar 2005

              Location: NL
              Posts: 715
              Reputation: (447)


              Re: Unable to DCPromo Demote AD 2003 Server

              --------------------------------------------------------------------------------

              source: http://www.experts-exchange.com/OS/M..._23018570.html

              Quote:
              Originally Posted by LauraEHunterMVP

              - - - - - -

              From a DC in your domain that is still online (there is no need to, nor would I recommend, powering the DC back on at this point), perform a metadata cleanup of the old DC as follows: http://www.petri.com/delete_failed_dcs_from_ad.htm

              If you wish to re-introduce this DC into your environment, power it up while NOT CONNECTED TO YOUR PRODUCTION NETWORK, and run dcpromo with the /forceremoval switch, after which you can reconnect it to your network and re-run dcpromo as though it is a normal member server that you are promoting for the first time.

              - - - - - -

              Default tombstone lifetime is 60 days; this can be lengthened or shortened, but 60 is the default.
              As the DC has been offline for more than 60 days, the point here is that the OP -cannot- safely turn on that DC again without incurring a USN rollback state within his domain.
              The appropriate steps here are:
              Metadata cleanup/seize any necessary FSMO roles from an existing DC.
              dcpromo /forceremoval on the tombstoned DC -while physically disconnected from the network-.
              Do with the no-longer-tombstoned-DC as you will

              Comment


              • #8
                Re: First Post In Forum

                www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/2003_Server/Q_23018570.html
                quote:
                If you wish to re-introduce this DC into your environment, power it up while NOT CONNECTED TO YOUR PRODUCTION NETWORK, and run dcpromo with the /forceremoval switch, after which you can reconnect it to your network and re-run dcpromo as though it is a normal member server that you are promoting for the first time.

                The appropriate steps here are:
                • Metadata cleanup/seize any necessary FSMO roles from an existing DC.
                • dcpromo /forceremoval on the tombstoned DC -while physically disconnected from the network-.
                • Do with the no-longer-tombstoned-DC as you will
                2.
                <...> I am asking this because my GC is also missing.
                Designate the present DC as a GC then run netdiag /fix


                \Rems
                Last edited by Rems; 9th May 2008, 17:24.

                This posting is provided "AS IS" with no warranties, and confers no rights.

                __________________

                ** Remember to give credit where credit's due **
                and leave Reputation Points for meaningful posts

                Comment


                • #9
                  Win 2000 network failure - s

                  Thanks Rems,

                  I am going to try this and I will let you all know how it went on moday.

                  Comment


                  • #10
                    Re: First Post In Forum

                    Originally posted by Rems View Post
                    2.

                    Designate the present DC as a GC then run netdiag /fix


                    \Rems
                    Rems, us "mere mortals" can't read that link
                    ** Remember to give credit where credit is due and leave reputation points where appropriate **

                    Comment


                    • #11
                      Re: First Post In Forum

                      Originally posted by Wired View Post
                      Rems, us "mere mortals" can't read that link
                      <http://.petri.co.il/forums/>

                      This posting is provided "AS IS" with no warranties, and confers no rights.

                      __________________

                      ** Remember to give credit where credit's due **
                      and leave Reputation Points for meaningful posts

                      Comment

                      Working...
                      X