Re: Event ID 5807 - No Client Site.... don't understand why..
- From: "Jorge Silva" <jorgesilva_pt@xxxxxxxxxxx>
- Date: Thu, 30 Aug 2007 09:08:32 +0100
Hi
This error is generally caused by bad configuration on sites and services,
you need to associate/create the correct subnets to tha site.
--
I hope that the information above helps you.
Have a Nice day.
Jorge Silva
MCSE, MVP Directory Services
"Luca" <Luca@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:453E090D-2492-4316-868D-0CA717D42228@xxxxxxxxxxxxxxxx
Hi there.
I have noticed that on our head office domain controller we are getting
event ID 5807 logged. The event reads:
"During the past 4.16 hours there have been 26 connections to this Domain
Controller from client machines whose IP addresses don't map to any of the
existing sites in the enterprise. Those clients, therefore, have undefined
sites and may connect to any Domain Controller including those that are in
far distant locations from the clients. A client's site is determined by
the
mapping of its subnet to one of the existing sites. To move the above
clients
to one of the sites, please consider creating subnet object(s) covering
the
above IP addresses with mapping to one of the existing sites. The names
and
IP addresses of the clients in question have been logged on this computer
in
the following log file '%SystemRoot%\debug\netlogon.log' and, potentially,
in
the log file '%SystemRoot%\debug\netlogon.bak' created if the former log
becomes full. The log(s) may contain additional unrelated debugging
information. To filter out the needed information, please search for lines
which contain text 'NO_CLIENT_SITE:'. The first word after this string is
the
client name and the second word is the client IP address. The maximum size
of
the log(s) is controlled by the following registry DWORD value
'HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters\LogFileMaxSize';
the default is 20000000 bytes. The current maximum size is 20000000
bytes.
To set a different maximum size, create the above registry value and set
the
desired maximum size in bytes."
So i check the log mentioned and it shows that the computers in question
are
comming from one of our remote sites. I logon to one of the computers
open a
command prompt type 'set' and it shows me that sure enough the LOGONSERVER
filed shows the wrong server.
Now i am absolutely positive that we have AD sites and services set up
correctly. We have one domain name with 9 sites. Each site has its own
subnet configured and the subnet is assigned to the correct site.
The only thing that i can think of is that in the problematic site we are
using a 26 bit subnet mask i.e. 255.255.255.192. AD sites and Services is
configured to reflect the 26 bit mask. We use VLANs in the site and
currently have it split up into 3 VLANs. In the netlogon log file it only
seems to be computers in 2 of the VLANs that are loging on to a different
DC.
The computers which are in the same VLAN as the local DC do not seem to
have
the problem, just the computers that are in a different VLAN.
I have tripple checked all DHCP and DNS settings and everything is fine...
can anyone give me some pointers as to why this may be happening?
.
- Prev by Date: Re: Active Directory could not create the NTDS Settings object for this domain controller
- Next by Date: Re: Windows cannot obtain the domain controller name for your comp
- Previous by thread: Re: Disaster Recovery Scenario
- Next by thread: ADAMsync - must update source object to get a successful sync ?
- Index(es):
Relevant Pages
|
