Windows PXE IPv4 Pass but IPv6 fail,WdsClient:There was a problem initializing WDS Mode.

Hi Nick Li, thank you for contacting the Microsoft Community.

I have heard about this error several times, and each case came from a different cause. So below, I have compiled all the possible sources of the issue that I have encountered so far for your reference.

Some common causes:

• Do not assign a static IP to the host PC on your DHCP server.
• The client and the WDS server are on different subnets.
• The NIC drivers are not included in the boot image (note: the boot image, not the install image).
• There is no VMware system running on the network, or it is not running a parallel DHCP service.

Most common cause:

Configure WDS for IPv6:

After adding DHCPv6 option 59.

Ensure that WDS is configured to listen on the IPv6 interface.

Open the WDS management console, right-click the server name → Properties → DHCP tab. Make sure “Configure DHCP option 60 to indicate that this server is also a PXE server” is unchecked, as this does not apply to IPv6.

Ensure that WDS is configured to respond to all client computers (both known and unknown).

 Additional Tips:

Firewall Settings: Ensure that the firewall allows traffic on the ports used by WDS and DHCP.

Check Server Logs: Examine the logs on the WDS and DHCP servers for any error messages related to IPv6 PXE boot.

Test Network Connectivity: Ensure that the PXE client can communicate with the server over IPv6.

If you find this answer helpful, don’t hesitate to click “Accept Answer” so everyone can refer to it. 😊

Thank you.

Dustin Tran

The issue you're experiencing with WDS (Windows Deployment Services) when using IPv6 could be related to the configuration of your DHCP and WDS settings. Here are some considerations to help troubleshoot the problem:

1. DHCP Scope Options: When using a mix of IPv4 and IPv6, ensure that your DHCP scope options are correctly configured for both protocols. For IPv6, you may need to use IP Helper Table Entries instead of DHCP Scope Options to direct PXE clients to the Boot Program on the WDS server, especially if you have both UEFI and Legacy BIOS machines.
2. WDS Configuration: Ensure that WDS is configured to support IPv6. You might need to check the settings in the WDS management console to ensure that it is properly set up for IPv6 operations.
3. Link-Local Addresses: The fact that you can connect using a link-local address (fe80::) but not with a global address (2001:DB8::) suggests that there may be issues with routing or firewall settings that are preventing the global address from functioning correctly.
4. Firewall Settings: Verify that your firewall settings allow traffic over the necessary ports for PXE booting with IPv6. Ensure that the ports used by WDS for IPv6 are not blocked.
5. Boot File Configuration: Double-check that the correct boot files are included in your boot.wim file and that they are compatible with the IPv6 environment.
6. Logs and Diagnostics: Review the WDS logs for any specific error messages that could provide more insight into the issue. You can enable logging in WDS to gather more detailed information about the PXE boot process.

If the problem persists, consider reaching out to your network infrastructure team to ensure that the IPv6 routing is correctly configured and that there are no network-related issues affecting the PXE boot process.

References:

• Invalid Boot File Received Error Message When PXE booting from WDS
• The WDS server may not start, and an error is logged in the System log when you start the WDS server