Kind of vague but something here may help.
https://support.microsoft.com/en-us/help/175767/how-multiple-adapters-on-the-same-network-are-expected-to-behave
--please don't forget to Accept as answer if the reply is helpful--
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Win Server 2019 server with 2 nics. I know it's got to be something in the DNS server. But for the life of me I can't find it.
When I ping the server with "ping labserver" I get 192.168.0.2 returned as expected. But when I ping the domain at "ping lab.local" I get 192.168.0.3 returned.I need both to ping 192.168.0.2. What do I need to do?
I've already checked (and had to change) the binding order to put the "Microsoft Windows Network" at the top of the list. But this issue still persists. I've poked around in DNS. But I know enough about DNS to be dangerous. Thanks for any help here.
Kind of vague but something here may help.
https://support.microsoft.com/en-us/help/175767/how-multiple-adapters-on-the-same-network-are-expected-to-behave
--please don't forget to Accept as answer if the reply is helpful--
2nd adapter was used for a VM on Hyper-V at one time. But no longer after reading your link. This issue started when I removed it from the Virtual Switch Manager. Now that I know that, I just disabled the adapter. So far, that "seems" to have alleviated the problem. Won't be convinced until after a server reboot at lunchtime today.
Just a bit of follow up if it's possible. After the lunchtime reboot things still look good. Checked again around 7pm and we're still good. Everything pings as expected, and MFA now works flawlessly again. A check of DNS shows that IP gone also.
My only concern will be if there's a need for a Hyper-V VM in the future, is if using that NIC will cause the issue to return. I would expect not, provided I select DHCP on it initially, and then select the option to not share the adapter with the management OS when setting it up in Hyper-V.
The situation isn't clear but I'd hope the hyper-v host is not also a domain controller.