Recently I faced a strange issue where one of my virtualized client operating system in VMware started getting APIPA IP even though I configured a static IP address from assigned pool. Which caused no network access at all. Even I got a popup saying “Conflict IP Address” Here is how I fixed this problem.

To figure out this problem follow this procedure

Open: Run > cmd > ipconfig /all

You may see the following issues:

or:

Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) 82567LM-3 Gigabit Network Connection
Physical Address. . . . . . . . . : 00-50-55-08-30-57
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::8508:6cb9:5112:f8c9 (Preferred)
Autoconfiguration IPv4 Address. . : 169.254.248.201(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.0.0
IPv4 Address. . . . . . . . . . . : 192.168.1.136(Duplicate)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.1
NetBIOS over Tcpip. . . . . . . . : Enabled

To fix it, enter these from Command Prompt:

C:\Users\Administrator> netsh interface ipv4 show inter

This command will produce something like this result:

Idx Met MTU State Name
-------------------------------------------------------
1 50 4294967295 connected Loopback Pseudo-Interface 1
11 10 1500 connected Local Area Connection

11: <= Note this Ethernet ID Number

Now run the following command:

C:\Users\Administrator> netsh interface ipv4 set interface 11 dadtransmits=0 store=persistent

It will produce a result saying Ok. Next we need to disable the DHCP Service from Services to stop getting IP address from DHCP and keep using Static IP address. For this purpose we shall be opening the Services console and select DHCP Client Service and stop it.

Run > services.msc > disable DHCP Client service

Now make sure you disable this service also to prevent it’s automatic start when operating system starts.

Finally, restart your guest operating system and enjoy the restored connectivity.

Good luck!
Hassan

We have publised an updated article with more details. Read More here

About the author

Hassan Latif

A Microsoft Certified Trainer, a hobby blogger and geek

Leave a Comment