Announcement

Collapse
No announcement yet.

DCDiag Error with PDC FMSO role

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

  • DCDiag Error with PDC FMSO role

    I am getting the following error and competely lost as to how to fix it. I have tried to move the role to another DC still with no luck. I have gone through google all day and have not been able to resolve this issue. Nobody can log in the network because the PDC cannot be found. Does anyone have any suggestions how I should proceed with this?

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

    Running enterprise tests on : infomap.lan
    Starting test: Intersite
    ......................... infomap.lan passed test Intersite
    Starting test: FsmoCheck
    Warning: DcGetDcName(PDC_REQUIRED) call failed, error 1355
    A Primary Domain Controller could not be located.
    The server holding the PDC role is down.
    ......................... infomap.lan failed test FsmoCheck

    P.S. - I am on the DC with the PDC.

  • #2
    Re: DCDiag Error with PDC FMSO role

    Have you made changes recently? What AD version are you at? What DC OS? Does the PDC FSMO role holder have other roles other than AD? DNS, DHCP etc?

    Comment


    • #3
      Re: DCDiag Error with PDC FMSO role

      Have you made changes recently? - No changes have been made
      What AD version are you at? - 44
      What DC OS? - Server 2003 R2 SP2
      Does the PDC FSMO role holder have other roles other than AD? DNS, DHCP etc? - Yes, DHCP and DNS

      Comment


      • #4
        Re: DCDiag Error with PDC FMSO role

        On the DC, run the following command to see where your PDC role should be;
        Code:
        netdom query /domain:<domain> fsmo
        Marcel
        Technical Consultant
        Netherlands
        http://www.phetios.com
        http://blog.nessus.nl

        MCITP(EA, SA), MCSA/E 2003:Security, CCNA, SNAF, DCUCI, CCSA/E/E+ (R60), VCP4/5, NCDA, NCIE - SAN, NCIE - BR, EMCPE
        "No matter how secure, there is always the human factor."

        "Enjoy life today, tomorrow may never come."
        "If you're going through hell, keep going. ~Winston Churchill"

        Comment


        • #5
          Re: DCDiag Error with PDC FMSO role

          use ntdsutil to find out where the fsmo roles are MEANT to be
          then see if that device is still there

          if not, seize the roles.. ?
          Please do show your appreciation to those who assist you by leaving Rep Point https://www.petri.com/forums/core/im.../icon_beer.gif

          Comment


          • #6
            Re: DCDiag Error with PDC FMSO role

            When I run the code it shows the PDC as the correct DC. I have tried to seize the role to the other DC on the network and it does a clean transfer because they are both available.

            Comment


            • #7
              Re: DCDiag Error with PDC FMSO role

              I was able to repair the issue with the following commands. Thanks for all the help


              The secure channel was corrupted between the Domain and the Domain controller. Reset the secure channel with

              1) The following command in command prompt

              Netdom resetpwd /server:172.16.1.31 /userd:INFOMAP.LAN\infranet /passwordd:*

              2) After hitting enter this will require user password

              Type the password associated with the domain user:

              3) After hitting enter you will see the following if successful

              The machine account password for the local machine has been successfully reset.
              The command completed successfully

              4) Type the following command to reset services

              net stop dns & net stop netlogon & ipconfig /flushdns & net start dns & net start netlogon & ipconfig /register dns

              5) You will see the following commands

              The DNS Server service is stopping.
              The DNS Server service was stopped successfully.

              The Net Logon service is stopping.
              The Net Logon service was stopped successfully.

              Windows IP Configuration

              Successfully flushed the DNS Resolver Cache.
              The DNS Server service is starting.
              The DNS Server service was started successfully.

              The Net Logon service is starting.
              The Net Logon service was started successfully.

              Windows IP Configuration

              Registration of the DNS resource records for all adapters of this computer has been
              initiated. Any errors will be reported in the Event Viewer in 15 minutes...

              6) Type the following command to verify the domain can see the PDC

              netdom query pdc

              7) You will see the following commands listing the current PDC

              Primary domain controller for the domain:

              IMAP1
              The command completed successfully.

              DCDiag /test:FSMOcheck will pass

              Comment

              Working...
              X