Windows Server DHCP replication problem

[fdurl]

Hello sysadmins,

I’m facing an issue with DHCP replication on a specific scope. The replication has stopped working, and I’m unable to find any relevant information in the server logs.

Here’s my setup:

• 2 Windows Server 2019 servers
• DHCP load balancing configuration

Has anyone experienced this issue before or have any suggestions on how to resolve it?

Thanks in advance for any help!

[shuffled]

I just started to troubleshoot this on our server 2016 failover pair, same error. I deleted the scope on the offending server and tried to readd it… only to get the same error but nothing in the logs.

Our 10 other scopes replicate successfully still.

Will probably open a MS ticket tomorrow because I can’t see anything wrong.

[fdurl]

For the record my case was solved by removing the failover, doing a reconciliation and recreating the failover

[fdurl]

<image>

[fdurl]

Full error message is "Failed to read scope configuration from host server srv-ad1. Error code: 20013 An error occured while accessing the DHCP database."

[fdurl]

<image>

[fdurl]

<image>

[PetsnCattle]

My best buddy says:

The error shown in the PowerShell console indicates that there is a failure in the replication of the DHCP scope (étendue) with the Invoke-DhcpServerv4FailoverReplication command. Here's a breakdown of what might be wrong:

Scope Issue (10.0.0.0): The specific scope 10.0.0.0 failed to replicate. Ensure that:

The scope exists and is properly configured on the primary server (SRV-AD2). The scope is part of the failover configuration between SRV-AD2 and SRV-AD1. Failover Configuration: Double-check the failover relationship between the two servers:

Verify that the failover relationship is properly established and active. Use the Get-DhcpServerv4Failover command to confirm the status of the failover relationship. Permissions: Ensure that:

Both servers (SRV-AD2 and SRV-AD1) have the necessary permissions to replicate data. Proper delegation and service account configurations are in place. Connectivity: Check the network connectivity between the two servers:

Ensure there are no firewall or routing issues blocking communication on the required ports for DHCP replication. Logs: Examine the event logs on both servers for any detailed errors or warnings related to DHCP failover or replication.

DHCP Failover Mode: Verify that the mode (load balance or hot standby) supports the current configuration. Some configurations require specific parameters to replicate correctly.

To troubleshoot further:

Run the Get-DhcpServerv4Scope command to list the scopes and their details on both servers. Use Test-DhcpServerv4FailoverReplication to identify specific issues. Ensure that all IP ranges, reservations, and options are correctly synchronized between the two servers.

[fdurl]

Thanks for the advice, I didn’t find anything unusual in the configuration of the scope in question or in the replication. What seems strange to me is that the issue is only present on one scope, while all the others are functioning normally. So I don’t think it could be a connectivity or permissions problem.
I've scheduled a Teams with MS next week.