Hello everyone. Got a head scratcher. New Server 2022 setup. AD, DNS, DHCP all running correctly. Trying to join the domain from a client PC, and i am repeatedly getting this message.

42e5f2bb-3766-40fc-998f-7f49308d34fc-domain.png

I can ping domain.local, i can ping the IP Address of the DC, I can ping the FQDN of the server. I can access shares of the server with \domain.local. But the client will not join the domain. I have all firewalls disabled. My hair is already turning gray. I don’t need anymore help from this. Please someone tell me how stupid i am and help me fix it. Thanks everyone.

9 Spice ups

A few questions:

  • Are all endpoints affected, or only one?

  • Can you use nslookup, specifying the new DNS server, and get predictable output? (e.g. "nslookup hostname DNSServerIPAddress")

- Can you assign a static IP to the endpoint and join it to the domain?

Nslookup works fine. Haven’t tried any other clients, was just testing this setup. And I haven’t tried a static ip

are there any 3rd party DNS servers configured in the TCP settings of this PC? If there are remove them

1 Spice up

No. There aren’t.

Are you using the FQDN when attempting to join and not just the short name?

1 Spice up

I’ve tried both. Short name asks for authentication and then gives the error I submitted. FQDN says dns name doesn’t exist. Although as I said, I can ping everything and access shares

You say AD, DNS, DHCP all running correctly.

How do you KNOW they’re running correctly?

Something isn’t running correctly if you aren’t able to join the domain, have you configured your DHCP scope?

A static IP address is the first thing I would try.

Also try manually entering the IP of your DNS server or servers into the client DNS settings and see if you can connect.

1 Spice up

DNS settings on the client are pointing to the DC and -nothing- else? DNS on the DC is pointing to other DC’s first and 127.0.0.1 last, or 127.0.0.1 if you have a single DC and -nothing- else?

2 Spice ups

Yes, I’ve configured everything. And you’re right. I shouldn’t say it’s working correctly. Obviously something isn’t. Single DC and I’ve configured DNS settings on client to point to the DC. Thanks for you’re help. I appreciate it

Does the DNS Service on the DC list the DC in DNS?

you should have several records and folders with references to your DC

Check where it’s pointing for DNS. It sounds like the short name is resolving by NETBIOS, WINS, Or LLMNR, but not pointing to the DC for DNS. Ensure it’s pointing to the DC for DNS.

Did you try to ping domain controller name like ping dc1 and ping dc1.domain.com ?

Check the host file also if it is having some entries of DC.
It shouldn’t.

Check the event viewer on both Server and client to see if there are any issues.