Re: Very Strange Problem Adding Additional DC's
- From: Z <Z@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 2 May 2007 12:46:00 -0700
The guidance is dont run Domain Controllers in a virtual enviorement. Use
physical boxes for domain controllers thats what MS suggest and me
to............
--
Z
"[c]" wrote:
Anyone? Would really to get this resolved and looking for a little guidance..
Thanks
"[c]" <no@xxxxxxxxx> wrote in message
news:%23qJ0fyLjHHA.4516@xxxxxxxxxxxxxxxxxxxxxxx
Hi All,
Would really appreciate a helping hand on this one. Sorry its a long
winded.
Okay here's the scenario, our primary site has two DC's. DC1 and DC2. We
wanted to start virtualizing so I started with DC2. I demoted it from AD
(yes, using dcpromo) and rebuilt it in a virtual environment since I read
about issues p2v'ing DC's. It seems that since that time though I have had
nothing but problems. Any client that authenticates against that DC,
well...they dont. So I demoted it after reading about a number of issues
with DC's in virtual environments and wanted to rebuild it on a physical
box again for the peace of mind.
I have done many of these and never had a problem. So I rebuilt this new
DC on a new physical box, giving it a new never before used static IP and
even a new never used before hostname of DC04. Its running Windows 2003
SP2. The primary DNS address is itself, the secondary DNS address is the
primary DC holding th master roles. This server holds no master roles
except acts as a GC.
As mentioned, if i run a set logon on any servers that are pointing to
this DC they can not authenticate on the network or allow clients to
connect. Our exchange server is the biggest issue as we service about 550
mailboxes and this effects all users if the server happens to use this
newly rebuilt DC and we all know its reliance on a functioning DC.
Initially DNS was not installed on this new build and did not prompt to
install like it normally does through the DC promotion process. So I
installed DNS after it was configured as a DC. I then later uninstalled
DNS, demoted the DC and reinstalled DNS and promoted again to be on the
safe side knowing that DNS was there for it, it should detect and
configure itself. The DNS console showed as not configured even though
clicking the properties of the DC04 showed as using AD integrated DNS, not
sure if this is/was safe to ignore or not.
Am I going wrong somewhere and just dont realize it? Should the primary
DNS address on DC4 point to DC1? Should I be doing something differently
with DNS setup on the server itself? I have never had this problem before
and I have configured a number of DC's with different companies. I am
thinking there is some other underlying problem but Im not sure what it
is. Reason I say that, is after rebuilding this new dc....dc4, yesterday
with a different IP the mail server doesnt even point to that server's IP
in DNS now and was giving the same grief it was yesterday where clients
couldnt connect to mail. And its not just internal. I tried through POP3
and OWA and the same thing....VERY slow, would time out, display one
screen after a minute, etc. So the mail server dns is pointing to the
primary DNS/DC server and the older no longer available DC.
Really need to get this resolved ASAP as Im running with only one DC for
now to service 500+ people and I dont like the consequences of it going
offline for any reason.
Thanks!
- Follow-Ups:
- Re: Very Strange Problem Adding Additional DC's
- From: Jack Doyle
- Re: Very Strange Problem Adding Additional DC's
- References:
- Prev by Date: Front end app to ad users to our AD
- Next by Date: Re: Very Strange Problem Adding Additional DC's
- Previous by thread: Re: Very Strange Problem Adding Additional DC's
- Next by thread: Re: Very Strange Problem Adding Additional DC's
- Index(es):
Relevant Pages
|
