WIN2K Pro cannot login to domain (In-place upgrade to 2003 R2 from NT4.0)
- From: puliyadim@xxxxxxxxx
- Date: 20 Aug 2006 18:55:48 -0700
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
.
- Follow-Ups:
- RE: WIN2K Pro cannot login to domain (In-place upgrade to 2003 R2 from NT4.0)
- From: Vincent Xu [MSFT]
- RE: WIN2K Pro cannot login to domain (In-place upgrade to 2003 R2 from NT4.0)
- Prev by Date: RE: IIS and Domain Controllers
- Next by Date: RE: CSVDE
- Previous by thread: CSVDE
- Next by thread: RE: WIN2K Pro cannot login to domain (In-place upgrade to 2003 R2 from NT4.0)
- Index(es):
Relevant Pages
|