I need to connect three branch offices back to our main office. I have purchased three 1750's with VPN cards and ordered T1 lines for each location. The main office has 25 users and each branch about 10. A couple questions:
Should the main office use something larger than a 1750? One branh office is new so I need to buy another router anyway. So I was thinking if I need to buy a larger one for the main office then I could send the existing 1750 to the branch.
Does this sound like a reasonable plan? Using Internet T1's to create a multi-state network? I'm not sure what issues I will run into in terms of usable bandwidth, latency issues, etc...
I'm fairly new to the wan side of networking but have 15 years with networks in general. Would appreciate any thoughts and comments.
Just finished doing the same with three branch offices and one HQ. We used C1720 with the VPN Module in all sites. Used ADSL for Internet and speed is fine. The remote sites access a Windows Terminal server at the HQ. Each remote is 5-10 users. Works as designed.
Now doing a site with six remotes and one HQ. Using the C1720 VPN bundles again for all the remote sites and a C3640 with IP/FW IPSec feature set, Remote clients login to a Netware 5.1 server via the VLAN. All programs are local to the remote sites and data is local to the Netware server at the HQ. Also accessing SQL services remotely. Beacuse don'y know what will be accessed through HQ site (DMZ with PIX being discussed) went with the C3640 to handle all options.
Cisco techs said that the 1720/1750 with VPN modules are fine for this traffic. Hopes this helps.
Table of ContentsIntroductionVersion HistoryPossible Future
UpdatesDocuments PurposeNAT Operation in ASA 8.3+ SectionsRule Types
Network Object NATTwice NAT / Manual NATRule Types used per SectionNAT
Types used with Twice NAT / Manual NAT and Network Obje...
[toc:faq]Introduction:This document describes details on how NAT-T
works.Background:ESP encrypts all critical information, encapsulating
the entire inner TCP/UDP datagram within an ESP header. ESP is an IP
protocol in the same sense that TCP and UDP are I...