DC strange issue with DNS/DHCP

Question

Hi all,

I have the weirdest issue with a single DC/DNS/DHCP server. Windows 2016 Essentials.

Once every few weeks a workstation can't connect to this server. I've narrowed it down to a DNS/DHCP issue.

The workstation shows a "domain.local unverified 2" network icon. Whatever you try, the workstation can't reconnect to the server.

The only thing that works is to change the MAC of the workstation's NIC. By doing so it immediately gives out a new IP, makes a new DNS record and shows "domain.local".

So I changed the DHCP lease to forever. Problem solved you'd think. But still every few weeks one of the workstations goes down. Changing the MAC keeps solving this issue.

I can't really think of a solution where to look. Does anyone have an idea?

Answer 1

Hello,

When you say that the workstation can’t connect to the server, what exactly are you referring to? (RDP, AD functions, etc)

thanks,

Mack Marchand

Answer 2

Hello,

Have you noticed any error messages in the Event Viewer logs on both the server and the affected workstations ? Also check the DNS event logs for any errors or warnings that might indicate issues.

How about assigning static IP addresses to the workstations instead of relying on DHCP?

Would this caused by duplicate IP addresses?

Thanks,

Karlie Weng

Answer 3

The workstation just can't connect to the domain. It looks like the DNS is missing.

It keeps the same IP and it has a DNS records. But it can't find it.

Removing the entries do not work. Only thing that works is to create a new MAC so it is getting a new lease and DNS record

Answer 4

Not on the server. On the workstation event id 53.

Static makes no difference. It really looks like it forgets the link between the IP and DNS record.

the records are still there, but does not seem to link to anything.

pinging to the server DNS name works out great. It just can't connect to the domain until I give the workstations a new MAC. Just removing the DNS record and DHCP lease doesn't do anything. It keeps the same IP, but does not create a new DNS record.

Having a new MAC on the card the server seems to know it is a new device and recreates a new record and IP.

No errors found when running dcdiag (besides dcom)

Answer 5

Are there any MAC address filtering or IP address reservation policies configured on your DHCP server specifically for this problematic workstation?

Have you considered reinstalling or updating the network drivers for the network adapter on the affected workstation?