How to Set Up Windows Server 2016 Network Adapter

Configuring the network adapter correctly on Windows Server 2016 is one of the first and most critical tasks after installation. A server that uses DHCP for its IP address can cause connectivity disruptions whenever the lease changes. This guide covers assigning a static IP address, configuring DNS settings, setting up NIC teaming for redundancy, and verifying network connectivity using PowerShell and GUI tools.

Step 1: Identify Network Adapters

Before configuring any settings, identify all network adapters installed in the server. Open PowerShell as Administrator and run:

# List all network adapters with their status
Get-NetAdapter | Select-Object Name, InterfaceDescription, Status, MacAddress, LinkSpeed

# Show adapter index numbers (useful for some commands)
Get-NetAdapter | Select-Object Name, InterfaceIndex

Note the Name field for the adapter you want to configure. Common names are “Ethernet”, “Ethernet 2”, or similar. You can rename adapters to more meaningful names for clarity.

# Rename a network adapter
Rename-NetAdapter -Name "Ethernet" -NewName "LAN"
Rename-NetAdapter -Name "Ethernet 2" -NewName "Management"

Step 2: Remove Existing DHCP Configuration

If the adapter currently has a DHCP-assigned address, remove it before assigning a static address to avoid conflicts:

# Remove existing DHCP IP address
Set-NetIPInterface -InterfaceAlias "LAN" -Dhcp Disabled

# Remove any existing IP addresses from the adapter
$ifIndex = (Get-NetAdapter -Name "LAN").InterfaceIndex
Get-NetIPAddress -InterfaceIndex $ifIndex | Remove-NetIPAddress -Confirm:$false

# Remove existing default gateway routes for this adapter
Get-NetRoute -InterfaceAlias "LAN" | Where-Object { $_.NextHop -ne "::" -and $_.NextHop -ne "0.0.0.0" } | Remove-NetRoute -Confirm:$false

Step 3: Assign a Static IP Address

Assign a static IPv4 address, subnet mask (expressed as prefix length), and default gateway:

# Assign static IP address
# PrefixLength 24 = 255.255.255.0 subnet mask
New-NetIPAddress `
    -InterfaceAlias "LAN" `
    -IPAddress 192.168.1.10 `
    -PrefixLength 24 `
    -DefaultGateway 192.168.1.1

# Verify the IP was assigned
Get-NetIPAddress -InterfaceAlias "LAN" -AddressFamily IPv4

Step 4: Configure DNS Server Addresses

Set primary and secondary DNS server addresses. On a domain-joined server, the primary DNS should point to your Active Directory DNS server:

# Set primary and secondary DNS servers
Set-DnsClientServerAddress -InterfaceAlias "LAN" -ServerAddresses ("192.168.1.1", "8.8.8.8")

# Verify DNS configuration
Get-DnsClientServerAddress -InterfaceAlias "LAN"

# Test DNS resolution
Resolve-DnsName "google.com"

Step 5: Disable IPv6 If Not Required

In environments that do not use IPv6, disabling it on the adapter can reduce complexity and prevent unintended IPv6 traffic:

# Disable IPv6 on a specific adapter
Disable-NetAdapterBinding -Name "LAN" -ComponentID ms_tcpip6

# Verify IPv6 is disabled
Get-NetAdapterBinding -Name "LAN" -ComponentID ms_tcpip6

Step 6: Configure NIC Teaming for Redundancy

NIC teaming combines multiple physical network adapters into a single logical adapter for redundancy or increased bandwidth. Windows Server 2016 includes built-in NIC teaming support. This requires at least two physical network adapters.

# View available adapters for teaming
Get-NetAdapter | Where-Object { $_.Status -eq "Up" }

# Create a NIC team named "Team1" using two adapters
New-NetLbfoTeam -Name "Team1" -TeamMembers "Ethernet","Ethernet 2" -TeamingMode SwitchIndependent -LoadBalancingAlgorithm Dynamic

# Check team status
Get-NetLbfoTeam
Get-NetLbfoTeamMember -Team "Team1"

# Assign a static IP to the team adapter
New-NetIPAddress -InterfaceAlias "Team1" -IPAddress 192.168.1.10 -PrefixLength 24 -DefaultGateway 192.168.1.1
Set-DnsClientServerAddress -InterfaceAlias "Team1" -ServerAddresses ("192.168.1.1","8.8.8.8")

Step 7: Set Network Profile

Windows assigns a network location profile (Domain, Private, or Public) to each connection. Servers in a domain environment should use the Domain profile. Check and set it if needed:

# Check current network connection profile
Get-NetConnectionProfile

# Set to Private if not on a domain (standalone server)
Set-NetConnectionProfile -InterfaceAlias "LAN" -NetworkCategory Private

Step 8: Verify Network Connectivity

After configuration, test connectivity to ensure the adapter is working correctly:

# Ping the default gateway
Test-NetConnection -ComputerName 192.168.1.1

# Ping an external address
Test-NetConnection -ComputerName 8.8.8.8

# Trace route to verify path
Test-NetConnection -ComputerName google.com -TraceRoute

# Show full adapter configuration summary
Get-NetIPConfiguration -InterfaceAlias "LAN"

Step 9: Configure MTU Size (Advanced)

In some environments (such as those using VPNs or jumbo frames), you may need to adjust the Maximum Transmission Unit (MTU) size:

# View current MTU
netsh interface ipv4 show subinterfaces

# Set MTU to 1500 (standard Ethernet) on the LAN adapter
netsh interface ipv4 set subinterface "LAN" mtu=1500 store=persistent

# For jumbo frames (requires switch support), set to 9000
netsh interface ipv4 set subinterface "LAN" mtu=9000 store=persistent

Step 10: Enable Network Adapter Jumbo Frames (Optional)

If your network infrastructure supports jumbo frames, enable them on the adapter to improve throughput for large file transfers:

# View advanced adapter properties
Get-NetAdapterAdvancedProperty -Name "LAN" | Select-Object DisplayName, DisplayValue

# Enable jumbo frames (value varies by driver, 9014 bytes is typical)
Set-NetAdapterAdvancedProperty -Name "LAN" -DisplayName "Jumbo Packet" -DisplayValue "9014 Bytes"

The network adapter is now fully configured. With a static IP address, proper DNS settings, and optionally NIC teaming, Windows Server 2016 is ready for reliable network communication. Always document the IP address, subnet, gateway, and DNS settings assigned to each server for future reference.