Solution to "Windows cannot connect to the domain…" problem when XP connects to WinNT or Win2K Server

Posted on June 21, 2002 by Kevin

Ran into a strange problem today. A week-old XP box that could log in to a domain yesterday suddenly couldn’t today. We were getting an error box that said:

Windows cannot connect to the domain either because the domain controller is down or otherwise unavailable or because your computer account was not found.

It winds up that that XP tries to cryptographically sign Netlogon sessions, which the servers do not like. The work around according to JSI FAQ is:

1. Use Control Panel to open Local Security Policy in the Administrative Tools.

2. Navigate to Local Policies / Security Options.

3. Double-click Domain Member:Digitally encrypt or sign secure channel data (always).

4. Press Disabled.

5. Press Apply and OK.

I had to also do the old “change to ‘login to workgroup’ and then back to ‘login to domain'” trick. After a reboot it worked fine.

Just FYI…

About Kevin

Kevin Jarnot is a technologist who lives just South of Boston, MA. He is currently employed as Chief Technology Officer at DebtX, a financial services technology company based in Boston.
This entry was posted in Uncategorized. Bookmark the permalink.

0 Responses to Solution to "Windows cannot connect to the domain…" problem when XP connects to WinNT or Win2K Server

  1. mehmet kahraman says:
    June 10, 2008 at 6:09 am

    this didn’t work for my problem

    Reply
  2. Alex says:
    September 26, 2008 at 1:52 pm

    Thanks a ton, this fixed a very annoying problem.

    Reply
  3. Will says:
    May 7, 2009 at 6:05 pm

    It did not work me .

    Reply

Leave a Reply