Announcement

Collapse
No announcement yet.

Error not able to loging after upgrading domain controller

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

  • Error not able to loging after upgrading domain controller

    Hi
     
    I tried upgrading my windows 2000 domain controller (with sp4) to windows 2003 (with sp2) domain controller.I have single domain controller in my organisation.I have made my windows 2003 as additonal domain controller and tried moving the fsmo roles via ntdsutil tool. i got succes, After shutting down my old windows 2000 server i tried login from test server and pc's i was not able to login.I get a error message no domain server found.if i start my old 2000 server all my pc are able to login.
    I am ataching the error log which i genrated from both the server (win 2000 & 2003) via dcdiag tool.Need help to resolve this problem




    WINDOWS 2003 SERVER Error
     
    C:\Documents and Settings\Administrator.ABMAURI>dcdiag
    Domain Controller Diagnosis
    Performing initial setup:
    Done gathering initial info.
    Doing initial required tests
    Testing server: Default-First-Site-Name\DATASERVER
    Starting test: Connectivity
    The host 8915e3e5-0e71-4c9f-a92a-6b3c1a2f9781._msdcs.abmauri.int could
    not be resolved to an
    IP address. Check the DNS server, DHCP, server name, etc
    Although the Guid DNS name
    (8915e3e5-0e71-4c9f-a92a-6b3c1a2f9781._msdcs.abmauri.int) couldn't be
    resolved, the server name (dataserver.abmauri.int) resolved to the IP
    address (192.168.0.11) and was pingable. Check that the IP address is
    registered correctly with the DNS server.
    ......................... DATASERVER failed test Connectivity
    Doing primary tests
    Testing server: Default-First-Site-Name\DATASERVER
    Skipping all tests, because server DATASERVER is
    not responding to directory service requests
    Running partition tests on : ForestDnsZones
    Starting test: CrossRefValidation
    ......................... ForestDnsZones passed test CrossRefValidation
    Starting test: CheckSDRefDom
    ......................... ForestDnsZones passed test CheckSDRefDom
    Running partition tests on : DomainDnsZones
    Starting test: CrossRefValidation
    ......................... DomainDnsZones passed test CrossRefValidation
    Starting test: CheckSDRefDom
    ......................... DomainDnsZones passed test CheckSDRefDom
    Running partition tests on : Schema
    Starting test: CrossRefValidation
    ......................... Schema passed test CrossRefValidation
    Starting test: CheckSDRefDom
    ......................... Schema passed test CheckSDRefDom
    Running partition tests on : Configuration
    Starting test: CrossRefValidation
    ......................... Configuration passed test CrossRefValidation
    Starting test: CheckSDRefDom
    ......................... Configuration passed test CheckSDRefDom
    Running partition tests on : abmauri
    Starting test: CrossRefValidation
    ......................... abmauri passed test CrossRefValidation
    Starting test: CheckSDRefDom
    ......................... abmauri passed test CheckSDRefDom
    Running enterprise tests on : abmauri.int
    Starting test: Intersite
    ......................... abmauri.int 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(TIME_SERVER) call failed, error 1355
    A Time Server could not be located.
    The server holding the PDC role is down.
    Warning: DcGetDcName(KDC_REQUIRED) call failed, error 1355
    A KDC could not be located - All the KDCs are down.
    ......................... abmauri.int failed test FsmoCheck
    C:\Documents and Settings\Administrator.ABMAURI>
    C:\Documents and Settings\Administrator.ABMAURI>
    ================================================== ================================================== ====
     
    WINDOWS 2000 SERVER Error
     
     
    C:\Program Files\Support Tools>dcdiag
    DC Diagnosis
    Performing initial setup:
    Done gathering initial info.
    Doing initial non skippeable tests
    Testing server: Default-First-Site-Name\MAINSERVER
    Starting test: Connectivity
    MAINSERVER's server GUID DNS name could not be resolved to an
    IP address. Check the DNS server, DHCP, server name, etc
    Although the Guid DNS name
    (f6395252-5abc-4524-bd9f-5c8688aabfda._msdcs.abmauri.int) couldn't be
    resolved, the server name (mainserver.abmauri.int) resolved to the IP
    address (192.168.0.5) and was pingable. Check that the IP address is
    registered correctly with the DNS server.
    ......................... MAINSERVER failed test Connectivity
    Doing primary tests
    Testing server: Default-First-Site-Name\MAINSERVER
    Skipping all tests, because server MAINSERVER is
    not responding to directory service requests
    Running enterprise tests on : abmauri.int
    Starting test: Intersite
    ......................... abmauri.int passed test Intersite
    Starting test: FsmoCheck
    Error: The server returned by DsGetDcName() did not match DsListRoles()
    for the PDC
    ......................... abmauri.int passed test FsmoCheck
    C:\Program Files\Support Tools>

    Regards
    Alexyy

  • #2
    Re: Error not able to loging after upgrading domain controller

    Did you set your client machines to use the new DC for DNS? Do you have DNS installed on the new DC? Is your DNS AD integrated?

    Comment


    • #3
      Re: Error not able to loging after upgrading domain controller

      All my my test pc i have pointed to new dc and dns intergrated

      Comment


      • #4
        Re: Error not able to loging after upgrading domain controller

        Is the new DC pointing to itself for DNS?

        Comment


        • #5
          Re: Error not able to loging after upgrading domain controller

          yea and if i try nslookup in dc it get resolve and in pc to dns get resolve

          Comment


          • #6
            Re: Error not able to loging after upgrading domain controller

            Make sure the new server is a GC. Verify the DNS settings on all DC's. Reboot all DC's and try again to login from a client machine.

            Comment


            • #7
              Re: Error not able to loging after upgrading domain controller

              tried the option told by u, still same problem persist,resarted all the servers still same problem persist. even when i try replication i get error Rpc server not found

              Comment


              • #8
                Re: Error not able to loging after upgrading domain controller

                Maybe it's time to start over. Bring the W2K server back online and transfer the FSMO roles back to it. Run dcpromo on the new server to demote it. Point all the clients DNS back to the W2K server. Try running dcpromo on the new server again.

                Comment


                • #9
                  Re: Error not able to loging after upgrading domain controller

                  when i try to restore back i get error message fsmo roles cant be moved, but my pc iam able to login via old server

                  Comment

                  Working...
                  X