really odd one this, i have a dell r710 server on 2008R2 which has a broadcom bcm5709c 4 port NIC.
the 4 ports are all teamed for load balancing and failover and have a static IPv4 set.
regularly (2-3 times a day) the team drops the statically assigned IP and picks up 192.168.10.1 from DHCP. this then for some reason causes an IP conflict message on the server and it updates DNS with the new IP.
the server can still be contacted on the correct IP but as DNS is now wrong you cannot contact it by name until you correct DNS and flush.
as this is an exchange server and it works on names its particularly annoying.
any ideas? im tearing my hair out..
the 4 ports are all teamed for load balancing and failover and have a static IPv4 set.
regularly (2-3 times a day) the team drops the statically assigned IP and picks up 192.168.10.1 from DHCP. this then for some reason causes an IP conflict message on the server and it updates DNS with the new IP.
the server can still be contacted on the correct IP but as DNS is now wrong you cannot contact it by name until you correct DNS and flush.
as this is an exchange server and it works on names its particularly annoying.
any ideas? im tearing my hair out..