Re: 2nd DC and DHCP?
- From: "Jorge Silva" <jorgesilva_pt@xxxxxxxxxxx>
- Date: Sun, 30 Jul 2006 15:50:08 +0100
Hi
Actually I have this working in a SBS2003 SP1 and I didn't recall having
made any change, I now that in SBS2003 no SP when the DHCP service detected
another DHCP in the network then it stop to prevent duplicated address. As
far as I remember all I had to do (SBS2003 SP1) was to authorize the other
DHCP server and perform that configuration, but I can't confirm this at this
point.
As I already said, in DNS AD integrated it will replicate automatically to
the other server.
As to the GC, he can make the other server a GC, however GCs are only needed
when you have multiple domains in one forest, and SBS doesn't support
multiple domains, anyway you can always make the other a GC, no problem with
that.
--
I hope that the information above helps you
Good Luck
Jorge Silva
MCSA
Systems Administrator
"/kj" <kj@xxxxxxxxxxx> wrote in message
news:OmSZiX2sGHA.1284@xxxxxxxxxxxxxxxxxxxxxxx
SBS DHCP has a modification that checks for other DHCP servers on the
subnet and if found, the SBS DHCP server will refuse to start. Therefor
the normal 80/20 doesn't work for SBS2003 enviroments without unsupported
modifications.
Likely the logon fail was due to lacking DNS and a GC.
"Jorge Silva" <jorgesilva_pt@xxxxxxxxxxx> wrote in message
news:%23tCjVS0sGHA.1596@xxxxxxxxxxxxxxxxxxxxxxx
Hi
With a SBS2K3 environment and a W2K3 acting as a secondary controller,
what
happens with DHCP and DNS.
- If your clients are using DHCP you would want to have a DHCP installed
in the Second Server 80/20 DHCP configuration.
- It's Imperative to have DNS in a DC, make sure that is AD integrated to
avoid SBS errors.
I ran the wizard to create the 2nd DC and then shut down the primary.
Couldn't log in.
Then I noticed there was no DHCP or DNS on the 2nd DC, which might
explain
the "no login" issue.
Make sure that the the clients have the 2nd DC in their NIC DNS
properties as secondary DNS server.
So, I suspect I need to configure DHCP/DNS on this box but want to do it
in
a way that doesn't conflict with the primary.
Any ideas?
No conflits needed. Make sure that the DNS is AD integrated and it will
be automatically replicade to the 2nd server, as for the DHCP you can
make a DHCP 80/20 configuration, googleit.
--
I hope that the information above helps you
Good Luck
Jorge Silva
MCSA
Systems Administrator
"Denis" <Denis@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:DBB36B62-651B-4015-9752-48A2288806A1@xxxxxxxxxxxxxxxx
With a SBS2K3 environment and a W2K3 acting as a secondary controller,
what
happens with DHCP and DNS.
I ran the wizard to create the 2nd DC and then shut down the primary.
Couldn't log in.
Then I noticed there was no DHCP or DNS on the 2nd DC, which might
explain
the "no login" issue.
So, I suspect I need to configure DHCP/DNS on this box but want to do it
in
a way that doesn't conflict with the primary.
Any ideas?
Thanks
Denis
.
- Follow-Ups:
- Re: 2nd DC and DHCP?
- From: kj
- Re: 2nd DC and DHCP?
- References:
- Re: 2nd DC and DHCP?
- From: Jorge Silva
- Re: 2nd DC and DHCP?
- From: /kj
- Re: 2nd DC and DHCP?
- Prev by Date: Re: R2 in-place upgrade bug ? ..HELP
- Next by Date: Re: Receiving access denied accessing 2000 domain controller
- Previous by thread: Re: 2nd DC and DHCP?
- Next by thread: Re: 2nd DC and DHCP?
- Index(es):
Relevant Pages
|
Loading