0

I have a local network consisting of 2 computers. The network configuration is as in the below picture.

enter image description here

On DC01 I installed Windows Server 2012 R2. On Laptop01 I have windows 8 enterprise. I have turned on "AD DS" and "DNS" roles on the server (DC01).

IP configuration of the network:

ADSL:     192.168.1.1

DC01:     192.168.1.10 Preferred DNS: 127.0.0.1

Laptop01: 192.168.1.11 Preferred DNS: 192.168.1.10

I created a domain mib.com. Here is result of pinging it from Laptop01.

enter image description here

Now I am trying to join Laptop01 to this domain but getting an error

enter image description here

What am I doing wrong?


Update

Result of DCDIAG

enter image description here


Update 2

DNS manager screenshot

enter image description here

  • So you installed the AD DS and DNS roles on DC01 and created an AD domain named mib.com? Have you verified that the relevant SRV records are registered in the DNS zone for mib.com? – joeqwerty Mar 19 '18 at 15:29
  • DC01 should use 192.168.1.10 for primary DNS and 127.0.0.1 for secondary DNS. – joeqwerty Mar 19 '18 at 15:34
  • Run the AD DS and DNS Best Practice Analyzer's on DC01. Run DCDIAG on DC01. – joeqwerty Mar 19 '18 at 15:34
  • @joeqwerty DC01 should use 192.168.1.10 for primary DNS and 127.0.0.1 for secondary DNS. -> didn't work – Bahrom Mar 19 '18 at 16:02
  • @joeqwerty, Please see the update regarding DCDIAG – Bahrom Mar 19 '18 at 16:03
0

Thanks for the pictures. Makes this much easier to troubleshoot. Your domain is "MIB.com" - NOT "MIB"

Put that in the Computer Name/Domain Changes window,

try that again, and let me know.

  • Getting Error: An Active Directory Domain Controller (AD DC) for the domain "MIB.com" could not be contacted. Ensure that the domain name is typed correctly. – Bahrom Mar 19 '18 at 13:59
  • You can join a domain using either the NetBIOS name of the domain or the FQDN. See my answer here for how name resolution during the domain join process works. - serverfault.com/questions/717689/… – joeqwerty Mar 19 '18 at 15:31
0

Your DC is resolving to an IPv6 address for some reason. Since that address is not working for DCDIAG, it's not going to work for clients either.

Unbind IPv6 from your network adapter(s) on the DC. Double-check the IPv4 address to ensure it is correct. Restart the NETLOGON service, then restart the DNS service.

After that, either clear the DNS cache on the client or reboot it. Try to join the domain again.

  • I disabled Internet Protocol Version 6 (TCP/IPv6) on both DC01 and Laptop01 long before creating Active Directory domain – Bahrom Mar 19 '18 at 16:46
  • That's not an IPv6 record. It's the DsaCname Record for the DC for non-SRV aware clients. There's one DsaCname Record for each DC. DO NOT DISABLE IPv6! – joeqwerty Mar 19 '18 at 17:03
  • @joeqwerty, Enabling IPv6 didn't help. – Bahrom Mar 19 '18 at 18:01
  • Looks like problem is in DNS zone configuration, – Bahrom Mar 19 '18 at 18:04
  • Right. I didn't say it was going to fix the problem. I only meant that you should not disable it. – joeqwerty Mar 19 '18 at 18:05

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.