Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. Event ID 20291 is logged in the System log when a client computer is moved to a different IP network

Event ID 20291 is logged in the System log when a client computer is moved to a different IP network

View products that this article applies to.

Symptoms

Consider the following scenario:
  • You have two DHCP servers that are running Windows Server 2012 R2.
  • You configure the servers as a failover cluster.
  • You set up multiple DHCP scopes and multiple IP networks.
  • You put a client computer on one of the IP networks and confirm that it receives an IP address from one of the scopes.
  • You move the client computer to a different IP network.

In this scenario, an Error event that resembles one of the following Event ID 20291 events is logged under the "Applications and Services Logs/Microsoft/Windows/Microsoft-Windows-DHCP Server Events" path in Event Viewer:

Source: Microsoft-Windows-DHCP-Server
Date: date/time
Event ID: 20291
Task Category: DHCP Failover
Level: Error
User: NETWORK SERVICE
Computer: DHCP-NODE
Description: A BINDING-ACK message with transaction id: number was sent for IP address: address with reject reason: (Fatal conflict exists: address in use by other client) to partner server: other_dhcp_node for failover relationship: failover_name.
Source: Microsoft-Windows-DHCP-Server
Date: date/time
Event ID: 20291
Task Category: DHCP Failover
Level: Error
User: NETWORK SERVICE
Computer: DHCP-NODE
Description: A BINDING-ACK message with transaction id: Transaction_Number was sent for IP address: IP_Address with reject reason: (Reject Reason Unknown) to partner server: DHCP_Partner_Server for failover relationship: DHCP_Failover_Relationship_Name.

↑ Back to the top

Resolution

Update information

The fix that resolves this problem is included in the November 2014 update rollup for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2.

Note Before you install this update, you have to first remove the failover relationship, install the update to both DHCP nodes and restart them, and then reestablish the failover relationship.

↑ Back to the top

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top

References

Learn about the terminology that Microsoft uses to describe software updates.

↑ Back to the top

Keywords: kbqfe, kbhotfixserver, kbfix, kbexpertiseinter, kbsurveynew, kbbug, kb

↑ Back to the top

Article Info
Article ID : 2955135
Revision : 1
Created on : 1/7/2017
Published on : 6/18/2015
Exists online : False
Views : 609