Every ip subnet should be associated with a site within your enterprise. If
not a user is routed back to the default site. This can be a real problem
if a user is at a site with a slow link and they have a local dc yet
improper configuration sends the user back to the default site.
So you need to create your sites and site links for the network topology so
Active Directory can then run the Knowledge Consistency Checker (KCC) for
intrasite connection as well as the InterSite Topology Generator (ISTG) for
intersite connection. Once defined each subnet then needs to be associated
with a a site for the best connection to the site (Really best connection to
a DC).
Look at Meinolf's link, this is a best practice that will guide you through
the setup for your site questions.
--
Paul Bergson
MVP - Directory Services
MCITP - Enterprise Administrator
MCTS, MCT, MCSE, MCSA, MCP, Security +, BS CSci
2008, Vista, 2003, 2000 (Early Achiever), NT4
Microsoft's Thrive IT Pro of the Month - June 2009
http://www.pbbergs.com
Please no e-mails, any questions should be posted in the NewGroups. This
posting is provided "AS IS" with no warranties and confers no rights.
"tkutil" <> wrote in message
news:EF6DCF35-DA12-4F28-87C4-...
> Bringing up AD in our remote plants and I want to make sure I understand
> the
> Subnet portion.
> Is it as simple as entering the IP and Subnet mask we user per location?
>
> Once I create sites and associate subnets to the site do I need to also
> associate a subnet with the main site (default)?