Re: Primary & secondary DC's in Win2k domain


Herb Martin;3449236 Wrote:
They are still just BOTH DCs even if you consider one of them to be your
"main" one.
I realise that. My main question was whether there was a way in which
we could prevent the DC which is really just there for failover from
doing ALL the work. If the answer is no then I guess one option would
be to promote one of the less important member servers to the role of
DC and demote the main fileserver out of the DC group and leave it to
concentrate on its main role.

Herb Martin;3449236 Wrote:
The DHCP behavior has NOTHING to do with the fact of being (or not
being) a DC.
You misunderstand. I was using the term DC to denote which machine I
was talking about. I should have been clearer. Sorry. The "backup"
DC is also the backup for a number of other services, including DHCP.
It's just that DHCP is the most visible example of the "wrong" server
doing all the work.

Herb Martin;3449236 Wrote:
Then it is authorized. Likely it is just SLOWER at responding. The
fastest DHCP server will "offer" and address first and generally the
clients will request an address for the FIRST to respond.
I did wonder that but the "main" DC should be quicker. Apparently
not.

Herb Martin;3449236 Wrote:
Not really -- and there is seldom a reason to care about this.

Check (with DCDiag) for REAL problems and quit worrying about
something unimportant if there are no real issues. (Really the best
help
we can offer if you don't have a broken DC or DHCP or DNS etc.)
Idle questions really, not any great worrying going on. I am changing
a number of functions within the network to increase resilience to
potential problems. Not all changes have produced the behaviour I
expected so I am just trying to understand a little more about it in
case I was overlooking something. The resulting behaviour is doing the
job intended but not distributing the load in the manner I had expected
that's all.

Until I arrived the "main" DC (and ONLY DHCP and Global Catalog server,
the only AD which could talk to Exchange and complete with all FSMO
roles as well) was a very old retired workstation, called THOR (a PII
400Mhz, small and old IDE HDD, not much RAM) without which nothing
useful function properly. That didn't seem like a very good idea to me
hence the changes.

Many thanks for your response.


--
plesbit
------------------------------------------------------------------------
plesbit's Profile: http://forums.techarena.in/member.php?userid=39364
View this thread: http://forums.techarena.in/showthread.php?t=890598

http://forums.techarena.in

.

Relevant Pages

  • Re: Adding additional WINS server
    ... reduce the router to only doing 'router' functions (gateway, forwarding, ... "Herb Martin" wrote: ... >> When you do decide to stand up a DHCP server on a Windows server, ...
    (microsoft.public.windows.server.dns)
  • Re: Primary & secondary DCs in Win2k domain
    ... Herb Martin;3449236 Wrote: ... DC is also the backup for a number of other services, including DHCP. ... It's just that DHCP is the most visible example of the "wrong" server ... Check for REAL problems and quit worrying about ...
    (microsoft.public.windows.server.active_directory)
  • Re: Windows 2003 server causes router to crash
    ... Many thanks Herb, I'll take another look a the things that you suggest. ... so I find it hard to beleive that the router has an inherent fault ... only appeared with the arrival of the server, and it disappears if the server ... the router provides DHCP and firewall. ...
    (microsoft.public.windows.server.networking)
  • Re: Strange problem with WINS
    ... "pete horm" wrote in message ... and have no defaut if you use DHCP so it seems likely ... in NetBIOS resolution behavior. ... Herb Martin> pete ...
    (microsoft.public.windows.server.networking)
  • Re: DHCP initial setup
    ... "Sam" wrote in message ... range that must not however be distributed by THIS DHCP ... Herb Martin ... Create scope for each subnet. ...
    (microsoft.public.win2000.networking)
Loading