Hub and spoke, then definately Shook's recommendation. You don't want users in remote office A going to DC2 in remote office B for authentication.
>>> "Joe Heaton" <[EMAIL PROTECTED]> 3/25/2008 1:50 PM >>> That's the method I thought it should be, but that's not what they set up initially, whenever they setup the network. My thoughts were hub and spoke configuration. Joe Heaton From: Andy Shook [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 25, 2008 9:50 AM To: NT System Admin Issues Subject: RE: Site link best practices? Usually I base this decision on geography, DC location and bandwidth between physical sites. Since you have DCs everywhere and the sites and subnets are in place, I would have a site link for each site back to the CO. Shook http://www.linkedin.com/in/andyshook From:Joe Heaton [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 25, 2008 11:37 AM To: NT System Admin Issues Subject: Site link best practices? Anyone have suggestions for best practices for site links? My network consists of a central office, and 3 branch offices, all connected through our ISP to look and act as one network. We have DCs at each branch, and 2 DCs here at the central office. Currently we have one site link, with all 4 sites listed in it. Is this acceptable practice, or should there be a separate link for each site back to the central site? Joe Heaton AISA Employment Training Panel 1100 J Street, 4th Floor Sacramento, CA 95814 (916) 327-5276 [EMAIL PROTECTED] Confidentiality Notice: This e-mail message, including attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure, or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~
