[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 566
  • Last Modified:

Event ID 5807

Problem is Event ID 5807 source NetLogon for DC's on NewDomain.local  "During the past 4.12 hours there have been 177 connections to this Domain Controller from client machines whose IP addresses don't map to any of the existing sites in the enterprise."

We have 40 remote sites that have no local domain controller for NewDomain.local.  These 40 remotes each have their own individual legacy domains, which trust NewDomain.local.  DC's for NewDomain.local all live at the datacenter and recovery center--these have been setup in Sites and Servises.  I would like to know the best way (easiest)  to set S&S for the remote clients.

Looked at http://support.microsoft.com/default.aspx?scid=kb;en-us;889031 but offers no recommendations for location with no DC.
  • 2
2 Solutions

I think you shoud have the subnet in your AD S&S even you don't have an DC in that subnet/site.


tfranciosiAuthor Commented:
The article assumes sites have DC's in them, which I do not.  Would it make sense to add a generic site with the remote subnets in it, even though the site would not have a DC?  I would think adding all the remote subnets to the main datacenter site with the primary DC's would be a bad idea because it could create a bunch of site links that are not valid comm channels for a DC to talk to another.

What I am trying now is setting up one site with for legacy nets and one with for the MPLS.  Will check in again later...
tfranciosiAuthor Commented:

Featured Post

Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now