IT Employment

General discussion


T1 VPN vs T1 Point to Point

By gli ·
We are in the NYC area. We currently have 3 locations, but we are looking to open 2-3 more locations in NYC and then expand outside of NYC after that. We need all our locations to connect to our central office, at all time...for our database and phone system. Which would be a better idea, VPN or PTP? How much of a speed difference between the two?

Currently we use PTP for our 3 locations.

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Comments

Collapse -


by johnnywatt In reply to T1 VPN vs T1 Point to Poi ...

Considering you mention, "connect to our central office, at all time", the answer is a point to point solution. Whether it is acceptable in the budget is another story.
VPN tunnel links using the public internet is just that, the public internet. If the internet has problems or one the ISP's is having problems so will your network between the locations.
I work with a company that uses roughly 13 different VPN tunnels, but they transfer Point of Sales information (low traffic) in short periods of time and occasional Exhange email.
Let me put it simple, they have problems. Much, much more than a computer network using t1's.

On the subject of speed; DSL upload's can be restricted to 300/400k. So two DSL links will talk at 300/400K depending on Internet/ISP traffic, opposed to a Factional T (512K consistent).

Use the DSL analogy for the T1 internet example as well, but the speed will be 512/frac or 1.5/full

Collapse -

T1 Internet

by gli In reply to Connections

We basically have two choices. PTP or VPN. Both T1's. So far, seems like PTP is the way to go. PTP is actucally cheaper than T1 Internet VPN. We use the PTP connections for POS and voice.

thanks johnnywatt

Collapse -

Not Apples to Apples

by JDSAL In reply to Connections

Not a fair comparison there. Point to Point should outperform VPN if the VPN physical circuit is running same bandwidth. VPN circuit can experience a great deal of latency spikes based on what's happening in the inet cloud. Point to Point circuits contains only your network traffic, but keep in mind that a point to point T1 is usually aggregated somewhere in your carriers network over T3 or OC3 circuits. If you have a large group of private line T1s through the same carrier you have yourself a single point of failure. However telcoms usually re-route down T3 traffic very quickly so you shouldn't have long outages.

If I had to do I would tap into MPLS VPNs. These services are better suited for voip traffic than the aforementioned. MPLS is of course a relatively new offering and can be expensive.

Thats my 2 cents.

Collapse -


by chailey In reply to T1 VPN vs T1 Point to Poi ...

We are currently using three solutions for connectivity of our remote sites to the main data center: PTP (T-1), DSL Megahost using ATM, Lan-to-Lan (Gateway to Gateway) VPN Ipsec tunnels using DSL modems. The Lan to Lan VPN tunnels appear to guarantee the most benefit using 2 DSL modems at the remote locations aggregated into a Linksys Cable Dsl Vpn Router and a 2811 Cisco Router with the firewall security set. The upload speeds of 1 mb and downloads of almost 14 mb/s serves a vital purpose. Most of the information the remote locations retrieve is from our As400 servers and 45 Windows/Linux servers. This solution has proved to be the most cost effective and allows for scalability. The reliability factor is based on your carrier for DSL (like Qwest for example) and what ISP you are pointing the DSL to for the IPSEC tunnel.

Related Discussions

Related Forums