Can win9x clients connect to new 2003 domain

From: Jerryboz (Jerryboz_at_discussions.microsoft.com)
Date: 11/16/04 

Date: Tue, 16 Nov 2004 06:49:11 -0800

Hello a'm Jerry Boz and have the following situation:

I have 9 resource domains (each on a different location connected by a 128
or 256 WAN link) and 1 master domain (2Mb WAN link). All domains are NT4 with
1 PDC on the resource locations and 1PDC and 2 BDC and 1 central exchange 5.5
server and internet connection with firewall on the master domain. (all the
current hardware of the PDC's do not support windows server 2003)
200 clients (mostly win95 and NT and some XP) and 250 users on the master
domain and approx. 240 global groups.

We want to migrate from NT4 (10 domains) to 2003 with 1 domain. And leave
the NT4 working as it is until all client are upgraded to XP (time approx. 6
months)

Recently we bought 2 new IBM x235 servers (not NT4 compatible).
On these server we want to install a fresh copy of Windows 2003 and make
them DC's for the new 2003 domain with AD and 1 new 2003 Exchange server.

Next we want to make a 2way trust between the NT4 domain and the Yk203
forest/domain.

Next we want to copy all the user and groups from NT4 to the new 2003 domain
with AD with the ADMT2 tool. It seems that ADMT works only with the 2003 AD
in native mode.

Question 1: When the new 2003 forest/domain is in native mode, is it still
possible for win9x or NT4 clients without DSCLIENT to authenticate on the
2003 domain??

Question 2: Can the win9x or NT4 clients without DSCLIENT work with the data
on the new DC's and still access files on the NT4 domain??

Question 3: if question 1 and 2 are not possible what can we do to make it
work??

Question 4: can y2k and XP clients who will be move to join the new 2003
domain connect to the old NT4 domain to access the data still left on that
domain??

Please forgive me my poor english.

With regards
JerryBoz

Relevant Pages

  • RE: Failed to create a trust relationship between NT4 and 2003 AD
    ... For Windows 2000 and 2003 these settings may be applied/configured via ... Digitally sign communications (if server ... With NT4 the only way to verify the settings is with the Regedt32 tool. ... Failed to create a trust relationship between NT4 and 2003 AD ...
    (microsoft.public.windows.server.migration)
  • RE: Failed to create a trust relationship between NT4 and 2003 AD
    ... Ping -a IP -- work and resolve the NT4 server name ... security policy in Administrative tools, go to local policies / security ... For Windows 2000 and 2003 these settings may be applied/configured via ...
    (microsoft.public.windows.server.migration)
  • RE: Failed to create a trust relationship between NT4 and 2003 AD
    ... is that a must to do for all setting when NT4 ... For Windows 2000 and 2003 these settings may be applied/configured via ... minutes in Windows 2003 Server ... Failed to create a trust relationship between NT4 and 2003 AD ...
    (microsoft.public.windows.server.migration)
  • Re: Windows NT Account missing or deleted
    ... mixed or Windows Server 2003 interim. ... One NT4 SP6a BDC. ... seems that the computer account passwords have not ... Looking at AD Users & Computers, the NT4 BDC is counted in the Domain ...
    (microsoft.public.windows.server.active_directory)
  • Re: Upgrade from NT4
    ... Frank McCallister SBS MVP ... I'm pretty sure Jeff would also promote the NT4 tempDC 'offline', ... Does Exchange server exist in the NT domain? ...
    (microsoft.public.windows.server.sbs)