1. You want static IP#s at both ends. A simple phone call to the ISP
usually fixes that.
2. You need Internet Sharing Devices to replace you current ones that are
capable of (on their own) establishing a Site-to-Site VPN. This is a
specific type of VPN,...it is *not* the same thing as the human initiated
dial-up based Remote Access VPN.
3. You need a Syncronous Internet Connection (same speed both directions).
Cable internet accounts do not provide this. This can be done with SDSL (not
ADSL), T1 lines, and Frame Relay lines (a T1 refers to speed and can be a
frame relay, DSL, or other).
The reason for #3 is that VPN will always sync up to the slower "upload
speed" of the line which in some cases can be as low as 128mbps but is most
commonly 256 or 512 mbps.
Once everything is done properly it will act as one big happy LAN without
the machines on the LAN even being aware of it. However VPN is alway a poor
performer (don't buy into the "marketing hype"). It will always be painfully
slow over the WAN link with file sharing. Copying files over any kind of
link is the most intensive bandwidth hog that you can ever do. Audio & Video
are not the worst,...that is just a "stereotype" that the average person has
bought into. File copying is the worst.
--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
<(E-Mail Removed)> wrote in message
news:(E-Mail Removed) ups.com...
> We are looking for the best recommendation for the following situation
> for sharing files on our server across a WAN. In Building A (call it
> BA), our server is Windows 2003 Standard Edition and it has (1) network
>
> card with (3) XP client computers and is a DC. We access the Internet
> via a cable connection. We do not currently have a Static IP address
> from our ISP. We have text documents & a database file for a program we
>
> use on the clients located on this server. We want to access these
> documents and database file from Building B (call it BB) which is (2-3)
>
> blocks away from BA and has (3) XP workstations, WITHOUT a server,
> currently sharing a cable Internet connection The workstations in BB
> run the same programs (software is installed locally) as those in BA,
> but need access to the database file and documents in BA.
>
> We are familiar with setting up VPNs using SBS2000 and remotely
> accessing workstations on a network using RDC. However, there may be
> occasion where users in BA will be using their computers and we would
> not want to permit a RDC to those PCs just in order run the approriate
> software or open shared documents.
>
> What hardware,setup would be required in BA and BB to configure this
> remote/WAN access?
> What are the latest,greatest technology options to accomplish this?
>
> We are assuming a Static IP in BA, adding another NIC (to isolate
> internal network from external) and new router with VPN support are
> necessary?
>
> Would it be necessary for both sites to have a Static IP?
> Any recommendations on reading about Branch office setups?
>
> When a Site-to-site VPN is setup, to the branch office users just login
> in to the domain and use resources as if they were at the Main Branch??
>
> Thanks!
>
Similar Threads
Linear Mode
