Microsoft-Windows-NLB-Diagnostic

14 events across 1 channel

Event	Title	Channel	Sample
1	FilteringReceiveAccept	Diagnostic	N
2	FilteringReceiveDrop	Diagnostic	N
3	FilteringReceiveAccept3	Diagnostic	N
4	FilteringReceiveDrop4	Diagnostic	N
5	FilteringSendAccept	Diagnostic	N
6	FilteringSendDrop	Diagnostic	N
7	FilteringSendAccept7	Diagnostic	N
8	FilteringSendDrop8	Diagnostic	N
9	AffinityCreate	Diagnostic	N
10	AffinityDestroy	Diagnostic	N
11	GhostingGhost	Diagnostic	N
12	GhostingUnGhost	Diagnostic	N
13	ConnectionUp	Diagnostic	N
14	ConnectionDown	Diagnostic	N

Event ID 1: FilteringReceiveAccept

Provider: Microsoft-Windows-NLB-Diagnostic
Channel: Diagnostic
Task: Task.Filtering.ReceiveAccept

Message #

NLB cluster on interface %1 received traffic from %4 destined to %6 [protocol: %7 (%9), flags: %8]. This cluster node will accept this traffic (reason: %2). Source port %10, destination port %11, and protocol %12 have been used for the accept/drop decision.

Fields #

Name	Description
`InterfaceGUID` GUID
`Reason` UInt32
`SourceIPLength` UInt32
`SourceIP` Binary
`DestinationIPLength` UInt32
`DestinationIP` Binary
`Protocol` UInt8
`Flags` HexInt32
`Data` HexInt32
`HashSourcePort` UInt16
`HashDestinationPort` UInt16
`HashProtocol` UInt16
`Bucket` UInt8
`CurrentBucketMap` HexInt64

Event ID 2: FilteringReceiveDrop

Provider: Microsoft-Windows-NLB-Diagnostic
Channel: Diagnostic
Task: Task.Filtering.ReceiveDrop

Message #

NLB cluster on interface %1 received traffic from %4 destined to %6 [protocol: %7 (%9), flags: %8]. This cluster node will drop this traffic (reason: %2). Source port %10, destination port %11, and protocol %12 have been used for the accept/drop decision.

Fields #

Name	Description
`InterfaceGUID` GUID
`Reason` UInt32
`SourceIPLength` UInt32
`SourceIP` Binary
`DestinationIPLength` UInt32
`DestinationIP` Binary
`Protocol` UInt8
`Flags` HexInt32
`Data` HexInt32
`HashSourcePort` UInt16
`HashDestinationPort` UInt16
`HashProtocol` UInt16
`Bucket` UInt8
`CurrentBucketMap` HexInt64

Event ID 3: FilteringReceiveAccept3

Provider: Microsoft-Windows-NLB-Diagnostic
Channel: Diagnostic
Task: Task.Filtering.ReceiveAccept

Message #

NLB cluster on interface %1 received traffic from %4 destined to %6. This cluster node will accept this traffic (reason: %2). An application registered hook requested that source %8, destination %10, and protocol %11 be used for the accept/drop decision.

Fields #

Name	Description
`InterfaceGUID` GUID
`Reason` UInt32
`SourceIPLength` UInt32
`SourceIP` Binary
`DestinationIPLength` UInt32
`DestinationIP` Binary
`HookSourceIPLength` UInt32
`HookSourceIP` Binary
`HookDestinationIPLength` UInt32
`HookDestinationIP` Binary
`Protocol` UInt8
`Flags` HexInt32
`Bucket` UInt8
`CurrentBucketMap` HexInt64

Event ID 4: FilteringReceiveDrop4

Provider: Microsoft-Windows-NLB-Diagnostic
Channel: Diagnostic
Task: Task.Filtering.ReceiveDrop

Message #

NLB cluster on interface %1 received traffic from %4 destined to %6. This cluster node will drop this traffic (reason: %2). An application registered hook requested that source %8, destination %10, and protocol %11 be used for the accept/drop decision.

Fields #

Name	Description
`InterfaceGUID` GUID
`Reason` UInt32
`SourceIPLength` UInt32
`SourceIP` Binary
`DestinationIPLength` UInt32
`DestinationIP` Binary
`HookSourceIPLength` UInt32
`HookSourceIP` Binary
`HookDestinationIPLength` UInt32
`HookDestinationIP` Binary
`Protocol` UInt8
`Flags` HexInt32
`Bucket` UInt8
`CurrentBucketMap` HexInt64

Event ID 5: FilteringSendAccept

Provider: Microsoft-Windows-NLB-Diagnostic
Channel: Diagnostic
Task: Task.Filtering.SendAccept

Message #

NLB cluster on interface %1 intercepted outgoing traffic from %4 destined to %6 [protocol: %7 (%9), flags: %8]. This cluster node will send this traffic (reason: %2).

Fields #

Name	Description
`InterfaceGUID` GUID
`Reason` UInt32
`SourceIPLength` UInt32
`SourceIP` Binary
`DestinationIPLength` UInt32
`DestinationIP` Binary
`Protocol` UInt8
`Flags` HexInt32
`Data` HexInt32

Event ID 6: FilteringSendDrop

Provider: Microsoft-Windows-NLB-Diagnostic
Channel: Diagnostic
Task: Task.Filtering.SendDrop

Message #

NLB cluster on interface %1 intercepted outgoing traffic from %4 destined to %6 [protocol: %7 (%9), flags: %8]. This cluster node will drop this traffic (reason: %2).

Fields #

Name	Description
`InterfaceGUID` GUID
`Reason` UInt32
`SourceIPLength` UInt32
`SourceIP` Binary
`DestinationIPLength` UInt32
`DestinationIP` Binary
`Protocol` UInt8
`Flags` HexInt32
`Data` HexInt32

Event ID 7: FilteringSendAccept7

Provider: Microsoft-Windows-NLB-Diagnostic
Channel: Diagnostic
Task: Task.Filtering.SendAccept

Message #

NLB cluster on interface %1 intercepted outgoing traffic from %4 destined to %6. This cluster node will send this traffic (reason: %2). An application registered hook requested that source %8, destination %10, and protocol %11 be used for the accept/drop decision.

Fields #

Name	Description
`InterfaceGUID` GUID
`Reason` UInt32
`SourceIPLength` UInt32
`SourceIP` Binary
`DestinationIPLength` UInt32
`DestinationIP` Binary
`HookSourceIPLength` UInt32
`HookSourceIP` Binary
`HookDestinationIPLength` UInt32
`HookDestinationIP` Binary
`Protocol` UInt8
`Flags` HexInt32

Event ID 8: FilteringSendDrop8

Provider: Microsoft-Windows-NLB-Diagnostic
Channel: Diagnostic
Task: Task.Filtering.SendDrop

Message #

NLB cluster on interface %1 intercepted outgoing traffic from %4 destined to %6. This cluster node will drop this traffic (reason: %2). An application registered hook requested that source %8, destination %10, and protocol %11 be used for the accept/drop decision.

Fields #

Name	Description
`InterfaceGUID` GUID
`Reason` UInt32
`SourceIPLength` UInt32
`SourceIP` Binary
`DestinationIPLength` UInt32
`DestinationIP` Binary
`HookSourceIPLength` UInt32
`HookSourceIP` Binary
`HookDestinationIPLength` UInt32
`HookDestinationIP` Binary
`Protocol` UInt8
`Flags` HexInt32

Event ID 9: AffinityCreate

Provider: Microsoft-Windows-NLB-Diagnostic
Channel: Diagnostic
Task: Task.Affinity.Create

Message #

NLB cluster on interface %1 port %2 bucket %3 created client affinity for address %5.

Fields #

Name	Description
`InterfaceGUID` UnicodeString
`PortId` UInt16
`BucketId` UInt16
`SourceIPLength` UInt32
`SourceIP` Binary

Event ID 10: AffinityDestroy

Provider: Microsoft-Windows-NLB-Diagnostic
Channel: Diagnostic
Task: Task.Affinity.Destroy

Message #

NLB cluster on interface %1 port %2 bucket %3 destroyed client affinity for address %5.

Fields #

Name	Description
`InterfaceGUID` UnicodeString
`PortId` UInt16
`BucketId` UInt16
`SourceIPLength` UInt32
`SourceIP` Binary

Event ID 11: GhostingGhost

Provider: Microsoft-Windows-NLB-Diagnostic
Channel: Diagnostic
Task: Task.Ghosting.Ghost

Message #

NLB cluster ghosted client %6. interface=%1;port=%2;bucket=%3;otherhost=%4.

Fields #

Name	Description
`InterfaceGUID` UnicodeString
`PortId` UInt16
`BucketId` UInt16
`HostId` UInt16
`SourceIPLength` UInt32
`SourceIP` Binary

Event ID 12: GhostingUnGhost

Provider: Microsoft-Windows-NLB-Diagnostic
Channel: Diagnostic
Task: Task.Ghosting.UnGhost

Message #

NLB cluster unghosted client %6. interface=%1;port=%2;bucket=%3;otherhost=%4.

Fields #

Name	Description
`InterfaceGUID` UnicodeString
`PortId` UInt16
`BucketId` UInt16
`HostId` UInt16
`SourceIPLength` UInt32
`SourceIP` Binary

Event ID 13: ConnectionUp

Provider: Microsoft-Windows-NLB-Diagnostic
Channel: Diagnostic
Task: Task.Connection.Up

Message #

NLB cluster Connection Up %2 -> %4 references=%5, flags=%6.

Fields #

Name	Description
`SourceIPLength` UInt32
`SourceIP` Binary
`DestinationIPLength` UInt32
`DestinationIP` Binary
`References` UInt32
`Flags` HexInt32

Event ID 14: ConnectionDown

Provider: Microsoft-Windows-NLB-Diagnostic
Channel: Diagnostic
Task: Task.Connection.Down

Message #

NLB cluster Connection Down %2 -> %4 references=%5, flags=%6.

Fields #

Name	Description
`SourceIPLength` UInt32
`SourceIP` Binary
`DestinationIPLength` UInt32
`DestinationIP` Binary
`References` UInt32
`Flags` HexInt32

Provenance

Where this provider's schema came from, and which Windows build it was observed on. Windows can change a provider's event schema between builds, so use this to judge whether it matches the build you collect from.

ETW provider GUID def02e30-3290-4b2d-bc28-d2b0edadf411

Defined in nlb.sys, the binary that emits these events.

Observed on:

WS2022-20348.4893, schema read from the registered manifest, binary version 10.0.20348.1, captured 2026-06-02

Downloads

Microsoft-Windows-NLB-Diagnostic registered manifest XML (in the WS2022-20348.4893 manifest pack, 1.9 MB) manifest-xml

`j` / `k`	Scroll down / up
`d` / `u`	Half-page down / up
`gg` / `G`	Top / bottom
`h` / `l`	History back / forward
`f`	Follow link (`Shift` = new tab)
`/`	Focus search
`?`	Toggle this help
`↑` / `↓`	Navigate search results
`Enter`	Open highlighted result
`Esc`	Close results / dialog

`type:`	`events` / `rules` / `providers`
`vendor:`	`sigma` / `elastic` / `splunk` / `kusto` / `chronicle` (vendor name alone also works: `sigma:`, `kql:`, `secops:`…)
`tactic:`	TA-id, slug, or name: `credential_access`, `TA0006`
`technique:`	technique or sub-technique ID: `T1003`, `T1003.001` (alias `tech:`)
`severity:`	`critical` / `high` / `medium` / `low` / `informational` (alias `sev:`)
`risk_score`	Numeric comparison on the Elastic risk score (0 to 100): `risk_score>50`, `risk_score<=20`, `risk_score=99` (alias `risk`; Elastic rules only)
`stages:`	Rules with exactly N pipeline stages
`correlation:`	`single_event` / `sequence` / `alternatives` / `alternatives_cross_log` / `all_required` / `correlated`
`with:`	Co-occurrence event-id; stacks (`with:4624 with:4769`) to require all, while a comma list in one occurrence (`with:4624,4769`) is an either-or group. Implies multi-event
`like:`	Structural neighbors of a rule slug (equivalents + subsumption stricter / broader): `like:comsvcs_lsass_memory_dump-splunk-sysmon`
`groupby:`	Entity-grouping substring match against `group_by_keys`: `groupby:user`, `groupby:host`
`uses:`	Rules whose predicate tree touches the field (any kind, any value): `uses:CommandLine`
`excludes:`	Rules with top-level `not()` clauses on the field (FP whitelists): `excludes:ParentImage`
`field:` / `value:`	Predicate search; narrows rule cards to those with a matching leaf and drives the indicator tier. Unquoted = substring, wildcards allowed (`value:mimikatz`)
`indicator:`	Shorthand for `field:F value:V`: `indicator:Image=*\powershell.exe`
`kind:`	Filter by predicate kind. Narrows rule cards to those carrying a matching predicate leaf (`vendor:elastic kind:cidr_match`) and drives the indicator tier: `contains` / `starts_with` / `ends_with` / `regex` / `cidr` / `eq` / `in` … (operator aliases `op:`/`match:`)
`has:` / `no:`	`sample`, `field`, `notes`, `refs`, `trace`, `thirdparty`, `rule`, `pattern`, `timewindow`, `threshold`, `newterms`, `sigma`/`elastic`/`splunk`/`kusto`/`chronicle`
`-op:val`	Exclude matches; works on most operators but not `type:`/`like:`/`has:`/`no:` (use `no:<flag>` to exclude a rule flag): `tactic:execution -vendor:splunk`. Standalone `-kind:`/`-field:`/`-value:` drop every rule carrying a matching predicate leaf (`type:rules -kind:is_null`)
`field:"…"` / `value:"…"`	Quoted value = anchored exact match (also allows spaces): `value:"net user"`
`a,b`	Comma = OR inside one operator (`vendor:sigma,elastic`, `severity:high,critical`); repeating a facet merges the same way. `field:`/`value:` never split (literal commas)
`vendors:` / `stage:`	Singular and plural spellings fold to the canonical operator and value: `tactics:` = `tactic:`, `type:event` = `type:events`, `correlation:sequences` = `correlation:sequence`, `has:thresholds` = `has:threshold`
`"quoted phrase"`	Exact-match a multi-word phrase (free text)