Connectivity between 2 physical locations

[Guest]

I have a windows 2000 Active Directory integrated domain in Building A. I have a couple of servers and internet connectivity through T1 circuits in building A. I have to expand in another building B very soon. How do I connect the two buildings so that I can seamlessly access the resources between both the buildings (webservers, databse server etc). Do I need to create a separate Active directory domain in building B or can I allow workstations in Building B to authenticate with the DC's in Building A.

What is the most ideal scenario?

 

[Sean Siler]

As long as A and B are well connected (I assume by the T1 you previously
mentioned) then you have plenty of options.

Do you mind if users in A log on to a DC in B? (Probably not, if you have
plenty of bandwidth)
Also, are they going to be in the same IP subnet or a different one
(Probably a different on, spearated by a router)

Assuming a lot of things here, I would say you are probably best to use a
single site, and assign multiple subnets to the site in the AD Sites and
Subnets snap in. Since both subnets are in the same site, users in either
building can access resources and be authenticated by servers in either
building just as if they were all in one big building.

Make sense?

Sean Siler

I have a windows 2000 Active Directory integrated domain in Building A. I

have a couple of servers and internet connectivity through T1 circuits in
building A. I have to expand in another building B very soon. How do I
connect the two buildings so that I can seamlessly access the resources
between both the buildings (webservers, databse server etc). Do I need to
create a separate Active directory domain in building B or can I allow
workstations in Building B to authenticate with the DC's in Building A.