Re: Cannot locate Domain after migrate from NT to Win2K3

next thing to check would be DNS. Is the workstation pointed to the right
DNS server?

--
--------
Hope It Helps!

dw
_______________________________
Don Wilwol
Distributed Application Technologies.
dwilwol(DELETE)@datbusiness.com
www.AtTheDataCenter.com (personal website)
www.skysphere.com (hosting available)


"tony@i-cable" <tony@xxxxxxxxxxxx> wrote in message
news:e$rjpRdmGHA.3468@xxxxxxxxxxxxxxxxxxxxxxx
I did. I follow this http://support.microsoft.com/kb/255504/en-use to
Transfer FSMO roles


"Vincent Xu [MSFT]" <v-xuwen@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:bGqpygcmGHA.4528@xxxxxxxxxxxxxxxxxxxxxxxx
Hi,

I'd like to suggest you transfer FSMO to the Windows server 2003 DC 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: "tony@i-cable" <tony@xxxxxxxxxxxx>
References: <u0cCgqNmGHA.3980@xxxxxxxxxxxxxxxxxxxx>
<A72yXkOmGHA.4928@xxxxxxxxxxxxxxxxxxxxx>
<eSWwIyOmGHA.4100@xxxxxxxxxxxxxxxxxxxx>
Subject: Re: Cannot locate Domain after migrate from NT to Win2K3
Date: Mon, 26 Jun 2006 18:56:08 +0800
Lines: 89
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1437
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
Message-ID: <#ZPwm8QmGHA.1896@xxxxxxxxxxxxxxxxxxxx>
Newsgroups: microsoft.public.windows.server.migration
NNTP-Posting-Host: 59.188.32.186
Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP05.phx.gbl
Xref: TK2MSFTNGXA01.phx.gbl
microsoft.public.windows.server.migration:24232
X-Tomcat-NG: microsoft.public.windows.server.migration

Finally I demote all Win2K3 server and turn on my backup BDC.
Everything
seems ok now.


"tony@i-cable" <tony@xxxxxxxxxxxx> wrote in message
news:eSWwIyOmGHA.4100@xxxxxxxxxxxxxxxxxxxxxxx
I found it.

I have 2 Domain controller, computer name areDC1 and DC2.

Both Operations master are DC2.aa.bbb.com.

Now I have few Win2K users also has logon problem, they will get "The
system
cannot log you on to this domain because the system's computer
account
in
its primary domain is missing or the password on the account is
incorrect."
error message.




"Vincent Xu [MSFT]" <v-xuwen@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:A72yXkOmGHA.4928@xxxxxxxxxxxxxxxxxxxxxxxx
Hi,

To identify the PDC emulator

1.Open Active Directory Users and Computers
2.Right-click Active Directory Users and Computers and click
Operations
Masters.
3.On the PDC tab, the name of the current PDC emulator appears in
Operations master.

Check if PDC is assigned.

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



--------------------
From: "tony@i-cable" <tony@xxxxxxxxxxxx>
Subject: Cannot locate Domain after migrate from NT to Win2K3
Date: Mon, 26 Jun 2006 12:40:09 +0800
Lines: 6
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1437
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
Message-ID: <u0cCgqNmGHA.3980@xxxxxxxxxxxxxxxxxxxx>
Newsgroups: microsoft.public.windows.server.migration
NNTP-Posting-Host: 59.188.32.186
Path:
TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP02.phx.gbl
Xref: TK2MSFTNGXA01.phx.gbl
microsoft.public.windows.server.migration:24224
X-Tomcat-NG: microsoft.public.windows.server.migration

After migrate PDC from NT Server to Windows 2003 standard, I
have
a
number
of user cannot locate the domain controller even I did the clean
isntall
Win
NT Workstations. Any idea?















.

Relevant Pages

  • Re: Windows 2003 server DNS problems
    ... you would disconnect the BDC not the PDC from the network. ... > server was promoted as a PDC and the original PDC was promoted to a BDC. ... The DNS server is setup as a forwarder and is pointing ...
    (microsoft.public.windows.server.setup)
  • Re: NT4 to Server 2003 Migration
    ... based on everything you've said here, I would hire an experienced consultant, if only to assist you in the planning stage. ... I would not upgrade your current PDC to 2003. ... it's only 4-8 gig, not nearly large enough for 2003 server with SP1, and future service packs & upgrades. ... BDC 1 - RAS, Print Server, File Storage ...
    (microsoft.public.windows.server.migration)
  • Re: Windows Time Service: What if the PDC-role is moved?
    ... NTP - use the time source specified in the NtpServer Value ... I suggest using the w32tm command for modifying the time service parameters rather than directly modifying the registry entries. ... switch that takes priority and tells it to acquire NTP server info ... Doesn't he has to have the PDC DNS-name or IP-address in it? ...
    (microsoft.public.windows.group_policy)
  • Re: Windows NT to 2003 Changeover Questions
    ... > PDC, then bring up the potential 2003 PDC and see if we can get the other ... The NT 4.0 PDC is the ONLY server on a NT domain that holds a writeable copy ... How To Upgrade a Windows NT 4.0-Based PDC to a Windows Server 2003-Based ... You should also read up on the DNS requirements of AD. AD absolutely must ...
    (microsoft.public.win2000.setup)
  • Re: PDC/BDC problem
    ... Even com away from PDC and BDC. ... So which server from you has which role in the moment? ... I tried everything to reestablish the trust. ...
    (microsoft.public.win2000.networking)