I had a failure on a 2008R2 guest which I had to restore from backups (we use veeam). The restore went fine but after I fired up the guest, it can't communicate on the orginal subnet. We use 192.168.99.0/24 for the network this guest is on. We have multiple vlans and if I give the server an address on any network besides the one that was statically assigned when the server crashed, it pings and works perfectly. This particular server is a DC/DHCP/DNS for the .99 vlan so simply using the other subnet isn't really an option.
I've tried changing/adding other network adapters as well as Legacy network adapters. No change. I've also shut the server down, removed all NIC adapters, restarted then deleted all the TCP/IP profiles in the registry. Shut down the server and added a network adapter again. Same symptoms.
I would really hate to have to replace this server as it fills a few roles for this subnet and business needs but I have to get it running. Any advice or things to try?