Announcement

Collapse
No announcement yet.

Having Problems joining a Domain!

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

  • Having Problems joining a Domain!

    I have specified the Computer and created a User for a workstation I have....When I try to join the Domain It prompts for the credentials I add the ones that I created in AV in the users section... After that a window comes up saying windows cannot find this computer in the XCLUSIVETECH Domain. Help please I am new to this and learning. This is my first encounter with a Server OS.

  • #2
    Re: Having Problems joining a Domain!

    Is the problem adding a server to the domain or adding a client?

    Either way, you will need to provide domain credentials (XCLUSIVETECH\Administrator)

    Before you do that, check you can ping the DC by NetBIOS and FQDN
    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: Having Problems joining a Domain!

      I trying to add a client to my DC.

      Windows IP Configuration

      Host Name . . . . . . . . . . . . : XT-MAINSERVER (CAN BE PINGED)
      Primary Dns Suffix . . . . . . . : xclusivetech.net (CANNOT BE PINGED)
      Node Type . . . . . . . . . . . . : Hybrid
      IP Routing Enabled. . . . . . . . : No
      WINS Proxy Enabled. . . . . . . . : No
      DNS Suffix Search List. . . . . . : xclusivetech.net

      Comment


      • #4
        Re: Having Problems joining a Domain!

        @10-fah

        are you the one who install your domain? is your domain working properly?

        try running this command on your client and post the result

        ipconfig /all

        what is the local IP of your DC?

        Comment


        • #5
          Re: Having Problems joining a Domain!

          Yea I just did run DCPORMO followed the steps and choosed a name that I liked.

          Windows IP Configuration

          Host Name . . . . . . . . . . . . : XT-MC1
          Primary Dns Suffix . . . . . . . :
          Node Type . . . . . . . . . . . . : Hybrid
          IP Routing Enabled. . . . . . . . : No
          WINS Proxy Enabled. . . . . . . . : No

          Wireless LAN adapter Wireless Network Connection:

          Connection-specific DNS Suffix . :
          Description . . . . . . . . . . . : Intel(R) PRO/Wireless 3945ABG Network Con
          nection
          Physical Address. . . . . . . . . : 00-1C-BF-14-21-D4
          DHCP Enabled. . . . . . . . . . . : No
          Autoconfiguration Enabled . . . . : Yes
          Link-local IPv6 Address . . . . . : fe80::edd3:67fe:886e:d115%12(Preferred)
          IPv4 Address. . . . . . . . . . . : 192.168.1.210(Preferred)
          Subnet Mask . . . . . . . . . . . : 255.255.255.0
          IPv4 Address. . . . . . . . . . . : 192.168.2.210(Preferred)
          Subnet Mask . . . . . . . . . . . : 255.255.255.0
          IPv4 Address. . . . . . . . . . . : 192.168.3.210(Preferred)
          Subnet Mask . . . . . . . . . . . : 255.255.255.0
          Default Gateway . . . . . . . . . : 192.168.1.1
          DHCPv6 IAID . . . . . . . . . . . : 218111167
          DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-13-6A-92-42-00-A0-D1-87-0A-C4


          NetBIOS over Tcpip. . . . . . . . : Enabled




          MY DC Local ip is 192.168.1.200

          Comment


          • #6
            Re: Having Problems joining a Domain!

            I've notice that the primary dns was not configured.
            Please add primary dns pointing to DC ip (assuming AD/DNS integrated) to your NIC.

            then try this command (for verification)
            • Ipconfig /flushdns
            • ipconfig /registerdns
            • nslookup %usernamedomain%
            If ad/dns was properly configured you will recieve a message like this:
            Server: your dc (fqdn)
            IP: your dc's IP

            Name: your domain/namespace (eg. TEST.COM)
            Address: your dc's IP

            Comment


            • #7
              Re: Having Problems joining a Domain!

              Ok I added Ip 192.168.1.200 to the DNS performed the actiond

              Ipconfig /flushdns
              ipconfig /registerdns

              Then tried (nslookup %usernamedomain%) and got...

              C:\Windows\system32>nslookup %usernamedomain%
              Server: UnKnown
              Address: 192.168.1.200

              Comment


              • #8
                Re: Having Problems joining a Domain!

                Is your DC also a DNS server?
                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


                • #9
                  Re: Having Problems joining a Domain!

                  I want it to be.


                  When I type nslookup on the server I get

                  1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0. 0.0.0.0.0.0.0.ip6.arpa
                  primary name server = 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.
                  0.0.0.0.0.0.0.ip6.arpa
                  responsible mail addr = (root)
                  serial = 0
                  refresh = 28800 (8 hours)
                  retry = 7200 (2 hours)
                  expire = 604800 (7 days)
                  default TTL = 86400 (1 day)
                  Default Server: UnKnown
                  Address: ::1

                  >

                  Comment


                  • #10
                    Re: Having Problems joining a Domain!

                    Hi there,
                    Is this a test lab that you are learning on? If so can you do an ipconfig /all on your domain controller and on the client that you are trying to add to the domain?
                    I notice that you have quite a few ip address configured on the client network interface card, why?
                    By what is written in your post you have promoted a domain controller for a new forest and this will have dns installed by default. Dns is a core component for active directory.
                    Before you can join a domain and perform name resolution you need to verify network connectivity. How are the domain controller and server/client physically connected? are they connected to the same switch?
                    You can verify network connectivity by a ping test the DC/DNS server.
                    Example: ping 192.168.1.200
                    If you can ping the DC/DNS and the configuration is like below then you should be prompted for domain credentials
                    Enter credentials specify a prefix example: xclusivetech.net\administrator and the correct password for the account.
                    Domain Controller example:
                    Ip address 192.168.1.200
                    Subnet mask 255.255.255.0
                    Default gateway 192.168.1.1
                    Primary DNS 192.168.1.200 (DNS Server/DC)
                    Seconday DNS would point to another DNS Server/DC preferable in the same site but not required

                    Example of client/Server configuration:
                    IP address 192.168.1.210
                    Subnet mask 255.255.255.0
                    Default gateway 192.168.1.1
                    Primary DNS 192.168.1.200 (DNS Server/DC)
                    Seconday DNS would point to another DNS Server/DC preferable in the same site but not required
                    If your configuration is not correct and you had to change something on the domain controller then you will need to restart the netlogon service and probably worth restarting the dns service.
                    This will re register the srv records (used to locate the domain controller) and NS records pointers to the dns servers.
                    If this is a test system then just restart the DC/DNS server. Again this is only if you made ip configuration changes to the domain controller.

                    Regards,

                    Jamie

                    Comment

                    Working...
                    X