Re: New Win2003 DC DNS into Win2000 AD with DNS

Hi Ace/Meinolf,

Well, cheers are in order!

This link, http://support.microsoft.com/kb/930220, will go into the record
books as both as a:
- great resource for this mind-numbing issue
- an example of mind-numbing issues that customers really don't have to go
through. It has references to SP1, so one would think this wouldn't drive
customers totally nuts when SP2 came out. Geesh....

Anyway thanks to both of you! Your efforts are very much appreciated!

References/keywords to this issue (for future poor souls - hope this saves
you time, a LOT of time, and agony):

Event ID 32777
Windows 2003 Server AD Domain controller loses all network connectivity
IPSec Block
Windows 2003 Server Network Connections Container Empty After SP1 or SP2

--
Cheers,
Ed Chavez
A bona fide Microsoft drone





"Ed" <ed@xxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:%23FMtqDp9IHA.1204@xxxxxxxxxxxxxxxxxxxxxxx
Hi Ace/Meinolf,

I think I'm not alone. I'm experiencing the exact same thing that anyone
else with the Event ID 32777 issue...which basically is total loss of
communications on the new Windows 2003 AD server.

Am currently reading up on it, but if anyone here has the
"correct"/accepted fix or a link to it, that would be TREMENDOUSLY
appreciated.

This link seems promising:
http://support.microsoft.com/kb/930220

as it almost replicates what I'm seeing in Event Viewer....

--
Cheers,
Ed Chavez
A bona fide Microsoft drone





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

As Ace said please post an unedited ipconfig /all. Also a dcdiag, netdiag
and repadmin /showrepl can be helpful. If your ip addresses start with
10.x.x.x 172.x.x.x oe 192.x.x.x you can post them without any problem.
Nobody can use them to connect to your machines.

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 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 ..

"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: DC/ DNS 2000 to 2003 Migration
    ... Add Windows 2003 server to domain ... Install DNS ... When promoting a 2003 server into a 2000 domain, ... Hotfixes to Install on Windows 2000 Domain Controllers Before Running Adprep ...
    (microsoft.public.windows.server.active_directory)
  • Re: DC/ DNS 2000 to 2003 Migration
    ... Add Windows 2003 server to domain ... Install DNS ... When promoting a 2003 server into a 2000 domain, ... Hotfixes to Install on Windows 2000 Domain Controllers Before Running Adprep ...
    (microsoft.public.windows.server.active_directory)
  • 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)
  • Re: NT Domain to AD migration
    ... Windows 2000/XP always prefer Kerberos authentication, ... Server 2003 Active Directory service, ensure that you have designed a DNS ...
    (microsoft.public.windows.server.active_directory)
Loading