NT to 2000 w/ AD upgrade...can't join servers

  • Thread starter Thread starter Mark
  • Start date Start date
M

Mark

Did the advised method of upgrading an NT 4 PDC to 2000
with Active Directory. Followed all the wizards, and
went through pre-deployment advice via MS white-papers.
Now the problems:

1. The PDC was named "PDC". The domain was
named "jf_hotel". I chose to use ih-corp.com as the new
domain name. It renamed my PDC: "PDC.jf_hotel" Why?

2. I let the wizard configure DNS. Removed the root
domain notation from "forward lookup zones", and
configured my ISP DNS servers in the forward lookup. DNS

3. The new hardware for the Active Directory controllers
is on a different subnet. I have configured the sites
and services to notice this subnet, and I actually was
able to do a DCPROMO on two of the machines last night,
and able to see the Directory on the original upgraded
PDC. This morning...can't see Directory anymore. Can't
DCpromo any servers, can't join any servers to the
domain. All servers have DNS pointed to upgraded PDC
that has DNS on it.

4. I do have the problem noted on Technet: Microsoft
Knowledge Base Article - 262376: Computer Name Does Not
Match the Windows 2000 Domain Name After Upgrade.
Service Pack 3 was installed after DCpromo...so that
screwed me.

Any advice on a solution? I have the BDC still running.
Would it be possible to shut-down the Active Directory
server, promote the BDC, and start fresh given the
problems noted in Q262376?
 
In
Mark said:
Did the advised method of upgrading an NT 4 PDC to 2000
with Active Directory. Followed all the wizards, and
went through pre-deployment advice via MS white-papers.
Now the problems:

1. The PDC was named "PDC". The domain was
named "jf_hotel". I chose to use ih-corp.com as the new
domain name. It renamed my PDC: "PDC.jf_hotel" Why?

2. I let the wizard configure DNS. Removed the root
domain notation from "forward lookup zones", and
configured my ISP DNS servers in the forward lookup. DNS

3. The new hardware for the Active Directory controllers
is on a different subnet. I have configured the sites
and services to notice this subnet, and I actually was
able to do a DCPROMO on two of the machines last night,
and able to see the Directory on the original upgraded
PDC. This morning...can't see Directory anymore. Can't
DCpromo any servers, can't join any servers to the
domain. All servers have DNS pointed to upgraded PDC
that has DNS on it.

4. I do have the problem noted on Technet: Microsoft
Knowledge Base Article - 262376: Computer Name Does Not
Match the Windows 2000 Domain Name After Upgrade.
Service Pack 3 was installed after DCpromo...so that
screwed me.

Any advice on a solution? I have the BDC still running.
Would it be possible to shut-down the Active Directory
server, promote the BDC, and start fresh given the
problems noted in Q262376?
Click to expand...

Actually, that is the name it should have, but it is not a good DNS domain
name.
Do it again this time give you domain a good DNS name like jf.hotel (use the
dot in the name) if you use jf_hotel DNS sees that as a single label domain
name. Which will cause problems in itself.
 
In
Mark said:
I actually gave the domain the new name of ih-corp.com.
jf_hotel was the name of the old NT domain...which seemed
to carry over. At least all the Domain choices on login
were jf_hotel. AD Users and services displayed it as ih-
corp.com.

Think I should trash the new AD controller, go back to my
old BDC and promote...then start the upgrade again?
Click to expand...
No , why would you want to do that? There is nothing wrong with the name you
have. As long as the primary DNS suffix matches the domain name you are good
to go. Even if the suffix does not match that can be fixed in 15 seconds.
To access external resources like email servers and web site all you need to
do is add host for www, mail etc. to the internal zone giving the public
address of the servers.
 
In
Mark said:
I actually gave the domain the new name of ih-corp.com.
jf_hotel was the name of the old NT domain...which seemed
to carry over. At least all the Domain choices on login
were jf_hotel. AD Users and services displayed it as ih-
corp.com.

Think I should trash the new AD controller, go back to my
old BDC and promote...then start the upgrade again?
Click to expand...

I just went back and re-read your original post are you saying your DNS
suffix is jf_hotel?
If so email me direct to verify your email address I will send you a script
to fix this, in 15 seconds, plus the time for a restart.
 
Back
Top