IPv4 Address Autoconfiguration Solution

Solution to Overcome Autoconfiguration IPv4 address - 2016, Sometimes if we use a LAN network at the office there is an IP conflict or for no apparent reason our IP has been set to static but after seeing it turns out that the IP we set is different from the one that is running so that even though we have set the IP accordingly it doesn't will be able to connect to the internet.

On this occasion, the admin will provide a way to resolve conflicting IP addresses or Autoconfiguration IPv4 addresses that are different when set. Indeed, this problem is a bit difficult to explain, but for those of you who feel that you have set a static IP and the internet is still not working, you can follow the method that we will discuss below.

Problem Indication

The PC cannot be connected to the internet (cable) even though the settings have been adjusted accordingly. When we look at the details of the IP address, there is something strange, namely the information "Autoconfiguration IPV4 address: xxx.xxx.xxx.

Sometimes there are also those who experience that when they are connected to the internet a notification "Ip Address Conflict" suddenly appears.

Or if you don't know, you can find out the problem with the ipconfig /all command. How, Click start> Run | or press CTRL+R and type CMD press enter. CMD window will appear then type ipconfig /all then press enter.

If you see that the Autoconfiguration IPv4 results are different from the IP address that we set, then that's the cause.

First Solution - CMD

The first way to solve the ip address auto configuration problem is to use the CMD / Command Prompt command. Press CTRL + R then type CMD and hit enter. Enter command

netsh interface ipv4 show inter

The result will come out like this:

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

Well, this number 11 may be different on each PC, but it's the numbers in this section that you must remember because we will use this number later.

Next, type this command in CMD:

netsh interface ipv4 set interface 11 dadtransmits=0 store=persistent

If so, the last step we need to do is to disable the DHCP client. The trick is to press CTRL + R then type Services.msc and press enter.

Well, this number 11 may be different on each PC, but it's the numbers in this section that you must remember because we will use this number later.

Next, type this command in CMD:

netsh interface ipv4 set interface 11 dadtransmits=0 store=persistent

If so, the last step we need to do is to disable the DHCP client. The trick is to press CTRL + R then type Services.msc and press enter.

Double click on DHCP Client then on Startup type select Disable. Now you can restart your PC and see the results.

Second Solution - Uninstall the driver

If the first method doesn't work to solve the problem of auto configuration ipv4 addresses, then the thing we can do is reset all the networking settings that we have. The easiest way is to remove the Ethernet/LAN driver, but this method requires an internet connection later, so you can prepare a usb modem first. The method is:

Open control panel > search for Device Manager. then you look for ethernet / LAN drivers.

Then if you have found the network adapter device, look for the ethernet / LAN then right click and select uninstall.

Don't worry, after you uninstall it, we can restore it by pressing the "Search for new hardware" button on the menu bar, the driver will automatically be reinstalled (must be connected to the internet). After that you can restart the PC and the cable connection will work again.

That's the solution to overcoming the ipv4 address Auto configuration on Windows, it's quite easy, isn't it? I hope that after practicing the above your problem can be solved.