Re: AD from 2000 to 2003

"juicejug" <juicejug.2f4mwf@xxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:juicejug.2f4mwf@xxxxxxxxxxxxxxxxxxxxxxxxx

I have a 2000 set up with AD with name domain.local

When I try to connect my new 2003 box and dcpromo as an additional
controller, it fails stating srv reasons.

Which DNS server is this 2003 box using? (It must use
strictly the internal DNS server [set] which is able to
resolve your DCs etc.)

Also, have you performed ADPrep for both /ForestPrep and
/DomainPrep? This is required before introducing the first
Win2003 DC into a Win2000 Domain.

On the 2000 box, when I run
netdiag /fix, it causes fatal errors. I also ran dcdiag with errors.

And this was my next suggestion: You need to run DCDiag on
every DC and fix those errors.

DNS problems are the usual reason for failure to authenticate
and to replicate which includes DCPromo.

I realize this problem looks related to the single-label,

Not at all since you listed the Domain name with two labels:

domain.local

however the
domain we use is also the same as the domain name for the web site
which is hosted by external web hosts (due to bandwidth reasons).

Not if you are using .local -- if you aren't using that then it
was misleading to say domain.local and not domain.com.

You should NOT however define the A record with the DOMAIN
name in the internal DNS server for the zone that supports AD --
the DCs use this record.

You may still contact the Web server using the www or other
prefix however, just not the bare domain name.

The reason for this upgrade is so that we can also run exchange server
on site (which is being hosted by the web host now).
What is my best method for allowing all parts to work?

You could start by putting the Win2003 Server CD in the
Win2000 box and letting it help you DCPromo that but my
FIRST goal would be a clean DCDiag on every DC.


--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]



--
juicejug
------------------------------------------------------------------------
Posted via http://www.webservertalk.com
------------------------------------------------------------------------
View this thread: http://www.webservertalk.com/message1688112.html



.

Relevant Pages

  • Re: AD from 2000 to 2003
    ... Expected if the second failed DCPromo. ... They must use STRICTLY the Internal DNS server set -- ... The following is an INCOMPLETE DCDiag but the problem ...
    (microsoft.public.win2000.dns)
  • Re: AD from 2000 to 2003
    ... When I try to connect my new 2003 box and dcpromo as an additional ... Which DNS server is this 2003 box using? ... And this was my next suggestion: You need to run DCDiag on ...
    (microsoft.public.win2000.dns)
  • RE: Multiple Public Domains on 1 SBS Certificate
    ... Nevertheless who control your external DNS server, ... Microsoft CSS Online Newsgroup Support ... Multiple Public Domains on 1 SBS Certificate ... >NS and MX records that point to the physical web site. ...
    (microsoft.public.windows.server.sbs)
  • Re: Disaster recovery and NTDSUTIL
    ... Have you done a dcpromo /force to remove the local AD info? ... done then you should go back and cleanup metadata ... Make sure the other Domain Controller is a Global Catalog server, ... Run dcdiag, netdiag and repadmin in verbose mode. ...
    (microsoft.public.win2000.active_directory)
  • Re: Browsing Default Web Site (SharePoint) with IIS Problem
    ... Nor should a dcpromo have actually removed your machine from the domain. ... Certain inbuilt IIS accounts would have become domain accounts when you dcpromo-ed the box, but wouldn't have returned to being local accounts when you ran the second dcpromo. ... Since we're not sure what state your box is currently in, you may wish to backup your Sharepoint database. ... On my default web site, which happens to be a SharePoint 2003 site, I had to reset all the permissions on both IIS and SQL in order to get the site back up and running. ...
    (microsoft.public.inetserver.iis.security)