Creating a WAN between 2 companies.

Hello everyone,

I have an interesting challenge coming up for me in the future, so I am

gathering information right now. The company I am working for (I'll
call them company A) is going to be buying another company in a
different state (Company B). We want to set up a network at company B
and have it be connected to our network as if they were in the same
building.

I have never done this before, so my question is how do I go about
starting this? What types of things do I need to research. What type of

hardware/software should I be looking into? What are the challenges?
Can I have these networks on the same domain?

I have setup and used VPN before, but this has just been between my
home computer
and the network at Company A. I am guessing that I would need to setup
something similar between the server at Company A and the server at
Company B.

Thanks

Hello "XxLicherxX"?

Yes the 2 companies can share the same domain.
Suggested design:
1. Depending on total number of PCs put a W2k3 or SBS2k3 DC (domain
controller) in company A. You can also install E2k3 (Exchange) as well.

2. Put a W2k3 DC in company B (can't be SBS - only 1 per domain ;-(, same
domain, but make it a separate "Site". (This will allow them to set up
replication of Active Directory, etc.). If you have the same e-mail domain,
put E2k3 as a different "Routing Group" (used to be called "Site" til the
W2k3 team stole the name ;-).

3. Configure a special type of VPN between the 2 servers called a
Demand-dial VPN-VPN connection (it is called Demand-dial, but can be set for
persistent). This is *much* better than the client connections you have
made in the past: it comes up and connects by itself after either PC is
rebooted without having to logon. You can use PPTP or L2TP. This
connection will be used for server-server AD replication AND Exchange to
Exchange communication.

4. Set up the E2k3 server in site A as a "bridegehead" server: all the mail
for hte domain will come into it, then it will forward mail to site B if the
recipient is there.

That is the framework I would suggest, and there are many, many articles in
TechNet on how to do these: just search the key words in the outline above.
In W2k3 server help, there is also a blip: "PPTP-based router-to-router VPN
deployment ". E2k3 has a Deployment Guide which talks about bridgeheads,
etc. This architecture is commonly used in "branch office" scenarios - so
search on that too.

Hope that helps some,
Harvey Juster, MCSE

Hi Harvey,

Thanks for the reply, that has cleared up a lot. Some of this is
already in place here at Company A. (Exchange 2003 and SBS). I do have
a few questions (and I'm sure I will be posting again when I actually
start doing this) at the moment.

Currently at Company A we have an older server running ISA 2000 for our
firewall/VPN. I haven't read the blip about router to router VPN yet,
but will be doing so today. What I am thinking at the moment would be
best to do is to have ISA 2004 installed on each server that will serve
as an end to the VPN tunnel. Is this what you would recommend? If so,
would it be better to install ISA 2004 on SBS or W2003 Standard at
company A?

Also I just want a clarification of:
" it comes up and connects by itself after either PC is rebooted
without having to logon."

PC refers to Server, Correct?

Thanks again for your response

"XxLicherxX" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed) oups.com...
> Hi Harvey,
>
> Thanks for the reply, that has cleared up a lot. Some of this is
> already in place here at Company A. (Exchange 2003 and SBS). I do have
> a few questions (and I'm sure I will be posting again when I actually
> start doing this) at the moment.
>
> Currently at Company A we have an older server running ISA 2000 for our
> firewall/VPN. I haven't read the blip about router to router VPN yet,
> but will be doing so today. What I am thinking at the moment would be
> best to do is to have ISA 2004 installed on each server that will serve
> as an end to the VPN tunnel. Is this what you would recommend? If so,
> would it be better to install ISA 2004 on SBS or W2003 Standard at
> company A?

Sorry XxLicherxX, I have not done this with ISA involved: it probably
introduces more complications - opening the correct ports and protocols (but
is more secure). Some of the TechNet articles may address it, or you can
post to the ISA newgroup once you have everything else planned out.
As for ISA2k4, if you are under 74 seats total, SBS premium is the way to go
IMO, if just for the wizards, backup shell, and most usefully, Remote Web
Workplace. If they need SQL, then it is even better deal. MS says if you
are using 3/4 apps, it is cost competitive with the individual components
CALS.

Regards,
Harvey
>
> Also I just want a clarification of:
> " it comes up and connects by itself after either PC is rebooted
> without having to logon."
>
> PC refers to Server, Correct?

Yes, correct.

>
> Thanks again for your response
>
>