Re: Upgrade of NT 4.0 to Windows 2003 Domain

I would suggest following this article:
http://support.microsoft.com/kb/325874/en-us

See the section on name resolution. If it doesn't work post back with what
you did and what the error was that stopped you from going farther.

hth
DDS W 2k MVP MCSE

<danielle@xxxxxxxxxxxxx> wrote in message
news:1149094736.178271.170970@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thanks, the BDC is a PDC. Still can't ping the IP address from the NT
PDC, but can ping all IP addresses from the Win2k03 server, so the
trust won't work yet anyway, until I can resolve this darned ping
problem.
Any ideas on the Ping problem? The Windows firewall is not turned on
on the Win2k03 server.

Danny Sanders wrote:
If you must migrate then promote the existing NT 4.0 BDC to PDC. You need
to
have a PDC in order to create the trust.

then look at ADMT from MS.


hth
DDS W 2k MVP MCSE

<danielle@xxxxxxxxxxxxx> wrote in message
news:1149090734.872837.168840@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thank you for your prompt response. Agreed, that would be the way to
go, except...all copies of NT 4.0 were purchased OEM and it cannot be
upgraded to Win2k03, so I have to stick with the plan I devised and set
out below. Anyone have any ideas given the scenario I set forth?
Thanks

Danny Sanders wrote:
Here's the scenario. I have an NT 4.0 BDC (PDC apparently bit the
dust
before I started here, so they're running off the BDC).


Promote the BDC to PDC. It will complain but it will work.

use. I formatted it and installed a fresh copy of Windows 2003
Standard server. Configured the server with the wizard to have DNS,
DHCP, and AD. In the DNS scope, I used the same IP schema as the
old

Format and install NT 4.0 on it as a BDC while connected to your
existing
domain, promote to PDC then upgrade to Win 2k3 and AD.

See:
http://support.microsoft.com/kb/326209/en-us


DNS must be set up right.
See:
http://support.microsoft.com/kb/814591/en-us

http://support.microsoft.com/kb/825036/en-us\

http://support.microsoft.com/kb/323380/en-us


. By upgrading the domain you won't have to worry about the migration
wizard
creating you accounts.


hth
DDS W 2k MVP MCSE

<danielle@xxxxxxxxxxxxx> wrote in message
news:1149084229.614399.129570@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Here's the scenario. I have an NT 4.0 BDC (PDC apparently bit the
dust
before I started here, so they're running off the BDC). I have a
server that used to be used for a Citrix backup, but was no longer
in
use. I formatted it and installed a fresh copy of Windows 2003
Standard server. Configured the server with the wizard to have DNS,
DHCP, and AD. In the DNS scope, I used the same IP schema as the
old
domain had. I can ping all servers from the Windows 2003 server,
but
the NT side of things cannot see the IP address. I attempted to add
a
trust for the old domain, but received errors on both ends. I'm
thinking I cannot go forward with the trust until ping works between
the servers. Additionally, we have a brand new server which will be
installed with Win2k03 and Exchange 2k03. We then plan to use the
Migration Wizard to move the old Exchange 5.5 clients to Exchange
2k03,
which should automaticallly create the AD accounts as well. Can
anyone
help me get past this first step? Thanks.





.

Relevant Pages

  • Re: Hosts file ignored
    ... > any of the entries I have made to the server's hosts file. ... > Successfully flushed the DNS Resolver Cache. ... > I am not running a DNS server on my system. ... > I can ping IP addresses without any problem, both on the LAN and on ...
    (microsoft.public.windows.server.general)
  • RE: NT 4.0 to Windows Server 2003 Upgrade
    ... 325851 How To Set Up ADMT for a Windows NT 4.0-to-Windows Server 2003 ... NT 4.0 to Windows Server 2003 Upgrade ... | the AD wizard, my client systems are still able to log into the domain ... |> | would it be better to configure DNS through the AD wizard? ...
    (microsoft.public.windows.server.migration)
  • Re: HTTP trouble in 2004
    ... In this way, all DNS ... how does this server resolve external ... They are just HTTP ... > Ping in ALLOW PING protool from EXTERNAL to INTERNAL ...
    (microsoft.public.isaserver)
  • Re: loss of SOME connectivity
    ... I'm a little concerned about your Primary DNS suffix and your DHCP. ... Is your router handling DHCP for the network? ... Ethernet adapter Server Local Area Connection: ... I get "Ping request could not find ...
    (microsoft.public.windows.server.sbs)
  • Re: Cant see out to .co.uk from inside my .local domain (forward l
    ... Well I removed the entry from my hosts file and issued a ping command to both ... network only from the server which I changed the hosts file for. ... Indeed is it even a DNS issue. ...
    (microsoft.public.windows.server.sbs)