Windows Server 2016 static IP shown as 169.x.x.x (APIPA) in ipconfig

Question

Windows Server 2016 static IP shown as 169.x.x.x (APIPA) in ipconfig

Arranda Saputra 6

I have a windows server 2016 with two network adapter. Both are assigned static address and do not overlap. The first adapter never have issue but the second adapter is always changed to 169.x.x.x (apipa) after restart.
If we look at the adapter properties, the statically configured ip address is actually still there. The workaround is to set it to dynamic and then return it to static , it will stay until the next reboot. Now I think i’m tired enough to do this repeatedly for dozens of server. Anyone can sort this out? Really appreciated all inputs. Thanks

Fyi… first adapter ip 10.x.x.x /24 , default gateway 10.x.x.1
Second adapter ip 192.168.x.x /24, no default gateway

Jiang Zhang 821 Reputation points

2021-06-18T07:05:31.61+00:00

Hi

I'm currently working with your case, and i will get back to you as soon as possible.

Mulder
Jiang Zhang 821 Reputation points

2021-06-25T09:43:17.163+00:00

Hi，

You could accept the useful reply as answer if you want to end this thread up.
If there is anything else i can do for you, please feel free to post in the forum.

Mulder
Jiang Zhang 821 Reputation points

2021-07-02T02:10:48.32+00:00

Hi,
Just checking the update of the case? Is there anything else i can do for you? Please feel free to post.

Best Regards,
Mulder Zhang

4 answers

Your answer

Jiang Zhang 821 Reputation points

2021-06-18T07:05:31.61+00:00

Hi

I'm currently working with your case, and i will get back to you as soon as possible.

Mulder
Jiang Zhang 821 Reputation points

2021-06-25T09:43:17.163+00:00

Hi，

You could accept the useful reply as answer if you want to end this thread up.
If there is anything else i can do for you, please feel free to post in the forum.

Mulder
Jiang Zhang 821 Reputation points

2021-07-02T02:10:48.32+00:00

Hi,
Just checking the update of the case? Is there anything else i can do for you? Please feel free to post.

Best Regards,
Mulder Zhang

Answer 1

Jiang Zhang 821

Hi,

Windows probes for a tentative IP address at the same time the switch is probing for device status. This is usually triggered by rebooting which results in a duplicate ip address. To prevent the duplicate ip address on the network the windows system assigns an APIPA address to the adapter. (ie. 169.254. x.x)

In my opinion, you may try the following workaround:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
Set ArpRetryCount (32-bit DWORD) to 0

Hopefully, it can help and looking forward to your feedback.

Best Regards,
Mulder Zhang

--------------------------------------------------------------

If the Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Robert Ehlenfield 0 Reputation points

2024-01-07T01:42:31.4366667+00:00

Enabling Spanning Tree on the network switches (HPE/Aruba) did not resolve this issue.

I did not have this issue with servers that are connected to Cisco or Dell switches.

** This registry entry resolved the issue for my Dell servers with Broadcom NICs that were showing the domain network as "Unidentified" until the adapters are disabled & enabled.

Nice work, Mulder Zhang.

Answer 2

Anonymous

the statically configured ip address is actually still there

Where are you seeing this and where do you see the problem? What roles have been installed?

Arranda Saputra 6 Reputation points

2021-06-17T12:32:03.847+00:00

The problem is the secondary adapter has no connectivity to the network that it is supposed to connect.
So if i run cmd and issue command “ipconfig” the second adapter will show its ip address as APIPA
While in fact if i look at the adapter properties > tcp/ipv4 > i can still see the static ip configured there

Have you ever experienced such thing?

Answer 3

Anonymous

I'd still confirm the hardware supports Server 2016. A hypervisor does not insulate from meeting requirements.

--please don't forget to upvote and Accept as answer if the reply is helpful--

0 comments

Answer 4

Anonymous

Sounds like problematic hardware or drivers. I'd check here and with manufacturer about support for the operating system installed.
https://www.windowsservercatalog.com/

also check the server manufacturer's site for updated firmware, ROM bios, chipset and driver support pack.

--please don't forget to upvote and Accept as answer if the reply is helpful--

Arranda Saputra 6 Reputation points

2021-06-17T12:46:40.427+00:00

Sorry forgot to mention this is a VM
(Vmware esxi 7.0)
David Sain 1 Reputation point

2022-08-11T19:22:31.027+00:00

I had a very similar issue. ESXi 7 VM (Server 2012 R2 ADDS restored from backup) with static IP would show the APIPA address as preferred and still show the secondary static IP. I reinstalled VMware tools to bring it up to the latest drivers. No dice.

Found our NOC had turned on the original server in an attempt to bring them back up and since the server detected a duplicate IP, it reverted to APIPA. I would have preferred a Duplicate IP notification because it would have made a little more sense...

Share via

Windows Server 2016 static IP shown as 169.x.x.x (APIPA) in ipconfig

4 answers

Your answer