I have a vanilla Windows 2003 SP2 installation (using MS Media) installed on an HP DL380 G6 (using Broadcom nics).
When I boot the machine unattached to a domain, there are no issues. As soon as I join the machine to another vanilla domain server and reboot, I begin getting event id 1053 ("Windows cannot determine the user or computer name. (). Group Policy processing aborted.") logged. The other errors are such that DHCP logs an error that it cannot lease an IP and assigns the default 169 address.
Once the machine is booted, though, and I'm able to log in, the machine has already rechecked and leased it's DHCP address and applied the Group Policies. I will be using this machine to run SQL Server and VMWare vCenter, so I installed those applications and reboot. The above error prevents SQL and vCenter from starting at boot time.
Now, the crazy thing is that if I disable/reenable the NIC and reboot before the NIC recovers it's DHCP lease, the system boots with no error. If I reboot while the NIC is functioning and active, the error manifests itself.
I've read there might be an issue with the Broadcom NICs and Server 2003 SP2, but I've tried the tweaks and they don't seem to work.
Any suggestions would be greatly appreciated.