Skip to main content

Configure a Failover IP on Windows

This guide explains how to add a Failover IP to your Windows server, either through the graphical interface or the command line.

Prerequisites​

  • Administrator access to your Windows server (via RDP)
  • A Failover IP assigned to your server

Important: before making any change, note your current network configuration (IP address, mask, gateway and DNS). Switching the interface to manual configuration without filling in these values would result in a loss of RDP connection.

Note the current configuration​

  1. Connect to your server via RDP.
  2. Open a Command Prompt (cmd) and run: 
    ipconfig /all
  3. Note the IPv4 address, subnet mask, default gateway and DNS servers of your main interface.

Method 1 — Graphical interface​

  1. Open the network connections:
    • Press Windows + R, type ncpa.cpl then confirm.
  2. Right-click your network adapter (for example "Ethernet") then select Properties.
  3. Select Internet Protocol Version 4 (TCP/IPv4) then click Properties.
  4. Check Use the following IP address and fill in the IP address, mask and gateway noted earlier (as well as the DNS servers).
  5. Click Advanced….
  6. In the IP Settings tab, under IP addresses, click Add….
  7. Enter your Failover IP with the subnet mask 255.255.255.255, then click Add.
  8. Confirm with OK on each window.

If the new IP doesn't respond immediately, disable then re-enable the network adapter (right-click the adapter → Disable, then Enable).

Method 2 — Command line (netsh)​

You can also add the Failover IP through a Command Prompt or PowerShell opened as administrator.

  1. Identify your interface name:

    netsh interface ipv4 show interfaces

    (for example "Ethernet")

  2. Add the Failover IP:

    netsh interface ipv4 add address "Ethernet" YOUR_FAILOVER_IP 255.255.255.255

    Replace Ethernet with your interface name and YOUR_FAILOVER_IP with your IP.

Verification​

  1. Check that the IP is present:

    ipconfig

    The Failover IP should appear as an additional IPv4 address on your interface.

  2. Test connectivity from another machine by running a ping to the Failover IP.

Troubleshooting​

  • Make sure the Failover IP is properly assigned to your server in your customer area.
  • Verify that no other server is already using this IP (address conflict).
  • Check that the subnet mask is indeed 255.255.255.255.
  • Check the Windows Firewall rules if some services don't respond on the new IP.

Important notes​

  • The Failover IP must be configured with a subnet mask 255.255.255.255.
  • A Failover IP can be moved from one server to another from your HostMyServers customer area.
  • Some services may require reconfiguration to listen on the new IP.