Weird DHCP/subnet problem on dual NIC

[tmcc]

I recently installed a pair of dual nic HP SFP cards for my VMs. Initially, it was fine. Somehow, after a weekend reboot, one of the adapters no longer connects to the correct gateway or sub-net. I am baffled and really don't even understand what I am supposed to search in order to correct this.

You can see below that the adapter for Ethernet 9 is connecting to a different subnet for some inexplicable reason and has not attached a gateway. That Ethernet 9 is a physical adapter.

Keep in mind that Ethernet 8 and Ethernet 9 are on the same physical card. Please also keep in mind that my DHCP server lists the physical address of the adapter with a valid IP address (10.0.0.202).

I already broke the NIC team to try to figure this out. I have tried a simple trial and error to eliminate possible reasons. I have tried manually setting the gateway, subnet, IP and DNS but it doesn't ever "take". Other things I've tried out of desperation include swapping cables, switches, order of cable plugging, different cables in different ports, reboots etc.

Below is a screenshot of the ipconfig /all.

When I try to release #9, it tells me:

Windows IP Configuration
An error occurred while releasing interface Ethernet 9 : An address has not yet been associated with the network endpoint.

When I try to renew #9 it tells me:

Windows IP Configuration
An error occurred while renewing interface Ethernet 9 : The name specified in the network control block (NCB) is in use on a remote adapter.
The NCB is the data.

I'm afraid that this has me baffled. Any wizards know what to make of this?

 

[RaDiKaL_]

The 169.254.x.x IP range is the one a computer will set to itself when it fails to contact its DHCP server, so you need to check the connection (physical or virtual) between your Ethernet 9 and whichever its DHCP server is.

 

[ingtar33]

ethernet 9 indicates ZERO internet. (169.254.x.x means no internet on a DHCP) Either its a cable issue or a hardware failure. Either way that card isn't detecting anything. You could try to manually configure it with a static ip/gateway (which is something you should do normally anyway), but if that's not "taking" then there is a serious hardware issue.

 

[Rhinofart]

What is your VM platform? I have had ESXi servers swap hardware around on me during a reboot. I had to manually correlate what physical adapter was mapped to which Virtual Adapter, and make adjustments in the ESXi config as needed. It was really really annoying.

 

[Rhinofart]

ethernet 9 indicates ZERO internet. (169.254.x.x means no internet on a DHCP) Either its a cable issue or a hardware failure. Either way that card isn't detecting anything. You could try to manually configure it with a static ip/gateway (which is something you should do normally anyway), but if that's not "taking" then there is a serious hardware issue.

169.254.x.x doesn't mean no internet. What that indicates is that the network connection is up and running, it's configured for DHCP, but it's not receiving any DHCP information from the server. 169.254.x.x IP scheme is reserved for APIPA (ad-hoc networks with no formal infrastructure)