MSDN Community / Discussions / Windows IoT
My Profile

Network Configuration Guide & Tips

Table of Contents

Overview

This guide walks you through configuring network interfaces on Windows IoT Core devices, covering both wired and wireless scenarios. It also provides troubleshooting steps for common connectivity issues.

IP Configuration

Use the netsh command or PowerShell New-NetIPAddress to set static IPs or obtain them via DHCP.

# Set static IP (PowerShell)
New-NetIPAddress -InterfaceAlias "Ethernet" -IPAddress 192.168.1.50 -PrefixLength 24 -DefaultGateway 192.168.1.1

# Enable DHCP (netsh)
netsh interface ipv4 set address name="Wi‑Fi" source=dhcp

Verify the configuration with ipconfig /all.

DNS Settings

Update DNS servers to ensure reliable name resolution:

# PowerShell
Set-DnsClientServerAddress -InterfaceAlias "Ethernet" -ServerAddresses ("8.8.8.8","8.8.4.4")

Wi‑Fi Setup & Troubleshooting

Connect to an SSID using netsh wlan or the Wi‑Fi UI on the device.

# Add a Wi‑Fi profile
netsh wlan add profile filename="C:\WiFi\myprofile.xml"

# Connect
netsh wlan connect name="MyNetwork"

If you encounter connection drops, try the following:

  • Check signal strength (RSSI ≥ -70 dBm recommended).
  • Ensure the network uses WPA2‑PSK; older protocols may be disabled.
  • Update the device’s Wi‑Fi driver from the Windows IoT catalog.

Ethernet & POE

Ethernet should work out‑of‑the box. For Power‑over‑Ethernet, confirm that the switch supplies adequate power (up to 15.4 W for standard PoE).

If the link is down:

  • Verify cable integrity (test with a known‑good cable).
  • Confirm the NIC isn’t disabled: Get-NetAdapter.
  • Check the switch port configuration (VLAN, speed/duplex).

Windows IoT Firewall

Open required ports for IoT device communication (MQTT 1883, HTTP 80, HTTPS 443).

# PowerShell – allow MQTT inbound
New-NetFirewallRule -DisplayName "Allow MQTT" -Direction Inbound -Protocol TCP -LocalPort 1883 -Action Allow

Quick Tips & Common Pitfalls

  • Always test with a static IP first. This isolates DHCP issues.
  • Use ping and tracert to verify connectivity to the gateway and external DNS.
  • Check the device’s time/date. Incorrect system time can cause TLS handshake failures.
  • When troubleshooting Wi‑Fi, disable Power‑Saving mode on the radio (Set-NetAdapterAdvancedProperty).
  • Log network events with Get-WinEvent -LogName Microsoft-Windows-Networking-Operational.

Discussion