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

Arranda Saputra 6 Reputation points
2021-06-17T10:33:02.35+00:00

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

Windows for business | Windows Server | User experience | Other
{count} vote

4 answers

Sort by: Most helpful
  1. Anonymous
    2021-06-17T12:29:26.14+00:00

    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?

    1 person found this answer helpful.

  2. Jiang Zhang 811 Reputation points
    2021-06-23T04:39:45.923+00:00

    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.

    1 person found this answer helpful.

  3. Anonymous
    2021-06-17T12:34:55.983+00:00

    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--


  4. Anonymous
    2021-06-17T12:50:23.857+00:00

    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 No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.