Announcement

Collapse
No announcement yet.

Functional levels

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

  • Functional levels

    We are currently having an issue with our two AD servers being out of sysnc I would like to know if I raise the functional level from 2000 native to 2003 since that would get rid of the PDC and BDC role and both servers will be equal will that possibly solve the issue and we have several Linux machines that are workstations only and an NT4.0 stand alone web server will raising the function level affect them

  • #2
    Re: Functional levels

    Originally posted by randywhite30 View Post
    We are currently having an issue with our two AD servers being out of sysnc I would like to know if I raise the functional level from 2000 native to 2003 since that would get rid of the PDC and BDC role and both servers will be equal will that possibly solve the issue and we have several Linux machines that are workstations only and an NT4.0 stand alone web server will raising the function level affect them
    No. Fix issues before upgrading.

    Comment


    • #3
      Re: Functional levels

      But the issue is that the BDC is looking for the PDC and its not able to find it I was hoping to upgrade the functional level and that would solve the issue of the BDC would no longer look for the PDC because those roles dont exsist in the 2003 functional level.

      Comment


      • #4
        Re: Functional levels

        Is there a command to make sure the replication is taking place or I guess a better question is how do I make sure things are working correctly

        Comment


        • #5
          Re: Functional levels

          Originally posted by randywhite30 View Post
          But the issue is that the BDC is looking for the PDC and its not able to find it I was hoping to upgrade the functional level and that would solve the issue of the BDC would no longer look for the PDC because those roles dont exsist in the 2003 functional level.
          On a windows 2000 domain there are no more PDC and BDC. All the domain controllers are the same in the sense that they all have a writable AD database. There is however a PDC role (FSMO) assigned to one DC on the domain which performs certain functions.
          Don't confuse the functional levels (Forest and Domain) with the FSMO roles it is like putting a Lighthouse on the motorway!
          If you increase the functional levels you wont be able to use Domain controllers that run on OS not supported. I.e you may not be able to run win 2000 Dc if you increase the Domain Functional level to windows 2003.
          As Garen suggested, try to troubleshoot your existing problems before considering any changes on the functional levels.

          You could start of with Replmon (Google for the correct version)
          Caesar's cipher - 3

          ZKHQ BRX HYHQWXDOOB GHFLSKHU WKLV BRX ZLOO UHDOLVH LW ZDV D ZDVWH RI WLPH!

          SFX JNRS FC U6 MNGR

          Comment


          • #6
            Re: Functional levels

            I ran replmon like you suggested the only error it found was the old NT 4.0 server that is only being used as a stand alone webserver. It did not find any errors or the Domain controllers. This is the error I am getting in event viewer
            Active Directory could not use DNS to resolve the IP address of the source domain controller listed below. To maintain the consistency of Security groups, group policy, users and computers and their passwords, Active Directory successfully replicated using the NetBIOS or fully qualified computer name of the source domain controller.

            Invalid DNS configuration may be affecting other essential operations on member computers, domain controllers or application servers in this Active Directory forest, including logon authentication or access to network resources.

            You should immediately resolve this DNS configuration error so that this domain controller can resolve the IP address of the source domain controller using DNS.

            Alternate server name:
            iiserver01
            Failing DNS host name:
            fee8b032-1508-4de4-8a63-01a0514e7661._msdcs.interact.nonreg

            NOTE: By default, only up to 10 DNS failures are shown for any given 12 hour period, even if more than 10 failures occur. To log all individual failure events, set the following diagnostics registry value to 1:

            Registry Path:
            HKLM\System\CurrentControlSet\Services\NTDS\Diagno stics\22 DS RPC Client

            User Action:

            1) If the source domain controller is no longer functioning or its operating system has been reinstalled with a different computer name or NTDSDSA object GUID, remove the source domain controller's metadata with ntdsutil.exe, using the steps outlined in MSKB article 216498.

            2) Confirm that the source domain controller is running Active directory and is accessible on the network by typing "net view \\<source DC name>" or "ping <source DC name>".

            3) Verify that the source domain controller is using a valid DNS server for DNS services, and that the source domain controller's host record and CNAME record are correctly registered, using the DNS Enhanced version of DCDIAG.EXE available on http://www.microsoft.com/dns

            dcdiag /test:dns

            4) Verify that that this destination domain controller is using a valid DNS server for DNS services, by running the DNS Enhanced version of DCDIAG.EXE command on the console of the destination domain controller, as follows:

            dcdiag /test:dns

            5) For further analysis of DNS error failures see KB 824449:
            http://support.microsoft.com/?kbid=824449

            Additional Data
            Error value:
            11004 The requested name is valid, but no data of the requested type was found.
             
            For more information, see Help and Support Center at

            Comment

            Working...
            X