Difference between revisions of "The system cannot log you on now because the domain is not available"

from HTYP, the free directory anyone can edit if they can prove to me that they're not a spambot
Jump to navigation Jump to search
(actual solution)
(actually, I don't think I tried the first solution)
Line 4: Line 4:
 
* '''Symptom''': Computer happily joins ''domain'', but then shows this message when you try to log in to that domain. Logging in to the local computer still works fine.
 
* '''Symptom''': Computer happily joins ''domain'', but then shows this message when you try to log in to that domain. Logging in to the local computer still works fine.
 
* '''Possible fix''': Run a [http://www.microsoft.com/windowsxp/using/helpandsupport/learnmore/tips/doug92.mspx repair installation] (requires XP install CD)
 
* '''Possible fix''': Run a [http://www.microsoft.com/windowsxp/using/helpandsupport/learnmore/tips/doug92.mspx repair installation] (requires XP install CD)
** Did not work
+
** Did not get to try this; found solution below first.
 
* '''Solution''': Log in to the domain as '''Administrator'''. Log out, then log in as regular user. (I don't know why this worked.)
 
* '''Solution''': Log in to the domain as '''Administrator'''. Log out, then log in as regular user. (I don't know why this worked.)
 
==Leads==
 
==Leads==
 
* '''2006-10-26''' [http://support.microsoft.com/kb/824302 Microsoft Support Article ID 824302] applies to [[Windows 2000]]
 
* '''2006-10-26''' [http://support.microsoft.com/kb/824302 Microsoft Support Article ID 824302] applies to [[Windows 2000]]

Revision as of 01:06, 7 October 2010

About

"The system cannot log you on now because the domain domain is not available" is an error message in Microsoft Windows XP.

Examples

  • Symptom: Computer happily joins domain, but then shows this message when you try to log in to that domain. Logging in to the local computer still works fine.
  • Possible fix: Run a repair installation (requires XP install CD)
    • Did not get to try this; found solution below first.
  • Solution: Log in to the domain as Administrator. Log out, then log in as regular user. (I don't know why this worked.)

Leads