RE: NT to 2003 Upgrade problems

Tech-Archive recommends: Fix windows errors by optimizing your registry

Is this registry setting on the DC or on the workstation?

--Nick

"Vincent Xu [MSFT]" wrote:

Hi Nick,

There're many reasons that will cause the symptoms. For example, the name
of the domain member was changed recently; the computer account in DC was
removed unexpectedly; or, some 3rd party applications may cause the secure
channel broken, and so on.

Rejoin the problematic box into domain should be the most effective way.
However, we still have following method can have a try:

Modify the following entries and setting them to 0:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters]
"requiresignorseal"
"sealsecurechannel"
"signsecurechannel"

If the problem still occurs,
1. Enable logon failue audit on DC
2. Try to logon
3. Save system event log on client and Save Security event log on DC
4. Compress the two logs into one zip file and attache it in reply


Best regards,

Vincent Xu
Microsoft Online Partner Support

======================================================
Get Secure! - www.microsoft.com/security
======================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others
may learn and benefit from this issue.
======================================================
This posting is provided "AS IS" with no warranties,and confers no rights.
======================================================



--------------------
Thread-Topic: NT to 2003 Upgrade problems
thread-index: AcZcIM+eJz9b0UlETmaM5fK/IITxEw==
X-WBNR-Posting-Host: 68.5.139.132
From: =?Utf-8?B?Tmljaw==?= <Nick@xxxxxxxxxxxxxxxxxxxxxxxxx>
Subject: NT to 2003 Upgrade problems
Date: Sun, 9 Apr 2006 14:59:01 -0700
Lines: 15
Message-ID: <D92D71D1-D4CD-4E0C-9B43-2F9927104436@xxxxxxxxxxxxx>
MIME-Version: 1.0
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: 7bit
X-Newsreader: Microsoft CDO for Windows 2000
Content-Class: urn:content-classes:message
Importance: normal
Priority: normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
Newsgroups: microsoft.public.windows.server.migration
Path: TK2MSFTNGXA01.phx.gbl
Xref: TK2MSFTNGXA01.phx.gbl
microsoft.public.windows.server.migration:23247
NNTP-Posting-Host: TK2MSFTNGXA01.phx.gbl 10.40.2.250
X-Tomcat-NG: microsoft.public.windows.server.migration

I recently upgraded a Windows NT PDC to 2003 Active Directory. After the
upgrade I could no longer log in to several servers in the domain. I
received the following message:

Windows cannot connect to the domain, either because the domain
controller
is down or otherwise unavailable, or because your computer account was
not
found. Please try again later. If this message continues to appear,
contact
your system administrator.

I have checked and the computer accounts for these servers exist in the
new
domain controller.

Is there anything other than rebooting and/or re-adding these servers to
the
domain that will fix this problem?




.

Relevant Pages

  • RE: NT to 2003 Upgrade problems
    ... of the domain member was changed recently; the computer account in DC was ... Save system event log on client and Save Security event log on DC ... upgrade I could no longer log in to several servers in the domain. ... I have checked and the computer accounts for these servers exist in the ...
    (microsoft.public.windows.server.migration)
  • Re: Sophos Anti-Virus SBE problems
    ... I saw the issue on the issue on the first network I upgraded with Sophos ... policy and went on with the upgrade... ... information, see the Event log. ... This item is from an SBS 2003 site that has a second server ...
    (microsoft.public.windows.server.sbs)
  • Re: Question on event log errors
    ... Also forgot to mention when these errors occur, often the event log will get ... I have the error message at the ... The hardware of these 2 servers are identical. ...
    (microsoft.public.windows.server.general)
  • RE: XP Browsing issue
    ... I checked event log on server and workstation but there was no entry on ... On the servers, there is no problem browsing the ... The list of servers for this workgroup is not ... I have 'enabled NetBIOS ...
    (microsoft.public.windows.server.active_directory)
  • Re: Windows 2003 FRS Errors
    ... upgrade W2K3 DC from NT4 ... fresh installed W2K3 DCs ... On which DC did you run FRSDIAG? ... > Checking for errors in Directory Service Event Log ...
    (microsoft.public.windows.server.active_directory)