Hello community,
I've got a pretty strange 'ghost in the system' here lately. I originally thought this was happening only to my Vmware VMs, but turns out even statically assigned workstations are seeing the issue.
If a server/workstation/device has a static ip4 address, most of the time upon reboot I will not be able to use the network, RDP to that device, etc. When I log into the affected system directly and check the status of the adapter, I can see the static IP still, but also an auto-configured ip4 169 address. For instance on a VM I'll need to go into the console and log in, then disable the network adapter and re-enable it. This fixes the problem 100% of the time. Even my own windows 7 workstation has done it to me twice so far.
This issue is specific to static IP devices, DHCP devices work perfect on 2012 R2 DHCP with Failover.
If it matters, we're on Cisco 3750X routers throughout the company.
Thanks in advance for any ideas!
