We had to replace the motherboard and so also NIC on our Proliant ML350 G5.
Is is DC with all FSMO roles.
We didn't realize the BIOS time would be so far off on initial boot and had the network cables attached
We quickly reset the time but now notice problems with replication to the other DC, a Windows 2003 server.
We can browse the shares via IP on the ML350 but netbios name gives us an error
REPADMIN /syncall from ML350 runs okay but the 2003 server has errors.
Is this a Tombstone situation and/or something related to the different MAC address on the ML350 NIC? The IP address is still correct.
Also concerned that I might have "split-brain" AD.
All help is welcome.
Thanks,
Troy