Windows 8.1 and Windows 10 TCP/IP Static IP bug
This article identifies a bug found in Windows 8.1 and Windows 10 related to networking. For most users, this is not a problem as most users use DHCP to obtain an IP address. But for the few of us that need to set a static IP address, this becomes a problem.
Have not seen this problem on Windows 8 which indicates that something has changed in Windows 8.1 and later.
Operating systems confirmed that are affected by this:
- Windows 8.1 Professional
- Windows 8.1 Enterprise
- Windows 10 preview
Symptoms:
When Windows 8.1 or later is using DHCP to obtain an IP address is configured with a static IP address, after applying the settings from the command line using ipconfig/all you can confirm the settings as in my example below. At first glance, all looks fine. When viewing the static IP address from the adapter we cannot see the static IP address as Windows shows it is configured for DHCP. But do another ipconfig/all and you can see the static IP address that was configured as static but the results show the adapter is configured for DHCP.
In some cases two gateways. If you configure a static IP with a new gateway you will see two gateways when using ipconfig /all. This bug was introduced in Windows 8.1 and have not been present in Windows 8, Windows 7 and earlier.
Using DHCP
Wireless LAN adapter Wi-Fi:
Connection-specific DNS Suffix . : telecom
Description . . . . . . . . . . . : Broadcom 802.11ac Network Adapter
Physical Address. . . . . . . . . : 6C-71-D9-F2-1F-A2
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::40c5:da4d:9fdb:4f78%19(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.75(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Thursday, 28 May 2015 9:21:34 a.m.
Lease Expires . . . . . . . . . . : Friday, 29 May 2015 9:21:33 a.m.
Default Gateway . . . . . . . . . : 192.168.1.254
DHCP Server . . . . . . . . . . . : 192.168.1.254
DHCPv6 IAID . . . . . . . . . . . : 57438681
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1B-AA-5B-AF-64-51-06-04-D9-B0
DNS Servers . . . . . . . . . . . : 192.168.1.254
NetBIOS over Tcpip. . . . . . . . : Enabled
**
Using Static
**
Wireless LAN adapter Wi-Fi:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom 802.11ac Network Adapter
Physical Address. . . . . . . . . : 6C-71-D9-F2-1F-A2
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::40c5:da4d:9fdb:4f78%19(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.22(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.254
DHCPv6 IAID . . . . . . . . . . . : 57438681
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1B-AA-5B-AF-64-51-06-04-D9-B0
DNS Servers . . . . . . . . . . . : 192.168.1.254
8.8.8.8
NetBIOS over Tcpip. . . . . . . . : Enabled
**
Using Static 2nd view**
Wireless LAN adapter Wi-Fi:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom 802.11ac Network Adapter
Physical Address. . . . . . . . . : 6C-71-D9-F2-1F-A2
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::40c5:da4d:9fdb:4f78%19(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.22(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.254
DHCPv6 IAID . . . . . . . . . . . : 57438681
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1B-AA-5B-AF-64-51-06-04-D9-B0
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Enabled
TCP/IP does not show the static IP address configured earlier.
Two Gateways after configuring static IP address with different gateway than what the DHCP server handed out. IPconfig shows DHCP is not enabled but TCP/IP GUI shows DHCP is configured.
From here on your networking will be a big mess.
Resolution:
To resolve, a computer restart is the easiest for most users.
Advanced users might want to try the following from an elvated command prompt:
netsh int ip set address "Wi-Fi" static 10.2.1.158 255.255.254.0 10.2.0.250 (set a static IP address on the affected adapter. In my case this was the Wi-Fi adapter)
netsh int ip set address "Wi-Fi" DHCP (now for this adapter to use DHCP to obtain an IP address)
netsh int ip reset netsh interface set interface Wi-Fi disabled (Disable the adapter)
netsh interface set interface Wi-Fi enabled (Enable the adapter)
Adapter now successfully gets a DHCP IP address again and the second gateway removed.