Re: WIN2K Pro cannot login to domain (In-place upgrade to 2003 R2 from NT4.0)

Tech-Archive recommends: Speed Up your PC by fixing your registry

Hi,

Actually, regarding the NO2 in my previous reply, I suggest you perform a
test as:

After you take TBDC offline and upgrade it to PDC, connect it with a Win2k
client to see if it can login into domain with the TBDC. Not other DCs.

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.
======================================================



--------------------
From: puliyadim@xxxxxxxxx
Newsgroups: microsoft.public.windows.server.migration
Subject: Re: WIN2K Pro cannot login to domain (In-place upgrade to 2003
R2 from NT4.0)
Date: 21 Aug 2006 02:37:22 -0700
Organization: http://groups.google.com
Lines: 115
Message-ID: <1156153042.057279.289390@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
References: <1156125348.002380.104730@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
<m$xhsbOxGHA.5720@xxxxxxxxxxxxxxxxxxxxx>
NNTP-Posting-Host: 202.79.209.131
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
X-Trace: posting.google.com 1156153047 728 127.0.0.1 (21 Aug 2006
09:37:27 GMT)
X-Complaints-To: groups-abuse@xxxxxxxxxx
NNTP-Posting-Date: Mon, 21 Aug 2006 09:37:27 +0000 (UTC)
In-Reply-To: <m$xhsbOxGHA.5720@xxxxxxxxxxxxxxxxxxxxx>
User-Agent: G2/0.2
X-HTTP-UserAgent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; .NET
CLR 1.1.4322),gzip(gfe),gzip(gfe)
X-HTTP-Via: 1.0 PREMAS-ISA
Complaints-To: groups-abuse@xxxxxxxxxx
Injection-Info: 74g2000cwt.googlegroups.com; posting-host=202.79.209.131;
posting-account=FxHRLg0AAAAGA5hFlTWPXdlJ2s7pZ1T5
Path:
TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTFEEDS02.phx.gbl!msrnewsc1!
TK2MSFTFEEDS01.phx.gbl!newsfeed00.sul.t-online.de!t-online.de!border2.nntp.d
ca.giganews.com!border1.nntp.dca.giganews.com!nntp.giganews.com!postnews.goo
gle.com!74g2000cwt.googlegroups.com!not-for-mail
Xref: TK2MSFTNGXA01.phx.gbl
microsoft.public.windows.server.migration:24860
X-Tomcat-NG: microsoft.public.windows.server.migration

Hi Vincent,

1) Original PDC is in the production NW
2) Yes all clients were able to login to NT domain
3) I tried this morning and it worked but it might not be a workable
solution as we have more than 200 WIN2K pro in our infra.

Pl suggests.

Rgds,

Dinesh

Vincent Xu [MSFT] wrote:

Hi,

Something need to be clarified:

1. Since you take the TBDC offline and upgraded it. How about the
original
PDC?

2. When you take TBDC offline and upgrade it to PDC, can all clients
login
into domain successfully?

3. For the Windows 2000 clients, I suggest you disjoin the out of
domain by
using TBDC1 and rejoin into AD domain to see the results.


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.
======================================================



--------------------
From: puliyadim@xxxxxxxxx
Newsgroups: microsoft.public.windows.server.migration
Subject: WIN2K Pro cannot login to domain (In-place upgrade to 2003 R2
from NT4.0)
Date: 20 Aug 2006 18:55:48 -0700
Organization: http://groups.google.com
Lines: 37
Message-ID: <1156125348.002380.104730@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
NNTP-Posting-Host: 202.79.209.131
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
X-Trace: posting.google.com 1156125353 23613 127.0.0.1 (21 Aug 2006
01:55:53 GMT)
X-Complaints-To: groups-abuse@xxxxxxxxxx
NNTP-Posting-Date: Mon, 21 Aug 2006 01:55:53 +0000 (UTC)
User-Agent: G2/0.2
X-HTTP-UserAgent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0;
NET
CLR 1.1.4322),gzip(gfe),gzip(gfe)
X-HTTP-Via: 1.0 PREMAS-ISA
Complaints-To: groups-abuse@xxxxxxxxxx
Injection-Info: i42g2000cwa.googlegroups.com;
posting-host=202.79.209.131;
posting-account=FxHRLg0AAAAGA5hFlTWPXdlJ2s7pZ1T5
Path:

TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTFEEDS02.phx.gbl!newsfeed.c

w.net!cw.net!news-FFM2.ecrc.de!newsfeed.gamma.ru!Gamma.RU!postnews.google.co
m!i42g2000cwa.googlegroups.com!not-for-mail
Xref: TK2MSFTNGXA01.phx.gbl
microsoft.public.windows.server.migration:24852
X-Tomcat-NG: microsoft.public.windows.server.migration

Hello,

I am in the final testing of the in-place upgrade and yesterday i was
struck with a new potential problem which i have not come accross with
previous pilot testing.

What i did was..

a) Install 1 WIN2K (SP4) & 1 WINXP (SP2) pc and joing to the
production

NT infra.
b) Intall a BDC on the production infra (say - TBDC)
c) Intall another BDC on the production infra (say - TBDC1, this is to
simulate the actual upgrade process, as we will have 1 BDC serving as
a

print server for few months after the upgrade). This has DHCP & WINS
installed
d) Take TBDC off from the production and promote it to PDC.
e) Those 2 client PC's will use TBDC1 as the DHCP & WINS server
f) Perform in-place upgrade on TBDC which went on smooth.
g) Modify the DHCP scope to include the new AD DC's IP for DNS.
h) WINXP was able to detect the presence of AD and it joined the AD
automatically.
i) But WIN2K was not able to join the AD but was able to login using
the TBDC1 (BDC), when i tried shutting down the TDBC1, WIN2K was not
able to login.
The event logs reported...
1)Event ID: 5719 / NETLOGON
2)Event ID: 1000 / Userenv


Appreciate if you could let me know what could be causing this issue.


Thanks & Rgds,
Dinesh





.

Relevant Pages