Hello,
Thank you for posting in Q&A forum.
In Hyper-V Server 2019, if a virtual machine (VM) gets an IP address of 169.254.x.x, it usually means that the virtual machine failed to get a valid IP address through the DHCP server and instead used an automatic private IP address. Here are some possible causes and solutions:
- Open Hyper-V Manager and check the settings of the virtual switch to make sure it's connected to the correct physical network adapter.
- Make sure that the virtual machine's network adapter is properly connected to the virtual switch.
Check the type of virtual switch (external, internal, or private) and make sure that an external switch is selected to connect to the physical network.
- Make sure there is a DHCP server available on the network and that it is running.
Check the configuration of the DHCP server to make sure that it is able to assign IP addresses to virtual machines.
If the DHCP server is unavailable, you can try manually configuring the IP address of the virtual machine to ensure that it is within the valid range of the network.
- In the virtual machine, try restarting the network service, using the commands ipconfig /release and ipconfig /renew to force a new IP address.
- Check the firewall settings of the Hyper-V host and virtual machine to make sure that DHCP traffic is not being blocked.
Ensure that network security groups or other security settings do not restrict network access to virtual machines.
- Make sure the drivers for your Intel i210 network adapter are up-to-date and compatible with Hyper-V.
Make sure that the physical network connection is working and check the status of the switch and router.
I hope the information above is helpful.
If you have any questions or concerns, please feel free to let us know.
Best regards,
Jill Zhou
If the Answer is helpful, please click "Accept Answer" and upvote it.