If you want to add a secondary IP Address without using the Change Adapter Options in the GUI ( especially on Windows Core servers ) you could use sconfig or simply add the IP address with PowerShell.

In my case, I wanted to add a secondary IP address to a certain interface on some Windows Server Core servers. Unfortunately, an Invalid Index error was thrown when I chose the appropriate interface under sconfig – Network Settings:

However, I faced this error a couple of months ago already when I wanted to Disable IPv6 in my test lab.

Because this time it was production servers I didn’t want to change any settings while adding secondary IP addresses to the servers. The only option was to add a secondary IP address via PowerShell.

… and here we go:

Add Secondary IP Address to Network Interface:

List Network Interfaces with name and Interface Index

Display existent IPs on chosen Network Interface

To list IPv4 and IPv6 IP addresses:
Get-NetAdapter -ifIndex  ifIndex Number | Get-NetIPAddress | select IPAddress | ftTo display only IPv4 addresses:
Get-NetAdapter -ifIndex ifIndex Number | Get-NetIPAddress | where {$_.AddressFamily –eq “IPv4”} | select IPAddress

Add new IP address

New-NetIPAddress –IPAddress “IpAddress goes here” –PrefixLength 24 –InterfaceIndex ifIndex Number

The command adds the IP address to the ActiveStore and the Persistent Store.
You can read more about the PolicyStore values here.

Verify that add a secondary IP address was successful

Get-NetAdapter -ifIndex ifIndex Number | Get-NetIPAddress | where {$_.AddressFamily –eq “IPv4”} | select IPAddress

Thats all. You don’t need to specify a default Gateway since this has most likely be done already with the initial IP address.

Remove IP Address from Network Interface:

List Network Interfaces with name and Interface Index

Display existent IP addresses that can be removed on chosen Network Interface

We focus here only on IPv4 addresses. See point above to display IPv6 as well.
Get-NetAdapter -ifIndex ifIndex Number | Get-NetIPAddress | where {$_.AddressFamily –eq “IPv4”} | select IPAddress

Copy IP address to remove from the output.

Remove IP address

add secondary IP address verify

Get-NetAdapter -ifIndex ifIndex Number | Get-NetIPAddress | where {$_.AddressFamily –eq “IPv4”} | select IPAddress

I have compiled the above steps in a script to make it more convenient:

Script to Add/Remove IP Address

The post Add Secondary IP Address Windows Server appeared first on Webbanshee.

For whatever reason you may need to disable IPv6 on Server Core or any other server sometimes.

When I was building my new test lab I wanted all servers to communicate and respond to ping only in IPv4. So I started to disable IPv6 on  Server Core via Powershell.

After this the server responded to ping with its IPv4 address but  SCONFIG  > Network Settings >  Network Adapter Settings showed an Invalid Index.

The solution for me was to enable IPv6 on Server Core again. The server still responds in IPv4 and the Network Adapter Settings are available again.

 
Here are the steps …

Disable IPV6 on Server Core via Powershell:

Check the current status of the Adapter Bindings:

Disable IPV6:

It is possible that  Network Settings > Network Adapter Settings >with SCONFIG will show an invalid index after this:

One answer from a technet forum goes as follows:

( sorry, I just copied the text but do not have the referencing link anymore )

This was what did not work for me   After the IPv4 address was assigned and IPv6 was disabled the server was reachable and responded but the Network Adapter Settings still came with an Invalid Index.
So I enabled IPv6 again and left it this way. Everything works fine until now, the server responds with its IPv4 address.

Enjoy the spring!

 
Add Remove IP addresses despite the Invalid Index error:
Add IP Address Windows Server

The post Disable IPv6 on Server Core with Powershell appeared first on Webbanshee.