Dear SJMP,
I agree with Meinolf. Based on the KB article 889031, this issue occurs 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
http://support.microsoft.com//kb/889031
In addition to checking the configuration in DHCP server (Meinolf's
suggestions), we need to ensure that the <client_ipaddress> in the
netlogon.log have a matching (defined) subnet in the subnet container in AD
sites and servers.
1. Dump the Subnet Container via replmon
1) Click Start, click Run, type replmon and then press Enter.
2) In the Active Directory Replication Monitor console, right-click
Monitored Servers, and then add the DC which complains about the 5807
events.
3) Right-click the DC, select generate status report. In the Report
Options window, uncheck all but Subnets, and then click OK.
2. Open the log file, scroll to the bottom of the file, you should see a
list of all the Subnets in the AD structure.
3. Compare if <client_ipaddress> in the netlogon.log belong to any of
defined subnets.
You can also zip all the information:
" Status report.
" Netlogon.log
" Windows IP Configuration of a client machine which is reported in the
netlogon,log (ipconfig /all)
And upload to this space:
https://sftasia.one.microsoft.com/choosetransfer.aspx?key=0614749e-437f-4369
-9c45-9dc96de38a5a
Password: rji%+WRX)e
Thanks.
Sincerely,
Joson Zhou
Microsoft Online Support
Microsoft Global Technical Support Center
Get Secure! - www.microsoft.com/security
=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.