[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 243
  • Last Modified:

network bandwidth access for web server

Where my web server is located (call it location A) the internet (DSL) is not very fast and does not meet the bandwidth requirements. Therefore, I was thinking to have users access the web server through our other location's (call it location B) internet (different state) which is faster. Then it would route through our private WAN 1.5 T1 to get to my web server in location A.  Would this make a difference or is it the same thing since it has to go across the wan.
0
paul_techy
Asked:
paul_techy
  • 3
  • 2
1 Solution
 
giltjrCommented:
What is your DSL speed?  I is it ADSL?  If so, rember ADSL was designed for the client side access, not server side.  This is why the download speeds are faster than the upload speeds.

What is the latency on the T1 between he two sites?

Where are you users located at in relationship to location B?
0
 
paul_techyAuthor Commented:
Its actually uverse. 4-5Mbps down,  0.6-0.7Mbps up

Latency is 0% packet loss using traceroute

Location B = California
other users=California, north-central usa, east coast usa.
0
 
giltjrCommented:
O.K., you have a ADSL connection, which again is not for host services.  Your upload stream speed looks like it is a 768Kbps which is 1/2 of a T1, way to slow for hosting anything.

If you play on keeping your web server at its currently location you may want to look at getting a connection that has more upsteam bandwidth.

Latency is a measure of time, not packet loss.

You should be able to setup a test to see how it affect performance.

You can setup a new NAT at location B to forward to your web server at location A.  Then just use the IP address to get to the server and see what performance is.  

If it is acceptable, then just update the DNS entry to point to the new IP address.
0
 
paul_techyAuthor Commented:
correction:
Location B= north-central usa
Location A= california
other users=California, north-central usa, east coast usa.

Latency= 100ms

So basically, your saying to setup a new NAT at location B to forward to webserver at loation A would be the better solution unless location A gets a better internet speed.
0
 
giltjrCommented:
I am saying set it up and test.  However 100 ms is a long time.
0

Featured Post

VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now