| Event Id | 21113 |
| Source | DNS Intrusion Detection Filter |
| Description | There is no network adapter related to network '%1'. Network Load Balancing cannot be configured properly, and will be stopped on this server |
| Event Information |
According to Microsoft : CAUSE : The computer must have a network adapter that is associated with the network and has static IP address configured on it. Also, if the computer is running on Windows Server™ 2003 without any service packs installed (SP1 or later), the network adapter must not be the network adapter used for intra-array communication. The Firewall service cannot find a suitable network adapter for one of the following reasons: There is no adapter with an IP address in the range of the NLB-enabled network.The IP configured on the adapter is in the range of the NLB-enabled networks but the adapter is DHCP-enabled.There is no additional network adapter for intra-array communication (on Windows Server 2003 computers without Service Pack 1 installed).There are IP conflicts on one of the network adapters. SOLUTION : Change the network ranges of the NLB-enabled network so that they contain all the IP addresses of a network adapter which is not DHCP-enabled.Add an additional network adapter for intra-array communication.Check that the Virtual IP (VIP) you selected for the NLB-enabled network is not also configured as a Dedicated IP (DIP) of other computers in the subnet. For more information about NLB, see the Network Load Balancing topic in ISA Server Help.. For more information about Microsoft implementation of load balancing protocol look for Network Load Balancing (NLB) topic in http://msdn.microsoft.com. |
| Reference Links | Event ID: 21113 Of Source ID:DNS Intrusion Detection Filter |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.