SG Broadband Community

Someone help me in this?

Our company is opening a new Branch office that is 1000 miles away from the
main office...All our servers are Windows 2003 and all our clients use XP
Pro. Both locations have a Broadband connection to the internet. We have five static (Public) IP address on both ends for the company. Just a connection to the internet through leased line..

I want to create a domain at main office ‘A’ and additional domain at branch office ‘B’ so that office ‘B’ user directly login at domain ‘A’ and all the users information, changes and data must be replicated and synchronized with both offices domain. Once the site to site link is in place machines in site ‘A’ can directly contact machines in site ‘B’ and vice versa

That both

what are the requirements? Can we resolve our problem by using any Microsoft technology? Do we need a router at each location?

PLEASE show me in steps like 1 2 3 what to do A-Z

Thanks
Khurshid

How many PCs at each? I'd probably just take the "router to router VPN tunnel" approach...have routers at each end maintain a VPN tunnel.

Depending on the number of computers at location B...unless its very large, I'd probably just keep this a single domain that both sites have...and have a second domain controller at site B.

Information between the two...this would depend on what it is your are running..for software. Either database servers at both sides, that replicate back 'n forth, or a terminal server at the main site..that users from site B log into. Several different approaches...need much more information.

yea VPN tunnel approach is better and U have just mentioned the microsoft technology for implementing this- domain replication and i don think u need a router if ur implementing VPN tunnnel approach

YeOldeStonecat wrote:How many PCs at each? I'd probably just take the "router to router VPN tunnel" approach...have routers at each end maintain a VPN tunnel.

Depending on the number of computers at location B...unless its very large, I'd probably just keep this a single domain that both sites have...and have a second domain controller at site B.

Information between the two...this would depend on what it is your are running..for software. Either database servers at both sides, that replicate back 'n forth, or a terminal server at the main site..that users from site B log into. Several different approaches...need much more information.

Thanks for reply !
And sorry for late..........
we have fourty PCs at each end.I want to kept terminal server at main site that users from site B log into.Database will accessed locally at Site B.
So which series of router we need for that?
Can we do it without help of router?

For a terminal server at the main site...you have at least a couple of different choices.

*Just publish the terminal server on the public side at the main site. Open/forward port 3389 on your firewall....to the internal IP address of your terminal server. All users of the terminal server just access it across the internet to the WAN IP address (or dns alias you make). Naturally since the terminal server is made "public" on the internet..you want good passwords on your user accounts..and go through some lockdown proceedures on it.

*Setup a VPN appliance at your main site. Whoever needs to access the terminal server will have to VPN into the main site to access it. This way..your terminal server is not exposed to the internet. The can add some issues for users at site B...being able to access LAN resources at site B..depending on what type of VPN package you choose.

*Setup a VPN tunnel between both sites...and users at the second site access the terminal server securely through the tunnel. Terminal server remains safe behind site As firewall...not exposed to the internet.