Re: Cannot migrate a Windows XP station from a W2K domain to a W2K3 domain

From: Tim Goth (grandma_goth_at_yahoo.com)
Date: 03/30/04 

Date: Mon, 29 Mar 2004 22:25:20 -0800

Hello,

Your problem sounds like it could be spurring from a few
things. I have had the exact problem that you are
having. Here is a list of what to do (you have probably
already taken some of these steps.)
1. Log onto the local machine as Administrator
2. Verify the machine is in a workgroup, not a domain, if
in domain, join it to a workgroup
3. Restart the machine
4. Log back in
5. open a command prompt
6. insert the command "ipconfig /flushdns" (this removes
all old dns entries)
7. insert the command "ipconfig /registerdns" (this
registers the computer with a dns server)
8. verify all tcp/ip settings (ip address, dns server,
wins server(ensure that the default setting is checked
for NETBIOS on the WINS tab), dhcp server (if used), and
default gateway)
9. reboot the machine
10. log onto the local machine
11. join the domain

This should help, if it doesn't email me, and I wil work
with you.

Tim Goth
mailto:grandma_goth@yahoo.com
>-----Original Message-----
>Hi William,
>
>As your instructions I exported the specified key (I
have tested also
>with corresponding key of my lab computer that can join
the domain).
>I imported this on the not working XP station but
as "normal mode" or
>"safe mode", it is not possible to join the domain.
>
>On the not working XP station I have no event in the
event monitor
>that can be related to the problem (in the timeframe of
the logon
>test).
>
>But on the server I can look an event that I don't
receive previously.
> The event is only located on the Security events
monitor and the
>failure is following by some success audit :
>
>Type : Failure Audit
>Reason : An error occured during logon
>User Name :
>Domain :
>Logon Type : 3
>Login Process : Kerberos
>Authentication Package : Kerberos
>Workstation Name : -
>Status code : 0xC000006D
>Substatus code : 0xC000133
>
>Other fields are empty (expected the remote IP address
that is the IP
>address of the workstation)
>
>Regarding an other post the "Domain member :
digitally ... (always)"
>is well enabled.
>
>Thanks for your help.
>
>B. Lienard
>
>v-rxwang@online.microsoft.com (William Wang[MSFT]) wrote
in message news:<GK920x6EEHA.3244@cpmsftngxa06.phx.gbl>...
>> Hi,
>>
>> Thanks for your update. I understand that testing our
suggestions may take
>> some time. I was hoping that you would provide us
with a timeframe when
>> this might occur so we may better assist you. If for
some reason you are
>> unable to do so at this point, we understand and will
close the thread for
>> now. When you are able to provide additional
feedback, please reply to
>> this thread and I will be alerted and will follow up
with you promptly.
>>
>> Sincerely,
>>
>> William Wang
>> Microsoft Online Support Engineer
>>
>> 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.
>> =====================================================
>>
>> This posting is provided "AS IS" with no warranties,
and confers no rights.
>> --------------------
>> >From: parano007@hotmail.com (b. Lienard)
>> >Newsgroups: microsoft.public.windows.server.migration
>> >Subject: Re: Cannot migrate a Windows XP station from
a W2K domain to a
>> W2K3 domain
>> >Date: 26 Mar 2004 05:01:28 -0800
>> >Organization: http://groups.google.com
>> >Lines: 112
>> >Message-ID:
<c3fe9bcd.0403260501.3699a10b@posting.google.com>
>> >References:
<c3fe9bcd.0403250758.1bec992c@posting.google.com>
>> <2X$7a9vEEHA.660@cpmsftngxa06.phx.gbl>
>> >NNTP-Posting-Host: 81.240.130.73
>> >Content-Type: text/plain; charset=ISO-8859-1
>> >Content-Transfer-Encoding: 8bit
>> >X-Trace: posting.google.com 1080306088 2906 127.0.0.1
(26 Mar 2004
>> 13:01:28 GMT)
>> >X-Complaints-To: groups-abuse@google.com
>> >NNTP-Posting-Date: Fri, 26 Mar 2004 13:01:28 +0000
(UTC)
>> >Path:
>> cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!
newsfeed00.sul.t-online.de!t-onlin
>> e.de!news.glorb.com!postnews2.google.com!not-for-mail
>> >Xref: cpmsftngxa06.phx.gbl
microsoft.public.windows.server.migration:9200
>> >X-Tomcat-NG: microsoft.public.windows.server.migration
>> >
>> >Hi William,
>> >
>> >Thanks a lot for your answer, I'll try it as soon as
possible and I
>> >post a feedback here after that.
>> >
>> >B.Lienard
>> >IntecH NowEclipse
>> >
>> >v-rxwang@online.microsoft.com (William Wang[MSFT])
wrote in message
>> news:<2X$7a9vEEHA.660@cpmsftngxa06.phx.gbl>...
>> >> Hi Lienard,
>> >>
>> >> Thanks for your posting. You may want to try the
following steps which
>> have
>> >> helped a customer resolve the similar problem
before.
>> >>
>> >> IMPORTANT: This article contains information about
modifying the
>> registry.
>> >> Before you modify the registry, make sure to back
it up and make sure
>> that
>> >> you understand how to restore the registry if a
problem occurs. For
>> >> information about how to back up, restore, and edit
the registry, refer
>> to
>> >> the following article in the Microsoft Knowledge
Base:
>> >>
>> >> 256986 Description of the Microsoft Windows
Registry
>> >>
>> >> http://support.microsoft.com/default.aspx?
scid=kb;EN-US;256986
>> >>
>> >> 1. Export the following registry key from the XP
machine that has
>> >> successfully joined the new domain.
>> >>
>> >>
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netl
ogon]
>> >>
>> >>
>> >> 2. Import the registry to the workstation that is
experiencing this
>> problem.
>> >>
>> >>
>> >> 3. Bring the machine into a workgroup, reboot the
computer and then join
>> >> the domain.
>> >>
>> >> If the issue persists, you may want to try booting
the problematic XP
>> >> computer into Safe Mode with Networking and then
try to join the domain.
>> >>
>> >> If the computer still cannot be joined to the new
domain, I'd like to
>> check
>> >> if there are some related entries in the event logs
on both the
>> workstation
>> >> and the server.
>> >>
>> >> Please feel free to let me know if anything is
unclear.
>> >>
>> >> Sincerely,
>> >>
>> >> William Wang
>> >> Microsoft Online Support Engineer
>> >>
>> >> 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.
>> >>
=====================================================
>> >>
>> >> This posting is provided "AS IS" with no
warranties, and confers no
>> rights.
>> >> --------------------
>> >> >From: parano007@hotmail.com (b. Lienard)
>> >> >Newsgroups:
microsoft.public.windows.server.migration
>> >> >Subject: Cannot migrate a Windows XP station from
a W2K domain to a
>> W2K3
>> domain
>> >> >Date: 25 Mar 2004 07:58:54 -0800
>> >> >Organization: http://groups.google.com
>> >> >Lines: 31
>> >> >Message-ID:
<c3fe9bcd.0403250758.1bec992c@posting.google.com>
>> >> >NNTP-Posting-Host: 195.207.101.112
>> >> >Content-Type: text/plain; charset=ISO-8859-1
>> >> >Content-Transfer-Encoding: 8bit
>> >> >X-Trace: posting.google.com 1080230335 11187
127.0.0.1 (25 Mar 2004
>> 15:58:55 GMT)
>> >> >X-Complaints-To: groups-abuse@google.com
>> >> >NNTP-Posting-Date: Thu, 25 Mar 2004 15:58:55 +0000
(UTC)
>> >> >Path:
>> >>
>> cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!
newsfeed00.sul.t-online.de!t-onlin
>> >> e.de!news.glorb.com!postnews2.google.com!not-for-
mail
>> >> >Xref: cpmsftngxa06.phx.gbl
>> microsoft.public.windows.server.migration:9166
>> >> >X-Tomcat-NG:
microsoft.public.windows.server.migration
>> >> >
>> >> >Hi,
>> >> >
>> >> >After spend many hours to find a solution (in the
microsoft knowlegde
>> >> >database, in these news groups), I post my
problem :
>> >> >
>> >> >I must change a old W2k server by a new one
running Windows Small
>> >> >Business Server 2003. In the network I have 6 PCs
running windows 2k
>> >> >(already using the W2K domain) and 2 running
Windows XP (1 is new and
>> >> >was never put on the domain). I have not
approbation between servers
>> >> >because the new server replace the old one.
>> >> >
>> >> >I can join the new domain with all W2K PCs.
>> >> >I can join the new domain with the new PC running
windows XP.
>> >> >
>> >> >When I try to join the W2k3 domain with the last
XP PC, it doesn't
>> >> >work, I have "Access denied".
>> >> >
>> >> >- The DNS work fine
>> >> >- I tried the "domain member : digitaly ..."
enabled and disabled
>> >> >- I have remove all previous network connection
(mounted drive,
>> >> >printers, ...)
>> >> >- The user used to join the domain can do that
because I can join the
>> >> >domain with the other XP PC.
>> >> >- I changed the name of the computer
>> >> >- The XP PC that does not join the domain have
a "smart card reader",
>> >> >but reader plug or unplug is also the same.
>> >> >- I can "re-join" the W2K domain without problems.
>> >> >
>> >> >Anybody have an idea about that ?
>> >> >
>> >> >Thanks in advance.
>> >> >
>> >
>.
>

Relevant Pages

  • Re: Multiple IPs in DNS
    ... with our internal DNS server. ... The only way to stop the records is to go into the DNS server properties, ... parent folder) record for both the domain name and the Global Catalog ... Below is the registry entry you must use regedt32 to make these entries. ...
    (microsoft.public.windows.server.dns)
  • Re: Remove A-record from DNS server permanently...
    ... which has two NICs. ... The DNS server shows two A-records for the local server, ... Registry value: DnsAvoidRegisterRecords ...
    (microsoft.public.windows.server.dns)
  • RE: Certificate Authority is also a DC, want to demote?
    ... Have you installed Symantec Mail Security for Exchange? ... Delete the registry sub-key, MessageDeletionQueue, from the ... right click on the Default SMTP Virtual Server and select Properties ... SMTP could not connect to the DNS server '172.16.16.50'. ...
    (microsoft.public.windows.server.active_directory)
  • RE: 4004
    ... To prevent the errors remove the old zone key from the following registry location. ... '--'NT\CurrentVersion\DNS Server ... This DNS server is configured to ...
    (microsoft.public.win2000.dns)
  • DNS Error Event 7034
    ... I am running Windows Server 2003. ... I have received an error in my Event Viewer that states... ... We are running DNS on our main Domain Controller running Windows 2003. ... We do have a backup DNS server, and it did seem to allow the users who were ...
    (microsoft.public.windows.server.dns)