10-04-06 01:23 PM
quote:
Originally posted by Herb Martin
"juicejug" <juicejug.2f4mwf@mail.webservertalk.com> wrote in message
news:juicejug.2f4mwf@mail.webservertalk.com...
>
> 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
>
The problem is when I run dcdiag. There is only one DC. Here is the output
when I run dcdiag on that server:
Testing server: Default-First-Site-Name\DCSERVER
Starting test: Connectivity
DCSERVER's server GUID DNS name could not be resolved to an
IP address. Check the DNS server, DHCP, server name, etc
Although the Guid DNS name
(d20b1a9e-4917-4a9b-9de8-1db3ef216810._msdcs.domain.local)
couldn't be resolved, the server name (DCSERVER) resolved to the IP
address (192.168.1.30) and was pingable. Check that the IP address
is
registered correctly with the DNS server.
......................... DCSERVER failed test Connectivity
Doing primary tests
Testing server: Default-First-Site-Name\DCSERVER
Skipping all tests, because server DCSERVER is
not responding to directory service requests
Running enterprise tests on : domain.local
Starting test: Intersite
......................... domain.local passed test Intersite
Starting test: FsmoCheck
......................... domain.local passed test FsmoCheck
Thanks
[ Post a follow-up to this message ]
| 
