slow communication with server from long distance

I have a dedicated windows 2003 server at godaddy located in arizona.
the server is connected through a bandwidth connection speed of 5-15 Mbps
when i do a speed test On the server (using remote host) , i get results of 5-15 Mbps

when i access the server from my area (israel ,middle east), i download at about 15 Kbps only...
when i do a speed test on my pc, i get 2 Mbps which is my bandwith. (Even if i do a speed test against a server in arizona , where my server is located)

What can be the cause of problem of this speed lag?

amitanteAsked:
Who is Participating?
 
Mordillo98Commented:
I guess you've read my mind while I was doing my post.

Your bottleneck seems to happen as soon you get our of your home with hop #3 to hop #6, which is all related to your ISP.

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2   438 ms    14 ms    71 ms  pt114-89.nas.bezeqint.net [212.25.114.89]
  3   846 ms   844 ms   852 ms  bzq-64-114-9.bezeqint.net [192.114.64.9]
  4     *        *        *     Request timed out.
  5     9 ms    10 ms     9 ms  bzq-219-189-150.cablep.bezeqint.net [62.219.189.
150]
  6     *        *        *     Request timed out.

This is what we have so far.

1.  You did a speed test from your godaddy server and it's fine.
2.  You did a speed test with our home pc to a server in Arizona and it's fine
3.  You do a tracert to your godaddy server from your home PC, and your ISP lags it.

Conclusion:  Call your ISP and let them know they have a defective router.  ISP have multiple routers, and will be pick up a request depending of an IP table they have (not a geographic region).  So even though both you home PC test worked in Arizona, that doesn't mean it should all work in the entire Arizona region.

Be prepared though that they will tell you that you need to increase your bandwidth.  It's a patch of the real problem.  You see, if you lag at a higher speed, then you'll get a fast result.  But it doesn't solve the real problem, and you'll end up paying more.

Good luck.
0
 
amitanteAuthor Commented:
more info:

ping to server from my pc is 220 ms ttl=114

Tracing route to ip-208-109- xxx - xxx
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2   438 ms    14 ms    71 ms  pt114-89.nas.bezeqint.net [212.25.114.89]
  3   846 ms   844 ms   852 ms  bzq-64-114-9.bezeqint.net [192.114.64.9]
  4     *        *        *     Request timed out.
  5     9 ms    10 ms     9 ms  bzq-219-189-150.cablep.bezeqint.net [62.219.189.
150]
  6     *        *        *     Request timed out.
  7    79 ms    81 ms    80 ms  xe-0-2-0.lon21.ip4.tinet.net [77.67.72.241]
  8    82 ms    83 ms    81 ms  xe-11-0-0.lon10.ip4.tinet.net [89.149.187.101]
  9    82 ms    81 ms    87 ms  213.200.77.234
 10   226 ms   225 ms   226 ms  64.210.13.110
 11   228 ms   223 ms   223 ms  ip-97-74-252-126.ip.secureserver.net [97.74.252.
126]
 12   223 ms   226 ms   224 ms  ip-216-69-188-81.ip.secureserver.net [216.69.188
.81]
 13   221 ms   221 ms   222 ms  ip-208-109-112-6.ip.secureserver.net [208.109.11
2.6]
 14   223 ms   225 ms   234 ms  ip-208-109-xxx-xxx.ip.secureserver.net

Trace complete.
0
 
Mordillo98Commented:
Greetings.  This is what needs to be done first.

Do a command prompt on YOUR machine, and do a command called tracert.

The command should look like this:

tracert www.google.ca
or
tracert 66.249.90.104

... but instead of google.ca, put the public IP address of your server at godaddy

then post the results here.

DO NOT SHOW THE IP ADDRESS OF YOUR GODADDY SERVER IN THE POST.  ;)

You could hide the last 2 digits of your goddy ip.  as an exemple.

**************************************************
Tracing route to www.l.google.com [66.XX.XX.XX]
over a maximum of 30 hops:

  1     1 ms    <1 ms    <1 ms  192.168.1.1
  2     8 ms     7 ms    16 ms  10.240.224.1
  3    10 ms     8 ms     7 ms  69.63.254.77
  4    12 ms    11 ms    15 ms  69.63.249.193
  5    12 ms    10 ms     9 ms  69.63.250.93
  6    14 ms    10 ms     9 ms  72.14.216.14
  7    11 ms    13 ms    10 ms  216.239.47.114
  8    25 ms   104 ms    25 ms  72.14.233.112
  9    75 ms    24 ms    33 ms  209.85.241.222
 10    28 ms    27 ms    28 ms  lga15s04-in-f104.1e100.net [66.XX.XX.XX]

Trace complete.

***********************************************

That will help to know where the bottle neck is.
0
Cloud Class® Course: MCSA MCSE Windows Server 2012

This course teaches how to install and configure Windows Server 2012 R2.  It is the first step on your path to becoming a Microsoft Certified Solutions Expert (MCSE).

 
amitanteAuthor Commented:
i posted the tracert above :-) just when you posted the comment Mordillo98

from looking at the tracert few things look bad:

844msec at my isp bezeqint
and 200+200+200+..   at the godaddy server "secureserver"

if i tracert to google (as a gold standard), i get a similar result except the 844msec is not shown but maybe that's the * below:

C:\Users\Administrator>tracert google.com

Tracing route to google.com [72.14.221.104]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2    28 ms    59 ms    19 ms  pt114-89.nas.bezeqint.net [212.25.114.89]
  3     *        *        *     Request timed out.
  4     *        *        *     Request timed out.
  5    10 ms    11 ms    17 ms  bzq-219-189-162.cablep.bezeqint.net [62.219
162]
  6     *        *        *     Request timed out.
  7   264 ms   265 ms   272 ms  72.14.216.225
  8   258 ms   261 ms   268 ms  209.85.255.172
  9   289 ms   299 ms   260 ms  72.14.232.165
 10    75 ms    71 ms    71 ms  72.14.232.190
 11    79 ms    69 ms    71 ms  fg-in-f104.1e100.net [72.14.221.104]

Trace complete.
0
 
amitanteAuthor Commented:
i can live with 1.5 second delay in response (except for remote desktop)

but not with low bandwidth.
in the tracert , i can't see which point is the bottleneck of the bandwidth.
0
 
Mordillo98Commented:
Your google tracert looks like mine, except that you have those *** Request Timed Out *** issue that you shouldn't have.

Now I really believe that your ISP has a defective router.  When you look at mine, it looks really clean.  They need to be notified of it.  You could show them my tracert and yours so they can compare.

Good luck.
0
 
Mordillo98Commented:
The 1.5 sec delay is only for a ping.  That's the lowest of lowest.  Under a tcp/ip communication, there's more than one request during transmission of data.  So multiply 1.5 sec by X requests of communication, you have your lag right there.

With my experience, anything higher than 300 ms, your starting to have issue.  Plus, timeouts are NOT supposed to be there.

What do you to lose anyway by calling them?  You could just give them a call and tell them this, and if you want, try other troubleshooting on your own for other stuff.

If I would be in your position, I would call my ISP.   I don't see anything in your power to fix this since you don't have access to their routers.
0
 
Mordillo98Commented:
... And you are correct.  You can't see bandwidth issue on the tracert, and I don't think that's the issue either.  But ISP sometimes don't want to solve their own issues and will tell you to increase your bandwidth to resolve lagging.  It doesn't solve it, but masks it.  I guess I'm trying to say that don't be surprised if they tell you this....  but don't accept that answer.  ;)  
0
 
amitanteAuthor Commented:
i talked with the ISP
they say that the timeouts are because of firewalls they have there. which makes sense.
they will check it tommorow

thanks


0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.