domain controller restart

Sponsored Links

I have 2 domain controllers both as Global Catalogs in a single site. Both
of these servers are AD integrated DNS Servers as well.
It is my understanding that if i restart 1 of these Domain Controllers, all
of our services on the network should still be able to authenticate to the
domain.
Unfortunately, if i restart 1 of the servers i get errors with SQL jobs,
exchange and MS Data Protection Manager related to authentication problems.
Can anyone explain to me why this would be?

additional info-
DCDiag, netdiag and replmon are all showing as passing tests.

the Exact SQL error i got is:
A SQL Job named DW Rebuild on server failed at 10pm last night. Message is:
"The job failed. Unable to determine if the owner (domain\user) of job
JOBNAME has server access(reason: Could not obtain information about Windows
NT group/user 'Domain\User', error code 0x6e. [SQLSTATE 42000] (Error 15404)
The statement has been terminated. [SQLSTATE 01000](Error 3621)). NOTE:
Failed to notify user via email.

I'm glad that i'm not alone at least.
In our case though the secondary DNS server is the DC that was restarted,
not the primary one. In fact the primary DNS Server is the server with the
FSMOs on it so i don't understand why there would be an issue still if we
restarted the secondary DNS\AD server.

Make sure that all domain machines use both DNS servers on there NIC. Applications
like Exchange earlier 2007 use only one DC under the Recipients update service,
so there you can add the second DC also.

For the SQL error i suggest to posting that to:
microsoft.public.sqlserver.server
microsoft.public.sqlserver.setup
microsoft.public.sqlserver.tools

We are seeing this exact problem on a number of SQL 2000 and 2005 cluster
instances. We have two domain controllers, both configured as global catalog
servers. We have 4 sets of SQL cluster servers that have applications
connecting to them from Web servers using Windows authentication. All SQL
and IIS servers have both DCs configured in the NIC settings. No static DNS
entries configured. When one DC is rebooted, all applications lose
connectivity and they have to restart services to resolve this. We get a
18452 error in SQL error logs and in application log files. "Error message:
Login failed for user '(null)'. Reason: Not associated with a trusted SQL
Server connection." I was thinking it could have to do with SPN records or
Delegation but that is configured properly on one cluster and we are also
seeing the issue with that one. Any ideas?

[nkline]

We are having similar issues. Did you find a solution?

As you are replying to an older forumstecharena posting, no problem description
is included in the microsoft.public.windows.server.active_directory newsgroup,
please provide your complete problem with error message OS version description
and what exactly happens in your domain.