1 of 1 people found this helpful
I confirm that even with PXE Boot disabled in BIOS, the DHCP will still assign the addresses automatically.
I see a lot of confirmation that this is happening, from other posts. But nothing about Intel developing a BIOS update to correct the issue. I even got a suggestion to change the DHCP range on the DHCP sever and set reservations for the MAC addresses. Most of the 60+ workstations purchased with the DP43TF motherboards work fine with DHCP; however, there are a few unique cases which require static IP assignment. DHCP is to ease the administrative burden, not increase administration by setting reservation addresses. It is possible to manually delete the DHCP assignment and manually re-enter the correct static IP address in DNS. However, the next time the PC reboots, during POST it requests (and recieves) DHCP assignment. DHCP then updates DNS entries (removing the static values). When the OS loads, it will run with the static assignment; however those applications which use DNS forward and reverse lookup find the DHCP assigned address. This causes the application to fail or produce erroneous conditions.
These motherboards are in PCs assembled by a third party vendor and I cannot place a warranty claim against Intel to be the BIOS changed to operation as would be appropriate.
I'm having the same problem with the BIOS getting an IP number for the LAN card even with a static IP set in the OS. When will there be a BIOS update to fix this problem? I have 48 computers that are taking IP numbers from my DHCP server needlessly. Please help.