Alex Ruben
How To Add Multiple IP Addresses to a Windows Server 2025 Network Adapter
If you’re like me, trying to run multiple services on one server without throwing down extra hardware sounds perfect—except when it comes to IP addresses. Sometimes, Windows Server 2025 just doesn’t want to play nice with adding more IPs through the GUI or it’s a bit clunky. But honestly, configuring multiple IPs isn’t too crazy once you get the hang of it. It can help with network segmentation, hosting different sites, or just avoiding port conflicts. This guide is all about making that process a lot less painful.
How to Fix Adding Multiple IPs to a Network Adapter in Windows Server 2025
Access the network adapter properties with PowerShell
On one of my setups, using PowerShell did the trick way faster than digging through menus. Open up PowerShell as admin—Win + X and choose Windows PowerShell (Admin). Then, find your network adapter name first with:
Get-NetAdapterThis command shows all network interfaces. Copy the exact name, like “Ethernet” or “Wi-Fi”. Now, to add additional IP addresses, you can use the command:
New-NetIPAddress -InterfaceAlias "Ethernet" -IPAddress 192.168.1.25 -PrefixLength 24This adds a new IP. Repeat it with different IPs and subnet prefixes as needed. I’ve noticed sometimes the GUI just doesn’t save these new IPs properly, but PowerShell more reliably sticks them on. Plus, no need to restart—I think Windows just applies changes instantly, but check after.
Use Network Settings UI for Visual Confirmation & Troubleshooting
If you prefer the GUI, go to Start > Settings > Network & Internet. Hit Change adapter options under Advanced network settings. Right-click on your adapter and pick Properties. Find Internet Protocol Version 4 (TCP/IPv4), then click Properties. Next, click the Advanced button. Here, in the IP Addresses list, you can add IPs without fuss. Just click Add, punch in the IP and mask (like 255.255.255.0), then OK everything.
Be sure to check your current IPs with ipconfig in Command Prompt after you finalize. Sometimes, the GUI can bug out or might not show changes immediately. On some machines, it took a reboot or a network restart—so don’t be surprised.
Why it works and when to use it
This method applies when your server has a static IP and you need more than one IP for hosting multiple apps, segmentation, or testing. It helps prevent port conflicts and gives more control without extra hardware. It’s kinda frustrating when Windows defaults to one IP — but with a few tweaks here and there, you can have multiple IPs working smoothly. I’ve seen it work almost instantly after the command, but sometimes, Windows acts funny—especially if the network adapter is stubborn or if there’s a conflicting IP somewhere else in your network. Keep an eye on conflicts, though, because duplicates are trouble.
How to verify the new IPs are added successfully
Run ipconfig from Command Prompt. Your new IP addresses should be listed under your adapter. If they’re not, check your command syntax, network settings, or consider a quick reboot of the network adapter via:
Disable-NetAdapter -Name "Ethernet" -Confirm:$false
Enable-NetAdapter -Name "Ethernet"This can force Windows to re-read the new IP configs. Honestly, sometimes Windows just needs a kick to recognize the changes, even if they’re already applied.
Extra tips & common issues to watch for
- Make sure the IPs are within the same subnet unless you explicitly want different subnets (sometimes that’s necessary for multi-site setups).
- Check for existing IP conflicts — don’t assign an IP that’s already in use somewhere else; that’s a classic cause for network chaos.
- If services are acting weird or not binding to new IPs, verify their network bindings or IP listen settings. Some services, like IIS, need manual configuration to listen on multiple IPs.
Wrap-up
Basically, adding multiple IP addresses can be a pain if you rely only on the GUI, but PowerShell makes it much easier and more reliable. Sometimes all it takes is a quick command, or walking through the advanced TCP/IP settings, to get those IPs assigned correctly. Just be aware of network conflicts or subnet mishaps, and everything should be smooth sailing.
Summary
- Use
Get-NetAdapterto identify your interface. - Add IPs quickly with
New-NetIPAddressin PowerShell. - Or use the GUI: Network & Internet > Change adapter options, then Properties > TCP/IPv4 > Advanced.
- Check with
ipconfigafterwards to verify. - Watch for conflicts or binding issues with services.