mwebb_sdmc
asked on
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!
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!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
•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
http://support.microsoft.com/kb/889031
Step-by-Step Guide to Active Directory Sites and Services
http://www.activewin.com/win2000/step_by_step/active_directory/adsites.shtml