Client system shows red cross mark
Even though its supported to combine domain controller with 800xA services (refer to appropriate System Guide for details) its preferred to run the DCs in separate servers.
800xA uses authenticated sockets for in practice all communication - i.e. a client will only be accepted by a server if the server can authenticate the client.
When restarting a domain controller, certain domain controller services will probably not be available until they have fully started.
I suspect there is a limited "limbo state" during which domain authentication is not possible if attempted on the starting server.
We might be able to help you further if you can share some more details?
Are anything of interest output to the following event lists during the problem:
- [Workplace Structure]Web System Workplace:System Event List
- Windows Event Log (System + Application + DC specific logs)?
Does dcdiag.exe (part of Windows Support Tools on the 2003 Server CDROM, included in standard install on 2008 and later) report "Passed" on all check items?
Is DNS role added to secondary domain controller (DNS is default only on first domain controller)?
Error codes during workplace launch?