Announcement

Collapse
No announcement yet.

Identity error in connecting "2" 2003 servers

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

  • Identity error in connecting "2" 2003 servers

    Here's the specs of both machines:
    server1
    IP: 192.168.0.75
    Active directory: primary
    Domain: blade
    machine name: Damn

    server2
    IP:192.168.0.70
    no active directory
    machine name: graphite
    Duel boot with XP Pro

    Both machines ping each other
    No DNS errors on either machine

    When running DCPROMO on server 2 everything is fine until it begins writing (starts) the finishinging touches for AD; I recive this error message:

    "The operation failed because:

    Failed to identify the request replica partner (DAMN) as a valid domain controller with a machine account for (GRAPHITE$).
    This is likely due to either the machine account not being replicated to this domain controller because of replication latency or the domain controller is not advertising the Active Directory. Please consider Retrying the operation with \\damn.blade as the replica partner.

    "The server is unwilling to process the request.""

    I have been retrying this process different ways but I can not seem to get it to work. I could use all the input possible.

    thanx

    Omar Lozano

  • #2
    Re: Identity error in connecting "2" 2003 servers

    Is graphite joined to the domain?
    Regards,
    Jeremy

    Network Consultant/Engineer
    Baltimore - Washington area and beyond
    www.gma-cpa.com

    Comment


    • #3
      Re: Identity error in connecting "2" 2003 servers

      No thats what i am trying to accomplish. it gives me that error message before it could be on the server1 domain. its a real stompper

      Comment


      • #4
        Re: Identity error in connecting "2" 2003 servers

        Running dcpromo and joining the computer to the domain are two different things. But it should work either way IIRC.
        What is the server OS you're using? Have you searched ? If so, what have you tried (so other people don't give you links to stuff you already know about).
        http://www.google.com/search?hl=en&q...eplica+partner
        Regards,
        Jeremy

        Network Consultant/Engineer
        Baltimore - Washington area and beyond
        www.gma-cpa.com

        Comment


        • #5
          Re: Identity error in connecting "2" 2003 servers

          the os for server 1 is: 2003 enterprise edition SP1 R2 x64
          the os for server 2 is: 2003 enterprise edition SP1 x86
          i have tried doing it dcpromo and also using the wizard, but it wont work.
          Last edited by olozano7; 8th November 2006, 00:03.

          Comment


          • #6
            Re: Identity error in connecting "2" 2003 servers

            On Server2, where is the DNS pointing? Itself or Server1?
            1 1 was a racehorse.
            2 2 was 1 2.
            1 1 1 1 race 1 day,
            2 2 1 1 2

            Comment


            • #7
              Re: Identity error in connecting "2" 2003 servers

              Originally posted by olozano7 View Post
              "The operation failed because:

              Failed to identify the request replica partner (DAMN) as a valid domain controller with a machine account for (GRAPHITE$).
              This is likely due to either the machine account not being replicated to this domain controller because of replication latency or the domain controller is not advertising the Active Directory. Please consider Retrying the operation with \\damn.blade as the replica partner.

              "The server is unwilling to process the request.""
              Is this verbatim? My Googling didn't return much.

              I'll throw out some things (which you may have already covered)
              -Run dcdiag on server1 and see if there's any errors
              -Check the event log on both servers.
              -Make sure you have the proper credentials


              Chris, I don't think it's a DNS issue because he gets all the way to copying over the database. If it was DNS I would think it would fail much earlier in the process.... although I've been humbled once already today so maybe I should just keep my trap shut
              Last edited by JeremyW; 8th November 2006, 02:06.
              Regards,
              Jeremy

              Network Consultant/Engineer
              Baltimore - Washington area and beyond
              www.gma-cpa.com

              Comment


              • #8
                Re: Identity error in connecting "2" 2003 servers

                Agreed. There needs to be a Clutching at Straws smiley. But we also don't know how DNS is setup on Server2
                Originally posted by olozano7
                No DNS errors on either machine
                Has DNS been setup on Server2 or is it pointing to DNS on the DC and waiting for DCPROMO to do it's work?
                1 1 was a racehorse.
                2 2 was 1 2.
                1 1 1 1 race 1 day,
                2 2 1 1 2

                Comment


                • #9
                  Re: Identity error in connecting "2" 2003 servers

                  Im no expert with setting up domians, only done it 3 times, but I had this error once.

                  Is GRAPHITE actually a member of the Domian BLADE? ie have you joined it to the domain before running DCPROMO?

                  That was my problem, forgot to do that . Soon as I did that it worked fine.
                  Last edited by swfblade; 8th November 2006, 11:32.
                  James
                  MCP

                  Comment


                  • #10
                    Re: Identity error in connecting "2" 2003 servers

                    For the DNS on server2; it is using the DNS from server1.
                    for the domain question: at first its not, but when the process starts, then ends with the error message it is joined to the domain, but not as part of the AD, just as a computer.

                    Comment


                    • #11
                      Re: Identity error in connecting "2" 2003 servers

                      Originally posted by olozano7 View Post
                      For the DNS on server2; it is using the DNS from server1.
                      for the domain question: at first its not, but when the process starts, then ends with the error message it is joined to the domain, but not as part of the AD, just as a computer.
                      Sorry but I'm having trouble trying to decipher what you wrote. Are you saying that when you run dcpromo on server2 you get to the part where it starts to copy over everything but you then get an error that says it's not a Domain Controller but it is a member server????

                      Could you post any and all errors verbatim?

                      Also, it seems we use terms differently:
                      Active Directory
                      Domain Controller
                      Regards,
                      Jeremy

                      Network Consultant/Engineer
                      Baltimore - Washington area and beyond
                      www.gma-cpa.com

                      Comment


                      • #12
                        Re: Identity error in connecting "2" 2003 servers

                        Yeah, I'm slightly confuzzeld by that response as well.

                        Surely you want to add it as a computer on the Domain prior to running DCPROMO? Or am I missing something here?
                        James
                        MCP

                        Comment

                        Working...
                        X