This Rule generates alerts when Network Load Balancing cannot be configured properly because there is no suitable network adapter
The Firewall service generates this alert when it detects that a network which is not directly connected (has no associated adapter) is NLB enabled.
A "network behind a network" cannot be enabled for NLB, because no adapter can be associated with the configured Virtual IP (VIP) address.NLB is functional if this error occurs, but the traffic may not pass through TMG Server as expected.
The Firewall service may encounter the illegal configuration described above for one of the following reason:
An NLB-enabled network which is not directly connected (behind another network) is defined.
Enable NLB on the network which is directly connected and disable NLB for the network behind it.
Use a Virtual IP (VIP) of the connected network to reach TMG Server.
Microsoft TechNet Web site
Target | Microsoft.Forefront.TMG.NLB.ServerComponent |
Category | EventCollection |
Enabled | True |
Alert Generate | False |
Remotable | True |
ID | Module Type | TypeId | RunAs |
---|---|---|---|
DS | DataSource | Microsoft.Forefront.TMG.Rule.AlertGenerate.DS | Default |
WA | WriteAction | Microsoft.Forefront.TMG.Rule.AlertGenerate.WA | Default |
<Rule ID="Microsoft.Forefront.TMG.Network_Load_Balancing_cannot_be_configured_properly_because_there_is_no_suitable_network_adapter.Rule" Enabled="true" Target="Microsoft.Forefront.TMG.NLB.ServerComponent" ConfirmDelivery="true" Remotable="true" Priority="Normal" DiscardLevel="100">
<Category>EventCollection</Category>
<DataSources>
<DataSource ID="DS" TypeID="Microsoft.Forefront.TMG.Rule.AlertGenerate.DS">
<ComputerName>$Target/Host/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/NetworkName$</ComputerName>
<LogName>Application</LogName>
<EventsPattern>^(21113)$</EventsPattern>
<EventType>1</EventType>
<SourcePattern>[Microsoft Forefront TMG Firewall]|[Microsoft Forefront TMG Control]</SourcePattern>
</DataSource>
</DataSources>
<WriteActions>
<WriteAction ID="WA" TypeID="Microsoft.Forefront.TMG.Rule.AlertGenerate.WA">
<AlertMessageId>$MPElement[Name="Microsoft.Forefront.TMG.Network_Load_Balancing_cannot_be_configured_properly_because_there_is_no_suitable_network_adapter.AlertMessage"]$</AlertMessageId>
<DomainName>$Target/Host/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/DomainDnsName$</DomainName>
<Priority>1</Priority>
<Severity>2</Severity>
</WriteAction>
</WriteActions>
</Rule>