RE: NT clients after 2K3 server upgrade
- From: v-amanwa@xxxxxxxxxxxxxxxxxxxx (Amanda Wang [MSFT])
- Date: Mon, 30 May 2005 06:44:35 GMT
Hello,
Thanks for your post.
My understanding on this issue is that after upgrading NT environment to
2K3, NT clients need to be disconnected from the old domain and then
rejoined in new domain in order to log on. If not, they get the message
that a domain controller could not be contacted. If I have misunderstood
your concern, please feel free to let me know.
Based on the error information, it seems that the NT clients cannot find
the new DC. In NT networking, NT workstation should use WINS to contact
DC. On other hand, NT workstation and win98 are not fully compatible with
win2k3 domain. you may consider upgrading the workstation to higher
version. I suggest you perform the following steps to isolate the issue:
1. Please install WINS on win2k3 server to check the status.
The following article describes how to install a WINS server on Win2k3
server:
Install a WINS server
http://www.microsoft.com/technet/prodtechnol/windowsserver2003/library/Serve
rHelp/e59ecd56-f5f2-444f-a9fb-e2ff226c46f4.mspx
2. Try to ping the new DC's IP address from the client.
3. Use UNC: \\DC Name to access the new DC's shared files.
4. Where is the DNS server in the new domain? Make sure all the clients'
DNS settings point to the DNS server and restart the client to check the
issue again.
After the above confirmation, I would like give you the detailed upgrade
steps from WinNT to Win2k3 as following and you can check if there is
anything missing during your upgrade process:
As a kind reminder, please backup the whole system before you take any
action.
Performing a "not in place" upgrade
======================
1.Install NT 4.0 BDC on the new box.
2.Promote the BDC to the PDC, which demotes the PDC to a BDC.
3.Do a full backup of the former PDC and remove it from the network.
4.Upgrade the new PDC to Windows Server 2003.
If you want to expand the boot partition, please refer to the following KB:
5.Use the Windows Server 2003 Active Directory wizard to turn on the Active
Directory service. The Active Directory service imports the existing user
accounts, groups, and other settings from the PDC.
6.Run for a test period.
7.If desired you can do a clean installation of Windows Server 2003 on the
former PDC, and bring it online as an Active Directory domain controller.
8.Transfer GC and all Flexible Single-Master Operation (FSMO) roles to the
new Windows Server 2003 domain controller.
About how to transfer GC and FSMO, please refer to the following articles:
Configure a domain controller as a global catalog server (Windows Server
2003)
http://www.microsoft.com/technet/prodtechnol/windowsserver2003/proddocs/stan
dard/msmqconcepts/msmq_inst_set_gc.asp
324801 HOW TO: View and Transfer FSMO Roles in Windows Server 2003
http://support.microsoft.com/?id=324801
9.Verify all directory information has replicated.
10.Demote the first domain controller to a member server, and remove from
the domain.
I suggest you check the following KB articles to upgrade to Win2k3 from NT4:
Upgrading from Windows NT Server 4.0 to Windows Server 2003
http://www.microsoft.com/windowsserver2003/evaluation/whyupgrade/nt4/nt4tows
03-2.mspx
If the issue persists after checking the above steps, please help me
collect the screen shot of the detailed error information that a domain
controller could not be contacted so that I can perform further research on
this issue.
HTH! Any update, keep in touch!
Thanks & Regards
Amanda Wang [MSFT]
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 your issue.
=====================================================================
--------------------
>Thread-Topic: NT clients after 2K3 server upgrade
>thread-index: AcVioBAs5ePmkMECR5yXOtflXHp4tg==
>X-WBNR-Posting-Host: 195.115.151.193
>From: "=?Utf-8?B?UGF1bCBNLg==?=" <Paul M.@xxxxxxxxxxxxxxxxxxxxxxxxx>
>Subject: NT clients after 2K3 server upgrade
>Date: Fri, 27 May 2005 02:40:05 -0700
>Lines: 20
>Message-ID: <89B56F02-323B-48AA-8520-4ED3210B6FB0@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.0
>Newsgroups: microsoft.public.windows.server.migration
>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
>Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.migration:10407
>X-Tomcat-NG: microsoft.public.windows.server.migration
>
>Hi,
>
>I'm having a problem with our NT clients after upgrading our current NT
>environment to 2K3.
>
>We currently have an NT PDC and an NT BDC. I am using a third machine to
>become a BDC, promote and upgrade to 2K3. When this is the 2K3 DC, I am
>turning off the old NT PDC and BDC and installing 2 brand new 2K3 servers;
>Once these are synchronised and running all necessary services, the
'middle'
>server will be turned off.
>
>However, our NT clients (which are staying with NT for a while) need to be
>disconnected from the domain (into a W/G) and then rejoined in order to
log
>on. If not, they get the message that a domain controller could not be
>contacted.
>
>Can anyone suggest a solution so that I don't have to go to every client
and
>rejoin the domain?
>
>Many thanks in advance.
>
.
- References:
- NT clients after 2K3 server upgrade
- From: Paul M.
- NT clients after 2K3 server upgrade
- Prev by Date: RE: SMTP IIS6.0 -problem to send out external email
- Next by Date: RE: Where is the games folder?
- Previous by thread: NT clients after 2K3 server upgrade
- Next by thread: Migration w2k to w2k3 and creat a new forest
- Index(es):
Relevant Pages
|
