Re: New Win2003 DC DNS into Win2000 AD with DNS

Tech-Archive recommends: Speed Up your PC by fixing your registry



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: Secondary DNS Zone questions?
    ... > install DNS on the remote server? ... If I may add to the other posts, Active Directory Integrated zones are ... Windows 2003 Support Tools that you would need to install (found on the ...
    (microsoft.public.windows.server.dns)
  • Re: Preparing network connection after AD install
    ... I didn't install exchange yet. ... known symptoms of having exchange installed on DC and bad DNS ... Do not place the ISP DNS server or any other DNS on the ...
    (microsoft.public.windows.server.active_directory)
  • Re: DNS replication on new server
    ... When I set up my second dns/domain controller, ... populated for Forward Lookup Zones and Reverse Lookup Zones. ... How would I test if both dns are providing services- besides turning off ... I find it best to install DNS ...
    (microsoft.public.windows.server.dns)
  • 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: New Win2003 DC DNS into Win2000 AD with DNS
    ... 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 ... Install sp2 ...
    (microsoft.public.windows.server.active_directory)