The problem we are getting on our main DC is a slow bootup time of 10 minutes and its slow during the "Setting up network connections" part. When the event logs are checked we are getting an error of: Event Type: Error Event Source: DhcpServer Event Category: None Event ID: 1059 Date: 3/24/2006 Time: 9:04:56 PM User: N/A Computer: TFPDCS2 Description: The DHCP service failed to see a directory server for authorization. Our setup is: Server 1 is the main DC which runs DNS, DHCP, WINS with Active Directory installed. on it. Server 2 is the secondary DC in case Server 1 goes down, it is our file and print server. It has Active Directory installed also, and runs DNS, has DHCP but DHCP is turned off at the moment unless Server 1 goes down. Server 3 has Exchange server installed and strictly that, no DHCP, DNS, or Active Directory. Server 4 has SQL Server installed only, no AD, DNS, or DHCP installed or activated Server 5 is a development server and nothing else, no AD, DNS or DHCP installed or actived. The only 2 servers (Server 1 and Server 2) are the only servers that have Active Directory, DNS, DHCP, WINS on them, they both have global catalog on them. We are wondering if the problem could be that when server 1 starts up, its trying to find server 2 and in turn is hanging for around 10 to 15 minutes until it times out. Is there a way to change the time so that Server 1 will stop searching for Server 2 after say 10 seconds? Or could it be another issue altogether? Thanks in advance, Cody

Sorry forgot to add all on the same domain and servers are all 2003 Server

"The DHCP service failed to see a directory server for authorization." Means your AD is probably not kosher. Run DCDiag on your DC's and look for failures. I'm guessing DNS issues. "It happens."

Here's the results of running DCDiag on the Main DC and I don't see anything wrong with the report, unless I'm missing something. I didn't run it on the 2nd DC because we're not getting any kind of errors in the event log that even pertains to this, so I was thinking that it was something to do with the main DC, do you think it could be something with the 2nd DC? if so i'll run DCDiag on it also and see what the results are. Thanks in advance, Cody DCDIAG results: Domain Controller Diagnosis Performing initial setup: Done gathering initial info. Doing initial required tests Testing server: Default-First-Site-Name\TFPDCS2 Starting test: Connectivity ......................... TFPDCS2 passed test Connectivity Doing primary tests Testing server: Default-First-Site-Name\TFPDCS2 Starting test: Replications ......................... TFPDCS2 passed test Replications Starting test: NCSecDesc ......................... TFPDCS2 passed test NCSecDesc Starting test: NetLogons ......................... TFPDCS2 passed test NetLogons Starting test: Advertising ......................... TFPDCS2 passed test Advertising Starting test: KnowsOfRoleHolders ......................... TFPDCS2 passed test KnowsOfRoleHolders Starting test: RidManager ......................... TFPDCS2 passed test RidManager Starting test: MachineAccount ......................... TFPDCS2 passed test MachineAccount Starting test: Services ......................... TFPDCS2 passed test Services Starting test: ObjectsReplicated ......................... TFPDCS2 passed test ObjectsReplicated Starting test: frssysvol ......................... TFPDCS2 passed test frssysvol Starting test: frsevent ......................... TFPDCS2 passed test frsevent Starting test: kccevent ......................... TFPDCS2 passed test kccevent Starting test: systemlog ......................... TFPDCS2 passed test systemlog Starting test: VerifyReferences ......................... TFPDCS2 passed test VerifyReferences Running partition tests on : ForestDnsZones Starting test: CrossRefValidation ......................... ForestDnsZones passed test CrossRefValidation Starting test: CheckSDRefDom ......................... ForestDnsZones passed test CheckSDRefDom Running partition tests on : DomainDnsZones Starting test: CrossRefValidation ......................... DomainDnsZones passed test CrossRefValidation Starting test: CheckSDRefDom ......................... DomainDnsZones passed test CheckSDRefDom Running partition tests on : Schema Starting test: CrossRefValidation ......................... Schema passed test CrossRefValidation Starting test: CheckSDRefDom ......................... Schema passed test CheckSDRefDom Running partition tests on : Configuration Starting test: CrossRefValidation ......................... Configuration passed test CrossRefValidation Starting test: CheckSDRefDom ......................... Configuration passed test CheckSDRefDom Running partition tests on : TIMELYIND Starting test: CrossRefValidation ......................... TIMELYIND passed test CrossRefValidation Starting test: CheckSDRefDom ......................... TIMELYIND passed test CheckSDRefDom Running enterprise tests on : TIMELYIND.LOCAL Starting test: Intersite ......................... TIMELYIND.LOCAL passed test Intersite Starting test: FsmoCheck ......................... TIMELYIND.LOCAL passed test FsmoCheck

Well, it's troubling why the main DC can't see itself as a DC to check for authorization. Have you in fact checked to see if it's showing up as authorized? Corn chips are no place for a mighty warrior!

Yes it is showing up as authorized. And I made sure the other DC is not authorized.