cluster setup checklist thinks its found DHCP address?

I'm setting up a 2003 two node cluster, with 1 physical server (two NIC/4
port) and one virtual server.
The ports are teamed for public and private vlans with NFT for both.

Running the create new cluster option on the physical server, I keep
getting 'the network connection xxx has the following concerns: ....enabled
for DHCP... ...primary IP address cannot be found.

this happens for all four ports.

We checked our internal DNS and the physical server's entry had got stuck
on its original DHCP entry, which has been changed now.

The four ports are set correctly, and the miniports both show their static
IP addresses.
So we're baffled where this DHCP thing is coming from. Any ideas?

I see this all the time with the clusters I build. I always team my main
interfaces for redundancy, however I advise against teaming your Heartbeat.
I believe Microsoft cautions against this as well.

Next remember that when you team your nics a virtual nic appears, however
ever notice the TCP/IP settings for the Nics themselves... no settings right.
Well Cluster Administrator is still going to see the individual nics and
complain however it will see the virtual nic and have no problem doing that.

Now I see this with the Broadcom teaming software, but generally this will
not be an issue and Cluster Admin will ignore the individual nics anyway.