How to Fix Windows Server failed to release DHCP Lease

We tried to set a static IP address using the Command Prompt in Windows Server Core Edition and got a message stating, "Failed to release DHCP Lease." This error message could be brought on by modifying the settings of the network adapter. This post would explain some remedies and workarounds in case Windows Server failed to release the DHCP lease.

Fix Dismissal of DHCP Lease was unsuccessful on Windows Server.

If the DHCP lease could not be released by the Windows Server, try the solutions provided below.

Inspect for Updates to the Server

Switch the IP address manually by starting the DHCP client service again.

We should go into depth about them.

1-Verify if There Are Any Updates for the Server

If there is some bug in your OS version, then you can face issues while setting up network settings for your server. Though it is not officially confirmed by them, we will keep checking for updates to see if Microsoft has released a patch for this bug. Go to Settings > Update & Security, and click on Check for updates. Install any available update and restart your computer to check if the issue persists.

2] Forcibly Changing the IP Address

We will make a temporary adjustment to the server's IP address manually via the CLI if there are no updates available that can be accessed. We have to manipulate the IP address manually in order to get around this particular problem. In most instances, the option will read "Exit to the command line (PowerShell)"; if you're not on the screen the error came up on, just open PowerShell-as an administrator. If you happen to be on that screen, just press Enter to continue.

To view your list of network interface cards and their aliases, open up PowerShell and then run the Get-NetAdapter command.

To determine which alias for your network interface card to configure, type the following command to fetch the listing of all possible aliases of your card. In that listing, the existing alias will have its current IP address changed.

Using your choice of alias found with the above command run: deactivate Ethernet Interface's IP address below listed command: remove-netIPAddress -interfacealias ethernet -confirm"Not true."

1. we will dissect the command.

The Remove-NetIPAddress cmdlet removes an IP address and all of its configuration from an interface in a network.

InterfaceAlias Ethernet: This specifies the interface in the network that will be configured with the IP address. In this case, the Ethernet port.

confirm:$false: This allows the command to be carried out without any user input; that is, it hides the confirmation prompt that would appear if the cmdlet were to run.

For my particular case, it was Remove-NetIPAddress -InterfaceAlias Ethernet0 -confirm:$False.

Now that the IP has been removed, it is our duty to assign a new one. The following command when executed will do the task.

Create-NetIPAddress with the following parameters: {NAME} as the interface name, {IP} as the IP address, {L} as the prefix length, and {GATEWAY_IP} as the default gateway.

Now we can see the description of the command.

The New-NetIPAddress cmdlet configures a network interface with a new IP address.

The IP address to be assigned to a network interface can be specified using the InterfaceAlias {NAME} method. Replace the actual name of the network interface, such Ethernet, for {NAME}.

Specifies the new Internet Protocol (IP) address to assign. Replace {IP} with the actual IP address, such as 192.168.1.10.

The subnet mask, or subnet prefix length, of the IP address can be set by the PrefixLength {L} parameter. For instance, for a subnet mask of 255.255.255.0, you would use the number 24 as the prefix length {L}.

The IP address of the default gateway can be indicated by using DefaultGateway {GATEWAY_IP}. Replace {GATEWAY_IP} with the actual IP address of the gateway, such as 192.168.1.1.

After replacing all the variables, the command for my server is: New-NetIPAddress with the following parameters: 192.168.1.4 as the IP address, 24 as the prefix length, and 192.168.1.1 as the default gateway. You should adjust the query to take into consideration that you are not using the default gateway and IP address.

In the solution below, a new static IP address will be set and the current one removed.

3. Restart the DHCP client.

At the core of every network, Dynamic Host setup Protocol Client Service-DHCP-is responsible for managing IP address allocation among other setup factors automatically. In the case of automatic IP assignment issues, we could restart the DHCP Client Service on your machine. Let's open PowerShell and execute the following command to do that.

Service DhcpClient Restart

After that, check to see if the problem is still there. If the problem still occurs after that, reset the Winsock protocol using the command netsh winsock reset.

We hope this helps you fix the Windows Server error when releasing the DHCP lease, that's all good luck.