Announcement

Collapse
No announcement yet.

Active Directory can't connect(W2k Server)

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

  • Active Directory can't connect(W2k Server)

    when opening the active directory user and computer, I got this error
    Naming information cannot be located because:
    The specified domain either does not exist or could not be contacted
    Also our DNS got corrupted or something, some of the forward lookup zones was gone, too bad i don't have any back up.


    this happens when we uninstalled our Anti Virus,

    TY for any info about, it,

    Ps: if I installed active directory back would it recover our old data, the Users and etc.

  • #2
    DNS server are up and running?
    Your are open that console from Domain Controller server?
    (I know you do not need to open from there but try it first)
    You have the Domain Controller Online? FSMO roles are up on the respective DC servers?

    Imagine this case:
    You have oone domain with two dc's
    If you demote one DC with the 5 FSMO roles and you have another one, you will get that message in few days because you have not longer the FSMO roles online. Then you will need to seize the roles for the dc that are running.

    It is that your problem?
    MCSE w2k
    MCSA w2k - MCSA w2k MESSAGING
    MCDBA SQL2k

    Comment


    • #3
      sorry i'm really newbie about this, but not sure about that what your talking, but currently our active directory is not working and I'm left alone here to fix it, the people setup is not here anymore , so its me gonna fixed it.

      The DNS is up and running and i think is okay, I was able to to open it in DNS manager,its in in administrative tools->DNS

      now I did check the "Installing Active Directory" in AD tricks and seems some missing in the DNS in the Forward Lookup Zones, as i said before the DNS was corrupted so I have to add back some sites, but i think there was still missing, and maybe this is the cause why AD didn't connect?

      if this helps, this is my current server config.
      Computer fullname: subname.companyname.com
      Domain : companyname.com

      and in the DNS forward lookup zone, their was no subname.companyname.com so i think that's the reason why AD didnt' connect?

      i did try to add subname.companyname.com but i think I still to add the _msdcs _sites _tcp _udp, if so then is their anyway I can put it, or maybe I just missed it.

      Thanks

      Comment


      • #4
        Can you tell me how many domain controller do you have?
        Windows 2003 or windows 2000?
        DNS server is on the domain controller or is another server?


        See this article to find how have the FSMO roles:

        http://www.petri.com/determining_fsmo_role_holders.htm

        MCSE w2k
        MCSA w2k - MCSA w2k MESSAGING
        MCDBA SQL2k

        Comment


        • #5
          There is 3 computer standing here, two is windows and the other is linux,
          and the other one, dont have any DNS ,

          The DNS Server is on the same Computer with the Active Directory or the Domain Controller(dunno if correct way of saying)

          I check also the folder

          winnt/SYSVOL/sysvol and I have a folder called "company.com"


          ok, i'll be checking that FSMO roles,

          Thanks

          Comment


          • #6
            --sorry double posted-

            Comment


            • #7
              Go to the domain controller, open the dns console.
              Can you see all the zones?
              Open the Users and Computers.
              Can you see anything?

              What computer have that roles? did you find it?
              If you not find then you need to seize one of the two domain controllers.
              What system? Windows 2003?

              Answer all the questions please.
              MCSE w2k
              MCSA w2k - MCSA w2k MESSAGING
              MCDBA SQL2k

              Comment


              • #8
                what do you mean by

                Go to the domain controller, open the dns console

                is that in programs->Administrative tools->DNS ?

                i didnt see any domain controller, this might be the problem?

                The methods in determining the current FSMO requires to open the Active Directory Users and Computers and others, which by now is not working and having an error on my first post.

                The other one also gives me an error that could not connect to schema master...



                What computer have that roles? did you find it?
                If you not find then you need to seize one of the two domain controllers.
                What system? Windows 2003?
                How do you can I see i have two domain controllers? (confused)
                Their is only windows 2000 here, and the other is a plain server, so DNS and domain controller is on 1 machine.

                Sorry about the FSMO roles, I can't seem to get anything work in the determining the FSMO roles

                Edit: Just now I did an install of a server on a test machine, and I did install a Domain Controller and seems its okay, even the DNS is not configured... Maybe my Domain Controller is gone, or corrupted,

                maybe installing again the Active Directory would be a good idea?

                Comment


                • #9
                  Sorry rpadilla did mean too...


                  Let start from begining.

                  Find if you have one domain controller:

                  In one server

                  Go to start menu / run / type CMD

                  type nslookup

                  Can you see the name and ip address?


                  Find the FSMO Rules:

                  Go to the server that you have find and then see the Method #3: Use the Ntdsutil command from this link:

                  http://www.petri.com/determining_fsmo_role_holders.htm


                  You said to install active directory. Can you do that?
                  MCSE w2k
                  MCSA w2k - MCSA w2k MESSAGING
                  MCDBA SQL2k

                  Comment


                  • #10
                    sorry for replying just now, i think its time for a little break

                    using NSLOOKUP

                    server 1 i see the name and the ip address (which is, its own IP)

                    server 2 i see the name and the ip address, which is from server 1


                    Using Method 3, by ntdsutil

                    I get this error when connecting to the server 1(I get the name from the NSLOOKUP)



                    Code:
                    DsBindW error 0x6d9(There are no more endpoints available from the endpoint mapper)
                    EDIT: If have to re Install back Active Server then i think i should do it, but there is other way, then would be better.

                    Thanks

                    Comment


                    • #11
                      Soo i htink your server1 is your DOmain Controller.

                      The same old question :

                      Can you go to administrative tools and open sucessfully the users and computers console?
                      Can you go to administrative tools and open sucessfully the DNS console?

                      If not:

                      size the FSMO roles:

                      se here:

                      http://support.microsoft.com/kb/255504/en-us

                      after that try to open the dns and user & computer console.
                      MCSE w2k
                      MCSA w2k - MCSA w2k MESSAGING
                      MCDBA SQL2k

                      Comment


                      • #12
                        users and computers console wont open and has an error, like from my first post


                        The DNS console will Open and No error.


                        Only one is NO so should i seize FSMO roles to a domain controller?


                        but im on to that link.. thanks.

                        Edit:
                        I can't help but did try seizing FSMO, which need to use ndsUtil but when connecting to the server, i got an error

                        There are no more endpoints available from the endpoint mapper.
                        and i search and got this
                        http://support.microsoft.com/?id=839...25120121120120

                        Comment


                        • #13
                          Originally posted by rpadilla
                          users and computers console wont open and has an error, like from my first post


                          The DNS console will Open and No error.


                          Only one is NO so should i seize FSMO roles to a domain controller?


                          but im on to that link.. thanks.
                          One last question before you do that.
                          Do you know if some computer was re installed or removed from the network? after that happens! (Server computer)
                          MCSE w2k
                          MCSA w2k - MCSA w2k MESSAGING
                          MCDBA SQL2k

                          Comment


                          • #14
                            I think nothing was re- installed or remove no one will do it anyway.

                            ok i was just testing the sezing FSMO but got this before the seizing


                            DsBindW error( 0x6d9)There are no more endpoints available from the endpoint mapper.


                            and i search and got this
                            http://support.microsoft.com/?id=839...25120121120120

                            not sure if that link is the one(related to the error)

                            Comment


                            • #15
                              This is the right article:

                              http://support.microsoft.com/default...b;en-us;331953

                              Can you resolve it?

                              Another thing:

                              - Install anti virus and firewall.
                              - Change the admin password and rename it (you should first check what kind of services could be active on that account).
                              MCSE w2k
                              MCSA w2k - MCSA w2k MESSAGING
                              MCDBA SQL2k

                              Comment

                              Working...
                              X