J
Joel
Hi,
The issue I am having was sparked by an SMS question/problem. But this
may really be more of an Active Directory and Windows 2000 Server question.
It has to do with the design of an environment I take care of that has 2
domain controllers that reside on different subnets.
Please read my question below--it may seem like an sms question, but perhaps
it is more of an AD question. I am not sure I'll be able to actually do
anything about it at the moment, but I am interested in knowing what the
best or most healthy practice might be in this situation. Thanks!
I have a win2k domain with 2 domain controllers. DC1 serves as the SMS 2.0
server and DC2 serves as logon point, distribution point, CAP, and whatever
other roles domain controllers play in SMS.
The problem I am experiencing is that I frequently get critical errors in
the site system status summarizer about DC2. The errors about DC2 are
straight down the line. I am quite sure that these errors are generated due
to temporary network connectivity problems between DC1 and DC2. DC1 and DC2
reside within the same building but are on different subnets.
After futzing around with the service manager, I can usually get most of the
errors to clear with the exception of the "distribution point" error. And
then the whole thing happens all over again a day or two later.
My question: Would it be better or advantageous for the health of the
systems/domain for the two domain controllers to be on the same
subnet/switch? Or are there any pros to having things configured the way we
have it currently?
Thanks for any ideas. Currently, we are in production mode and I'd hate to
change things around, but at the same time, I would want to do so for the
sake of the overal health of the domain. /Joel
The issue I am having was sparked by an SMS question/problem. But this
may really be more of an Active Directory and Windows 2000 Server question.
It has to do with the design of an environment I take care of that has 2
domain controllers that reside on different subnets.
Please read my question below--it may seem like an sms question, but perhaps
it is more of an AD question. I am not sure I'll be able to actually do
anything about it at the moment, but I am interested in knowing what the
best or most healthy practice might be in this situation. Thanks!
I have a win2k domain with 2 domain controllers. DC1 serves as the SMS 2.0
server and DC2 serves as logon point, distribution point, CAP, and whatever
other roles domain controllers play in SMS.
The problem I am experiencing is that I frequently get critical errors in
the site system status summarizer about DC2. The errors about DC2 are
straight down the line. I am quite sure that these errors are generated due
to temporary network connectivity problems between DC1 and DC2. DC1 and DC2
reside within the same building but are on different subnets.
After futzing around with the service manager, I can usually get most of the
errors to clear with the exception of the "distribution point" error. And
then the whole thing happens all over again a day or two later.
My question: Would it be better or advantageous for the health of the
systems/domain for the two domain controllers to be on the same
subnet/switch? Or are there any pros to having things configured the way we
have it currently?
Thanks for any ideas. Currently, we are in production mode and I'd hate to
change things around, but at the same time, I would want to do so for the
sake of the overal health of the domain. /Joel