Announcement

Collapse
No announcement yet.

Problem in Joining Machines to windows 2008 domain

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

  • Problem in Joining Machines to windows 2008 domain

    facing a problem in joining machine to windows 2008 domain.

    having a single forest single domain architecture...

    Am able to join machine to the domain which are in same subnet as of my domain controller. When Am trying to add any other machine which is connected to different subnet its throwing an error.

    " Active Directory domain Controller for Domain gcb could not be contacted.
    The domain name gcb might be a NetBIOS domain name. If this is the case, verify that the domain name is properly registered with WINS.
    If you are certain that the name is not a NetBIOS domain name, then the following information can help you troubleshoot your DNS configuration.
    DNS was successfully queried for the service location (SRV) resource record used to locate an Active Directory Domain Controller for domain gcb:
    The query was for the SRV record for _ldap._tcp.dc._msdcs.gcb
    The following AD DCs were identified by the query:
    parrot.gcb
    Common causes of this error include:
    - Host (A) records that map the name of the AD DCs to its IP addresses are missing or contain incorrect addresses.
    - Active Directory Domain Controllers registered in DNS are not connected to the network or are not running.
    For information about correcting this problem, click Help. "

    Please note: there is no port blocking rule in place between the subnets which contain DC and subnet from which we are joining machine to domain.

  • #2
    Re: Problem in Joining Machines to windows 2008 domain

    Is there a route between the subnets? (can you ping the DC by FQDN?)
    Are they in the same site?
    Tom Jones
    MCT, MCSE (2000:Security & 2003), MCSA:Security & Messaging, MCDBA, MCDST, MCITP(EA, EMA, SA, EDA, ES, CS), MCTS, MCP, Sec+
    PhD, MSc, FIAP, MIITT
    IT Trainer / Consultant
    Ossian Ltd
    Scotland

    ** Remember to give credit where credit is due and leave reputation points where appropriate **

    Comment


    • #3
      Re: Problem in Joining Machines to windows 2008 domain

      Have you configured sites and subnets in AD Sites and Services?

      Comment


      • #4
        Re: Problem in Joining Machines to windows 2008 domain

        ossian,

        no they are in different subnets..

        and there is no route in place. machine can ping the Domain Controllers.and do telnet to LDAP and DNS ports.


        Virtual,

        we have only one site and it is a default site with proper subnets added to it.
        also we have 2 DC in same site with proper replication metholgy.

        Comment


        • #5
          Re: Problem in Joining Machines to windows 2008 domain

          Can you use

          pathping FQDN

          pathping IP

          tracert FQDN

          tracert IP

          And post the results.

          Comment


          • #6
            Re: Problem in Joining Machines to windows 2008 domain

            C:\Users\Administrator>tracert -d 192.168.138.213
            Tracing route to 192.168.138.213 over a maximum of 30 hops
            1 <1 ms <1 ms <1 ms 192.168.140.254
            2 <1 ms <1 ms <1 ms 192.168.138.213
            Trace complete.
            C:\Users\Administrator>pathping 192.168.138.213
            Tracing route to parrot.gcb [192.168.138.213]
            over a maximum of 30 hops:
            0 No resources.
            C:\Users\Administrator>pathping parrot.gcb
            Tracing route to parrot.gcb [192.168.138.213]
            over a maximum of 30 hops:
            0 No resources.
            C:\Users\Administrator>tracert parrot.gcb
            Tracing route to parrot.gcb [192.168.138.213]
            over a maximum of 30 hops:
            1 <1 ms <1 ms <1 ms 192.168.140.254
            2 <1 ms <1 ms <1 ms parrot.gcb [192.168.138.213]
            Trace complete.

            My domain Name is GCB

            Comment


            • #7
              Re: Problem in Joining Machines to windows 2008 domain

              Have the PCs ever been on another domain?
              Last edited by Virtual; 27th May 2009, 18:12. Reason: Comment changed

              Comment


              • #8
                Re: Problem in Joining Machines to windows 2008 domain

                yes,

                the machine from which above details where given is currently on different domain.

                Also adding below the results taken from a machine in a workgroup.(Standalone machine).

                C:\Documents and Settings\Administrator>pathping 192.168.138.213

                Tracing route to parrot.gcb [192.168.138.213]
                over a maximum of 30 hops:
                0 project-3 [192.168.140.90]
                1 192.168.140.254
                2 parrot.gcb [192.168.138.213]

                Computing statistics for 50 seconds...
                Source to Here This Node/Link
                Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
                0 project-3 [192.168.140.90]
                0/ 100 = 0% |
                1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.140.254
                0/ 100 = 0% |
                2 0ms 0/ 100 = 0% 0/ 100 = 0% parrot.gcb [192.168.138.213]

                Trace complete.

                C:\Documents and Settings\Administrator>tracert parrot.gcb

                Tracing route to parrot.gcb [192.168.138.213]
                over a maximum of 30 hops:

                1 <1 ms <1 ms <1 ms 192.168.140.254
                2 <1 ms <1 ms <1 ms parrot.gcb [192.168.138.213]

                Trace complete.

                C:\Documents and Settings\Administrator>pathping parrot.gcb

                Tracing route to parrot.gcb [192.168.138.213]
                over a maximum of 30 hops:
                0 project-3 [192.168.140.90]
                1 192.168.140.254
                2 parrot.gcb [192.168.138.213]

                Computing statistics for 50 seconds...
                Source to Here This Node/Link
                Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
                0 project-3 [192.168.140.90]
                0/ 100 = 0% |
                1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.140.254
                0/ 100 = 0% |
                2 0ms 0/ 100 = 0% 0/ 100 = 0% parrot.gcb [192.168.138.213]

                Trace complete.

                C:\Documents and Settings\Administrator>tracert parrot.gcb

                Tracing route to parrot.gcb [192.168.138.213]
                over a maximum of 30 hops:

                1 <1 ms <1 ms <1 ms 192.168.140.254
                2 <1 ms <1 ms <1 ms parrot.gcb [192.168.138.213]

                Trace completed.

                Please let me know if more info is needed

                Comment

                Working...
                X