Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Server won't get past preparing network connections

Status
Not open for further replies.

PRW2000

IS-IT--Management
Aug 24, 2001
45
GB
Hi

I have just updated my windows NT4.0 BDC to win2k server, i patched it and then made it a dc in my domain. However now when i boot the thing up it just sits there saying preparing network connections!


I have gone through the event log and have found the following.

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 Domain Controller. Please look for other SAM event logs that may indicate the exact reason for the failure.

I looked this up on the ms site and it said that this new server had recived some invalid identifiers from the RID master. I have checked this and it appears to be running fine!

Any sugestions greatly appreciated


Regards


Peter
 
You have not followed the proper steps required to perford yor migration. You should go to the microsoft site and get the "Migration cook Book". Also see post "Changing DC in win 2000". Below are the steps in the proper order. I recomend that you take the time to read the cook book before you go any further.



Step:
1)Add a BDC to the domain
2)Document configs of services and apps on PDC'S & BDC'S
3)Back-up services & apps to tape
4)Fully syncronize all BDC'S with PDC
5)Take one fully syncronized BDC off line (put in closet)
6)Keep this BDC offline and available until after migration
7)Upgrade the PDC (this will establish the forest root domain)
8)Upgrade BDC's (any order)


*If you have problems you can remove all w2k and promote the offline BDC to PDC and then bring it back into your network. This new PDC will replicate to any BDC'S that you add to your network , returning the domain to it's previous state.

*Make sure that you do not upgrade your back-up BDC to w2k until your migration is a success.
*Do not switch to native mode until you are sure everything works because you canno't revert back to your old NT 4.0 once you are in native mode
 
Yes i have followed the correct procedure becuase i syncronised and updated my PDC to win2k about 2 months ago i was just trying to bring accross the final bdc when i got this error!

Anyway I have managed to resolve this error it was because the network card in the server was a dual one and although one had a loopback plug init win2k did not like thsi at all! After removing this plug and installing a standard network cable connected back at the switch it boot quite happily now! Just strange how the card functiond happily under NT4.0 but not under 2k!

Thanks for your help anyway!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top