Re: New Win2003 DC DNS into Win2000 AD with DNS

Hi Ace/Meinolf:

Thanks both for your response...

Ace:
Don't have the server in front of me right now, I've ditched the effort
after last night's (late) yet-another-spectacular-failure...

Meinolf:
Yes, the original/old Windows 2000 AD contains all the AD-integrated
zones...which is why I did what I did with the new DNS on Windows 2003 AD
controller - actually it was a pleasant surprise at first since I really
couldn't find documentation on how to do this properly. I just did things
"logically" so to speak (not to create a zone..because we already have one,
etc.)...the only documentation I found was about integrating into a DNS
infrastructure that wasn't AD integrated....

BUT, I can say that we can forego DNS...since last night's attempt didn't
even get me that far.

After "successfully" dcpromo-ing the new box, post sp2, things seemed well.
The idea was to try and isolate the issue so DNS wouldn't be installed in
this box. Well, after going through the litany of updates (Microsoft
Updates), on the box with SP2 and AD already running, the subsequent
required reboot brought me back to groundhog day..

So, although DNS doesn't seem to be the culprit, still clueless...thinking
it's one of the updates...

OR, there is this pesky FRS failure in the win2k AD (Event 13508 ) that I
didn't even think would be something to look at. There's not much
documentation on this either...only something about safe to disregard and
wait for the "success" event (Event 13509) which doesnt occur actually. All
checks about network connectivity are fine, rpc is running, so it's yet
another mystery..But if this is totally unrelated, this can wait(?)...or can
this cause such a devastating problem **specific to** a new Windows 2003 AD
controller? I'm saying this only because our existing Windows 2000 AD
controllers, even with this FRS event, are unaffected.

Thanks again ..


--

*~*~*~*~
Cheers,
Ed


"Meinolf Weber" <meiweb(nospam)@gmx.de> wrote in message
news:ff16fb66a55678cac28e08125620@xxxxxxxxxxxxxxxxxxxxxxx
Hello ed,

You said you setup no zones in DNS? Do you have created a zone with the
2000 DNS server after installing the first domain controller ther?

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and
confers no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

Hi all,

I really hope someone can offer guidance since this is turning out to
be one horrible "ground hog" experience.

Our task: Completely moving from Windows 2000 AD to Windows 2003 AD

What's already done: We've done the pre-introduction of a Windows 2003
AD controller (Adprep, etc.)

The issue in detail:
- Install windows 2003 server - this is an original cd (not even sp1).
- Install sp2
- join domain
- install AD
At this point everything is fine, or seems so. Then here's where the
problem
starts:
- install DNS, maybe we're doing it wrong here so advice on the proper
options may help.
- our selections are, primary and secondary, not to create any new
zones, no forwarding
- even this seems to go without a hitch since looking at DNS
management
shows the AD DNS is already replicated....
However, after this successful DNS installation, if we reboot (for
whatever
reason):
- the reboot process "stalls" a bit at "Preparing Network Connections"
- then the dreaded "At least one driver....failed"
- the reboot takes a long time but, you'll finally get to the login
screen
- after logging in, and this is where it's driving us nuts, you find
that
the NETWORK CONNECTIONS container is empty!
- you essentially can't see any of "MY CONNECTIONS"
- If you do a hardware check, the adapters are fine
- but you have absolutely no network connectivity
- obviously at this point, the EVENT LOG is stacked with errors...
Hope someone has some thoughts...I've gone cross-eyed with this....and
yes, the AD cleanup is a chore (manually removing the failed
controller from AD...at least that seems to be going smoothly).

Thanks in advance!






.

Relevant Pages

  • Re: Domain users
    ... for the DNS Server. ... User in the Domain and an Administrator in Windows XP still has all its ... > "George Hester" wrote in message ... >>> As a regular user they will not be able to install much of anything. ...
    (microsoft.public.win2000.group_policy)
  • Re: Reboot several times a day
    ... I was using either RAID 0 or 1; one controller on the MB the other was ... > Running programmes written long before the introduction of Windows XP ... clean install of XP on new hard drives and ... >> as far as the id in the event viewer is concerned. ...
    (microsoft.public.windowsxp.general)
  • Re: Install Problem at GUI Startup
    ... After completing the install and getting to the "NTLDR Missing" error, ... directory or trying to boot from a directory other than the root. ... How to troubleshoot the "NTLDR is missing" error message in Windows Server ... I am using the non promise controller exactly as you suggest. ...
    (microsoft.public.windows.server.sbs)
  • Re: installing windows
    ... Windows help - www.rickrogers.org ... > Controller" and the modem. ... Install them one at a time. ...
    (microsoft.public.windowsxp.general)
  • Re: New Win2003 DC DNS into Win2000 AD with DNS
    ... Windows 2003 Server AD Domain controller loses all network connectivity ... Windows 2003 Server Network Connections Container Empty After SP1 or SP2 ... zones...which is why I did what I did with the new DNS on Windows 2003 ... Install sp2 ...
    (microsoft.public.windows.server.active_directory)