DHCP Failover Event ID 20292

I got this error with "BAD_ADRESS" in DHCP scope for Wi-Fi segment.
This error on scope occur on Chromebooks. According to web sites, there are same issues reported and it looks like related between Windows Server DHCP feature and Chrome OS.

You might want to apply Windows Update and Hot-fix as much as possible and blow are the list of updates and some information.


The blow updates could not solve 100% but when I configure Wi-Fi network and DHCP to allow Chromebook access only one DHCP Scope (Wi-Fi VLAN segment), the issue stopped...

<Japanese: 日本語>
完全には直らないようだが、Chromebook を特定の DHCP Scope (Wi-Fi VLAN segment) にのみアクセスできるようにすると、この現象がほとんど見られなくなった。。。

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

[  https://support.microsoft.com/en-us/kb/2955135 ]

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:

…

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.

[Install #: 21-24]

November 2014 update rollup for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2

[ https://support.microsoft.com/en-us/kb/3000850 ]

Important When you install this update (3000850) from Windows Update, updates 3016437, 3003057, and 3014442 are included in the installation.

Update for Windows Server 2012 R2 (KB3000850)

Download the x64-based Windows Server 2012 R2 update package now.

[  http://www.microsoft.com/en-us/download/details.aspx?id=44975 ]

* To apply this update, you must first install update 2919355 on Windows 8.1 or Windows Server 2012 R2

[Install #: 11 - 17 ]

Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 update: April 2014

[  https://support.microsoft.com/en-us/kb/2919355 ]

Important When you install this update (2919355) from Windows Update, updates 2932046, 2937592, 2938439, 2934018, and 2959977 are included in the installation.

Download the x64-based Windows Server 2012 R2 update package now.

Windows Server 2012 R2 Update (KB2919355)

[  https://www.microsoft.com/en-us/download/details.aspx?id=42334 ]

Note The updates must be installed in the following order:

clearcompressionflag.exe, KB2919355, KB2932046, KB2959977, KB2937592, KB2938439, and KB2934018.

* Prerequisites

To apply this update, you must have the following update installed on Windows RT 8.1, Windows 8.1, or Windows Server 2012 R2:

2919442 A servicing stack update is available for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2: March 2014

[install #: 01 ]

A servicing stack update is available for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2: March 2014

[  https://support.microsoft.com/en-us/kb/2919442 ]

Method 1: Windows Update

This update rollup is provided as an important update from Windows Update. If you turn on automatic updating, this update is automatically installed.

Update for Windows Server 2012 R2 (KB2919442)

[ https://www.microsoft.com/en-us/download/details.aspx?id=42153 ]

Blog Tech Net:

DHCP Failover fixes in KB 2919393 for Windows Server 2012 and KB 2919355 for Windows Server 2012 R2

[  http://blogs.technet.com/b/teamdhcp/archive/2014/02/26/dhcp-failover-patch-to-address-a-reservation-issue-and-another-issue-related-to-failover-partner-not-accepting-state-transition-from-bad-address-gt-active-has-been-released.aspx?pi47623=2 ]

Good Luck!!

-End-