Been awhile since I've worked on a NT4.0 server but here goes.
I have rebuilt a BDC due to system failure and on its final run through setup it synchs the securtiy database with the PDC. When NDS for NT is installed it changes a file and causes replication to generate numerous events to be logged and takes a very long time to synch (like a couple of days) If I was to cancel and let the machine come online and finish synching it will also start handling authentication requests and for those that haven't been replicated will fail and give a domain trust failure or access denied.
So my question is is it possible to bring the BDC online and stop the handling of authentication until the SAM database is completelt synchronized. If I stop the netlogon service won't this stop the replication.
KingE
MCP, MCSE-NT4.0
I have rebuilt a BDC due to system failure and on its final run through setup it synchs the securtiy database with the PDC. When NDS for NT is installed it changes a file and causes replication to generate numerous events to be logged and takes a very long time to synch (like a couple of days) If I was to cancel and let the machine come online and finish synching it will also start handling authentication requests and for those that haven't been replicated will fail and give a domain trust failure or access denied.
So my question is is it possible to bring the BDC online and stop the handling of authentication until the SAM database is completelt synchronized. If I stop the netlogon service won't this stop the replication.
KingE
MCP, MCSE-NT4.0
