Citrix Provisioning Services : BSOD "NETWORK_BOOT_DUPLICATE_ADDRESS

Citrix Provisioning Services : BSOD "NETWORK_BOOT_DUPLICATE_ADDRESS

book

Article ID: CTX215516

calendar_today

Updated On:

Description

Intermittent Blue Screen on Target Devices with an error NETWORK_BOOT_DUPLICATE_ADDRESS. The error was present using both PXE & BDM ISO

PC error Message

 

Environment

Caution! Using Registry Editor incorrectly can cause serious problems that might require you to reinstall your operating system. Citrix cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk. Be sure to back up the registry before you edit it.

Resolution

Solution 1

The solution to the problem is to delete the registry keys containing IP-addresses on the PVS Streaming Interface ( two Interfaces on my pvs target Devices ). The registry keys needs to be deleted in both ControlSet001 and ControlSet002.

DHCP registry

Create a batch file with the following lines and run it just before shutdown whenever the vdisk has been in Read / Write mode or New Version Maintenance mode. Remember to replace the GUID with your own values.
 

REM * Remove IP-information to avoid duplicate IP bluescreens

reg delete HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\Tcpip\Parameters\Interfaces\{6B367847-567F-4C19-B42E-EF27899A1F9D} /v DhcpServer /f

reg delete HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\Tcpip\Parameters\Interfaces\{6B367847-567F-4C19-B42E-EF27899A1F9D} /v DhcpIPAddress /f

reg delete HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\Tcpip\Parameters\Interfaces\{6B367847-567F-4C19-B42E-EF27899A1F9D} /v DhcpSubnetMask /f

reg delete HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\Tcpip\Parameters\Interfaces\{6B367847-567F-4C19-B42E-EF27899A1F9D} /v DhcpSubnetMaskOpt /f

reg delete HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\Services\Tcpip\Parameters\Interfaces\{6B367847-567F-4C19-B42E-EF27899A1F9D} /v DhcpServer /f

reg delete HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\Services\Tcpip\Parameters\Interfaces\{6B367847-567F-4C19-B42E-EF27899A1F9D} /v DhcpIPAddress /f

reg delete HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\Services\Tcpip\Parameters\Interfaces\{6B367847-567F-4C19-B42E-EF27899A1F9D} /v DhcpSubnetMask /f

reg delete HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\Services\Tcpip\Parameters\Interfaces\{6B367847-567F-4C19-B42E-EF27899A1F9D} /v DhcpSubnetMaskOpt /f

Solution 2

Create a simple script that the customer could tag on to the end of their existing shutdown processes for the Master VM whenever it is updated that:

Stops the DHCP client service: “Net stop DHCP”

Blanks the following registry keys: “regedit /s DHCP_clear.reg”

The DHCP_clear.reg file contained blank values for the following keys:

———————————————–

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters]
“NameServer”=””

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces]

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{GUID_OF_NETWORK_ADAPTOR}]
“NameServer”=””
“Domain”=””
“DhcpIPAddress”=””
“DhcpSubnetMask”=””
“DhcpServer”=””
“DhcpNameServer”=””
“DhcpDefaultGateway”=””


Problem Cause

  • VMs are using the cached registry information to send a renewal request to the DHCP servers as they come up.
  • 50% of the time the DHCP server responds within the expected time and issues it a new address.
  • The other 50% of the time the DHCP server doesn’t respond within the expected time frame so the client enters a rebinding state, broadcasting a DHCPDiscover message to any available DHCP servers to update its current IP address lease.
  • While it waits for responses it is using the cached registry information for it’s address.
  • As PVS streaming is happening over this address it conflicts with other VMs that are also experiencing the issue and kicks out to a blue screen before the DHCP server can sort out the mess ( DHCP is pretty good at this – but if it doesn’t do it quick enough it will be too late as the PVS target device has already failed.