RE: NT to 2003 Upgrade problems

Hi,

Please modify the registry at client side.

Thanks.


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: AcZe+ryQNMHppqy+T8uUJjHkiWN4yA==
X-WBNR-Posting-Host: 209.11.255.30
From: =?Utf-8?B?Tmljaw==?= <Nick@xxxxxxxxxxxxxxxxxxxxxxxxx>
References: <D92D71D1-D4CD-4E0C-9B43-2F9927104436@xxxxxxxxxxxxx>
<ywwWoyEXGHA.888@xxxxxxxxxxxxxxxxxxxxx>
Subject: RE: NT to 2003 Upgrade problems
Date: Thu, 13 Apr 2006 06:04:02 -0700
Lines: 94
Message-ID: <7238A794-15D7-476E-8F83-2F1C2DB7CC93@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:23305
NNTP-Posting-Host: TK2MSFTNGXA01.phx.gbl 10.40.2.250
X-Tomcat-NG: microsoft.public.windows.server.migration

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: IE6 Wont let me See Graphics
    ... Microsoft Online Partner Support ... Get Secure! ... When responding to posts, please "Reply to Group" via your newsreader so ...
    (microsoft.public.windows.inetexplorer.ie6.browser)
  • RE: Migrating users from another forest
    ... Microsoft Online Partner Support ... Get Secure! ... When responding to posts, please "Reply to Group" via your newsreader so ...
    (microsoft.public.windows.server.migration)
  • Re: DNS Update problem
    ... Microsoft Online Partner Support ... Get Secure! ... When responding to posts, please "Reply to Group" via your newsreader so ...
    (microsoft.public.windows.server.dns)
  • Re: From Win 2K To Win 2003
    ... Microsoft Online Partner Support ... Get Secure! ... When responding to posts, please "Reply to Group" via your newsreader so ...
    (microsoft.public.windows.server.migration)
  • RE: Wasnt thinking, locked admin out of policy. How do I remove?
    ... Microsoft Online Partner Support ... Get Secure! ... When responding to posts, please "Reply to Group" via your newsreader so ...
    (microsoft.public.windows.group_policy)