The thing to look at is router-to-router (also called LAN-to-LAN or
site-to-site) VPN connections. These connect up your sites so that they can
route (not bridge) between sites.
Apart from the routing, you need to consider the effect this will have
on your network. It will look just like two or more segments connected by a
router (a slow one!). Speaking of slowness, the link may be too slow for
database operations to operate reliably. If it is, consider using Terminal
Services. With TS, the "client" application runs on the Terminal Server
which has a high-speed connection to the database. Only the
display/keyboard/mouse data has to cross the VPN link.
"Ray Lavelle" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed) om...
> I have a couple locations that each have their own network and
> internet connection. One of these locations acts as a central server
> to the others. The central server contains a database server which
> all other locations must have access to. I don't want to have to make
> the database server accessable to the internet in order to give each
> location access to it. I was thinking about setting up a VPN to make
> this more secure so the database server can remain behind the firewall
> and can only be accessed through a VPN connection. I know how to set
> up a VPN but the problem is that each location must be able to have
> VPN access to the central location as well as access to their own
> network at the same time. Each location is going to remain connected
> to the central location all the time. The computer that connects to
> the central office at each location must also be able to have access
> to it's own network. Can I create a VPN connection at each location
> then bridge that with the local area connection?
> Any suggestions on how I can do this?
> Thanks...
|