site-subnet affinity needs to be updated to reflect the client's subnet in AD and associating it with an appropriate site.

When running dcdiag I am running into this error, I understand the error basically (tell me if I am wrong) means there is a subnet that is not associated with a site and pc's are contacting the DC.  However, I have looked and all the subnets I believe are in the sites.  My question is how do I find out what subnet those 451 connections are from.  Or what is the easiest way to resolve this issue?

During the past 4.22 hours there have been 451 connections to this Domain Controller from client machines whose IP addresses don't map to any of th
 existing sites in the enterprise.

Thank you very much!
Who is Participating?
Mike KlineConnect With a Mentor Commented:
That gets logged in the netlogon.log file, the askpfe team has a powershell script and blog that can help going through the logs


SandeshdubeySenior Server EngineerCommented:
This issue may occur if the following conditions are true:
•The IP address of the client computer is not defined.
•The IP address of the client computer is not mapped to an existing site in the Subnets folder of the  Active Directory Sites and Services snap-in on the local domain controller.
You may receive event ID 5807 on a Windows Server 2003-based domain controller

Step-by-Step Guide to Active Directory Sites and Services
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.