0

Just a query - we have an on-prem Windows 2012R2 server running AD with 'domain.local'. I've always added the computers to the domain using 'domain.local', however my assistant tells me that he's always added them using just 'domain' until today when it didn't work, but using 'domain.local' did.

Why would adding them as 'domain' work at all?

Thanks

NightM0de
  • 1
  • See my answer here - https://serverfault.com/questions/717689/cannot-join-client-to-domain-non-virtual-dns-issue/717914#717914 – joeqwerty Jan 27 '23 at 15:31
  • @joeqwerty Thanks for the response. That makes sense as to why it works without the DNS suffix, but turning that on it's head then, what would be the possible reason for it not working without the DNS suffix as we found today? – NightM0de Jan 27 '23 at 15:49
  • Without a DNS suffix, the client will use a NetBIOS broadcast to locate a Domain Controller. So my guess is the client is not getting a reply to the NetBIOS broadcast. Is this client remote by any chance and connected to the corporate network via a VPN? Is the client on a different routed network from the Domain Controller? – joeqwerty Jan 27 '23 at 16:41
  • No, client is on prem, wired single network. – NightM0de Jan 27 '23 at 16:57

0 Answers0