Skip to main content

mom: subnet missing from ad site configuration

if you've upgraded your domain controllers to windows 2003 (and i hope by now you have), you won't be able to pick up these events anymore:

Event Type: Information
Event Source: NETLOGON
Event Category: None
Event ID: 5778
Date:
Time:
User: N/A
Computer: 'Computer Name'
Description: 'Computer Name' tried to determine its site by looking up its IP address ('Computer IP Address') in the Configuration\Sites\Subnets container in the DS. No subnet matched the IP address. Consider adding a subnet object for this IP address.

instead, you get this type of event message that really doesn't help at all:
Event Type: Information
Event Source: NETLOGON
Event Category: None
Event ID: 5807
Date:
Time:
User: N/A
Computer: 'Computer Name'
Description: During the past 4.22 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.
if you're still interested in these messages, you can create a new type of rule, pulling from a different location instead. the first thing you'll need to do is create a new provider. in my case, i named it something silly like... netlogon log. here are the parameters:
  • provider name: netlogon log
  • provider log type: generic single-line log file
  • directory: c:\windows\debug
  • format: generic
  • file pattern: netlogon.log
now create a new rule with the netlogon log provider that we created above. i set the criteria to:
description contains substring ': NO_CLIENT_SITE:'
now you can set it to alert or just collect the event data. it'll read the netlogon.log file and send up an event every time a line matching the description above shows up. the event data will look like this:
Description:
DIR:C:\Windows\debug, Log Directory
FIL:Netlogon.log, Log File
FMT: Generic Single-Line Log File Format, File Format
ENT: 01/01 12:01:01 DOMAIN: NO_CLIENT_SITE: COMPUTERNAME 10.1.1.89

Comments

  1. Hi,

    Thanks for the info...However, if I may, could you please clarify something else...once the collection is configured, how do you have it generate events based on what it finds in the netlogon logs? Do you create another event rule ?

    ReplyDelete
  2. It was very helpful..thanks!

    ReplyDelete
  3. senna, glad it helped. all you have to do is set the event rule to trigger an alert. otherwise, you can create an alert rule to pick up the information in the events. i went the simple route and chose the first option. :)

    ReplyDelete
  4. senna, glad it helped. all you have to do is set the event rule to trigger an alert. otherwise, you can create an alert rule to pick up the information in the events. i went the simple route and chose the first option. :)

    ReplyDelete

Post a Comment

Popular posts from this blog

how to retrieve your ip address with powershell...

update: this is how it’s performed in powershell v3 as demonstrated here.(get-netadapter | get-netipaddress | ? addressfamily -eq'IPv4').ipaddress update: this is by far the easiest.PS C:\temp> (gwmi Win32_NetworkAdapterConfiguration | ? { $_.IPAddress -ne $null }).ipaddress
192.168.1.101
are you laughing yet?  i know you probably find this topic amusing.  it's really interesting though.  whenever you get over it, i'll do this in the standard cmd.exe interpreter and then in powershell to show you what kind of coolness powershell does.done?  okay, good.  this is an interpretation of a demo that bob wells did at our smug meeting.  hope you like it.i should tell you, it's not as simple as the title would lead you to believe.  i like doing that little slight-of-hand thing since it gives the impression that i'm painting a very easy target on my back for your criticism (though it's probably true in other ways)!  the idea is that we want to retrieve just the ip ad…

understanding the “ad op master is inconsistent” alert

i use the term “understanding” loosely.  this is by far no definitive guide on this particular alert, just a few things i have picked up in my attempt to understand it.let’s look at the context of the alert:The Domain Controller's Op Master is inconsitent. See additional alerts for details.
first of all, it gives very little information.  the only particularly useful detail is that it indicates which server is having the issue.  other than that, just a spelling error as there are no additional critical alerts to look at for details.this rule, as you know, comes from a sealed mp.  therefore, we can’t modify anything in it except the overrides.  the couple i’ve tinkered with are:interval (sec) log success event to begin with, interval (sec) is just set way too high.  the default is 60 seconds.  why on earth would anyone want to know that your op master consistency may be off, every minute?  actually, i could think of a few reasons, but really, it’s overkill.  the way the script works…

sccm: content hash fails to match

back in 2008, I wrote up a little thing about how distribution manager fails to send a package to a distribution point. even though a lot of what I wrote that for was the failure of packages to get delivered to child sites, the result was pretty much the same. when the client tries to run the advertisement with an old package, the result was a failure because of content mismatch.I went through an ordeal recently capturing these exact kinds of failures and corrected quite a number of problems with these packages. the resulting blog post is my effort to capture how these problems were resolved. if nothing else, it's a basic checklist of things you can use.DETECTIONstatus messagestake a look at your status messages. this has to be the easiest way to determine where these problems exist. unfortunately, it requires that a client is already experiencing problems. there are client logs you can examine as well such as cas, but I wasn't even sure I was going to have enough material to …