ashounsome
IS-IT--Management
Our w2k advanced server running proxy services died recently and was rebuilt from the ground up over a period of two days. It was then upgraded to a DC running Active Directory and DNS was installed. All services seem to be running ok apart from the inability for our exchange server to authenticate to it in order to create mailboxes. Two errors are flagged up every couple of minutes in event viewer:-
(1) NetBT Error>A duplicate name has been detected on the TCP network. The IP address of the machine that sent the message is in the data. Use nbtstat -n in a command window to see which name is in the conflict state.
(2) SAM Error>The account-identifier allocator failed to initialize properly. The record data contains the NT error code that caused the failure. Windows 2000 will retry the initialization until it succeeds; until that time, account creation will be denied on this DC. Please look for other SAM event logs that may indicate the exact reason for the failure.
All the info I've found so far on the MS support site leads me around in circles, although it seems to suggest that maybe the server being down for a couple of days has screwed up Active Directory.
(1) NetBT Error>A duplicate name has been detected on the TCP network. The IP address of the machine that sent the message is in the data. Use nbtstat -n in a command window to see which name is in the conflict state.
(2) SAM Error>The account-identifier allocator failed to initialize properly. The record data contains the NT error code that caused the failure. Windows 2000 will retry the initialization until it succeeds; until that time, account creation will be denied on this DC. Please look for other SAM event logs that may indicate the exact reason for the failure.
All the info I've found so far on the MS support site leads me around in circles, although it seems to suggest that maybe the server being down for a couple of days has screwed up Active Directory.
