Jump to content
Sign in to follow this  
luckyluca

downloads freeze with subscription

Recommended Posts

Hello,

 

I signed up for a month of subscription in order to support the site and download a few sf2 packages, however most of the big downloads freeze at around 5-20%. I'm trying both firefox and iexplorer with no luck.

 

For example the file Desrt3_optimized_tiles.7z hangs at 20%

Desert3_V1.2.rar at 5%

 

Any idea why this might be happening?

 

THanks

Luca

Share this post


Link to post
Share on other sites

Hello,

 

I signed up for a month of subscription in order to support the site and download a few sf2 packages, however most of the big downloads freeze at around 5-20%. I'm trying both firefox and iexplorer with no luck.

 

For example the file Desrt3_optimized_tiles.7z hangs at 20%

Desert3_V1.2.rar at 5%

 

Any idea why this might be happening?

 

THanks

Luca

 

Hi -

 

I checked the files you mentioned and they are fine. Subscriptions don't change the actual download process. Once you're at the point where the file transfer has initiated it's a matter of connectivity between the server and your local machine. Since you mentioned that you're getting some of the file then you are getting past the point the subscription could be an issue. Can you run a tracert and ping to our domain and post the results?

 

From a command prompt type the following:

 

tracert combatace.com + [Enter]

 

ping combatace.com -n 30 + [Enter]

 

I suspect that your connection is dropping or something on your local end is shutting down the open file request like security software.

 

Let me know.

 

Erik

Share this post


Link to post
Share on other sites

Thanks for looking into this!

interesting that it only happens with a few files..

I'm on virgin cable and wondering if they have some proxy/download accelerators their end....hmmm

 

 

 

C:\Users\conte>tracert combatace.com

 

Tracing route to combatace.com [216.104.36.210]

over a maximum of 30 hops:

 

1 1 ms 1 ms 1 ms 192.168.1.1

2 8 ms 17 ms 10 ms 10.68.224.1

3 31 ms 29 ms 21 ms camd-geam-1a-ge129.network.virginmedia.net [81.97.255.1]

4 145 ms 211 ms 204 ms hari-core-1a-tenge71.network.virginmedia.net [62.30.250.33]

5 21 ms 9 ms 9 ms brnt-bb-1a-ae1-0.network.virginmedia.net [195.182.178.165]

6 10 ms 8 ms 13 ms brnt-bb-1b-ae0-0.network.virginmedia.net [213.105.174.226]

7 9 ms 9 ms 10 ms popl-bb-1a-as7-0.network.virginmedia.net [62.255.81.237]

8 21 ms 66 ms 9 ms popl-tmr-1-ae4-0.network.virginmedia.net [213.105.159.2]

9 20 ms 18 ms 34 ms amst-ic-1-as0-0.network.virginmedia.net [213.105.175.6]

10 17 ms 27 ms 49 ms ams-ix.ae1.cr1.ams2.nl.nlayer.net [195.69.145.219]

11 27 ms 17 ms 17 ms ae3-40g.cr1.ams2.nl.nlayer.net [69.22.139.238]

12 24 ms 24 ms 22 ms xe-2-0-0.cr1.lhr1.uk.nlayer.net [69.22.142.94]

13 95 ms 94 ms 120 ms xe-2-2-0.cr1.nyc3.us.nlayer.net [69.22.142.9]

14 98 ms 101 ms 96 ms ae2-70g.cr1.ewr1.us.nlayer.net [69.31.95.145]

15 126 ms 168 ms 107 ms xe-3-0-0.cr1.ord1.us.nlayer.net [69.22.142.74]

16 108 ms 135 ms 110 ms ae1-30g.ar1.ord1.us.nlayer.net [69.31.111.134]

17 166 ms 225 ms 251 ms as32475.xe-3-0-2-1101.ar1.ord1.us.nlayer.net [69.31.111.94]

18 108 ms 109 ms 138 ms asw-c11.r03.ord02.singlehop.net [65.60.6.66]

19 108 ms 108 ms 107 ms trinity.combatace.com [216.104.36.210]

 

Trace complete.

 

C:\Users\conte>ping combatace.com -n 30

 

Pinging combatace.com [216.104.36.210] with 32 bytes of data:

Reply from 216.104.36.210: bytes=32 time=109ms TTL=51

Reply from 216.104.36.210: bytes=32 time=120ms TTL=51

Reply from 216.104.36.210: bytes=32 time=107ms TTL=51

Reply from 216.104.36.210: bytes=32 time=108ms TTL=51

Reply from 216.104.36.210: bytes=32 time=107ms TTL=51

Reply from 216.104.36.210: bytes=32 time=110ms TTL=51

Reply from 216.104.36.210: bytes=32 time=107ms TTL=51

Reply from 216.104.36.210: bytes=32 time=117ms TTL=51

Reply from 216.104.36.210: bytes=32 time=108ms TTL=51

Reply from 216.104.36.210: bytes=32 time=108ms TTL=51

Reply from 216.104.36.210: bytes=32 time=108ms TTL=51

Reply from 216.104.36.210: bytes=32 time=107ms TTL=51

Reply from 216.104.36.210: bytes=32 time=107ms TTL=51

Reply from 216.104.36.210: bytes=32 time=106ms TTL=51

Reply from 216.104.36.210: bytes=32 time=108ms TTL=51

Reply from 216.104.36.210: bytes=32 time=108ms TTL=51

Reply from 216.104.36.210: bytes=32 time=109ms TTL=51

Reply from 216.104.36.210: bytes=32 time=111ms TTL=51

Reply from 216.104.36.210: bytes=32 time=107ms TTL=51

Reply from 216.104.36.210: bytes=32 time=131ms TTL=51

Reply from 216.104.36.210: bytes=32 time=107ms TTL=51

Reply from 216.104.36.210: bytes=32 time=106ms TTL=51

Reply from 216.104.36.210: bytes=32 time=107ms TTL=51

Reply from 216.104.36.210: bytes=32 time=118ms TTL=51

Reply from 216.104.36.210: bytes=32 time=109ms TTL=51

Reply from 216.104.36.210: bytes=32 time=108ms TTL=51

Reply from 216.104.36.210: bytes=32 time=129ms TTL=51

Reply from 216.104.36.210: bytes=32 time=124ms TTL=51

Reply from 216.104.36.210: bytes=32 time=108ms TTL=51

Reply from 216.104.36.210: bytes=32 time=109ms TTL=51

 

Ping statistics for 216.104.36.210:

Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 106ms, Maximum = 131ms, Average = 110ms

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Hi -

 

I checked the files you mentioned and they are fine. Subscriptions don't change the actual download process. Once you're at the point where the file transfer has initiated it's a matter of connectivity between the server and your local machine. Since you mentioned that you're getting some of the file then you are getting past the point the subscription could be an issue. Can you run a tracert and ping to our domain and post the results?

 

From a command prompt type the following:

 

tracert combatace.com + [Enter]

 

ping combatace.com -n 30 + [Enter]

 

I suspect that your connection is dropping or something on your local end is shutting down the open file request like security software.

 

Let me know.

 

Erik

Share this post


Link to post
Share on other sites

Those numbers aren't bad considering you're jumping the pond.

 

My return routing looks like this:

 

1 . (216.104.36.209) 1.413 ms 1.829 ms 2.066 ms

2 dr6506a.ord02.singlehop.net (65.60.6.65) 1.313 ms 1.297 ms 1.299 ms

3 xe-3-0-2-1101.ar1.ord1.us.nlayer.net (69.31.111.93) 1.502 ms 1.493 ms 1.480 ms

4 ae1-30g.cr1.ord1.us.nlayer.net (69.31.111.133) 1.207 ms 25.428 ms 25.424 ms

5 xe-3-0-0.cr2.iad1.us.nlayer.net (69.22.142.26) 18.156 ms xe-4-2-0.cr1.ewr1.us.nlayer.net (69.22.142.42) 19.640 ms xe-3-0-0.cr2.iad1.us.nlayer.net (69.22.142.26) 18.138 ms

6 eqix-ix-1.ntli.net (206.223.115.174) 113.808 ms ae2-50g.cr1.nyc2.us.nlayer.net (69.31.95.174) 20.141 ms eqix-ix-1.ntli.net (206.223.115.174) 113.128 ms

7 popl-bb-1b-as0-0.network.virginmedia.net (62.253.184.5) 114.086 ms 113.325 ms 114.062 ms

8 popl-bb-1b-ae5-0.network.virginmedia.net (213.105.159.5) 170.019 ms 170.000 ms 169.977 ms

9 popl-bb-1b-as0-0.network.virginmedia.net (62.253.184.5) 115.741 ms hari-core-1b-pc200.network.virginmedia.net (195.182.178.170) 116.225 ms 117.455 ms

10 hari-core-1a-v11.network.virginmedia.net (62.30.144.38) 116.691 ms 116.923 ms 119.129 ms

11 hari-core-1b-pc200.network.virginmedia.net (195.182.178.170) 121.379 ms camd-geam-1a-tenge71.network.virginmedia.net (62.30.250.34) 116.402 ms 114.404 ms

12 camd-cmts-13-ge130.network.virginmedia.net (81.97.255.2) 116.912 ms 117.823 ms 117.793 ms

13 * * *

14 * * *

15 * * *

 

As you can see the return inbound to your machine reaches what looks like your ISP's headend just fine. The machine at your step 2 and my step 13 is not responding to inbound ICMP traffic which is pretty normal for security reasons. The only thing I can suggest that might help diagnose the problem is to disconnect from your home network and go straight to your modem then check downloading again. This will just take your router at home out of the equation. If your router and modem are one and the same try resetting it. Past that the only other thing I can suggest is try a different machine and check your firewall settings.

 

Let me know how or if I can help further.

 

Erik

Share this post


Link to post
Share on other sites

thanks for taking a look, it works now (it hadn't for almost two days) I wonder if this has to do with poor over-the-weekend virgin cable support..

anyway thanks again

Luca

 

 

Those numbers aren't bad considering you're jumping the pond.

 

My return routing looks like this:

 

1 . (216.104.36.209) 1.413 ms 1.829 ms 2.066 ms

2 dr6506a.ord02.singlehop.net (65.60.6.65) 1.313 ms 1.297 ms 1.299 ms

3 xe-3-0-2-1101.ar1.ord1.us.nlayer.net (69.31.111.93) 1.502 ms 1.493 ms 1.480 ms

4 ae1-30g.cr1.ord1.us.nlayer.net (69.31.111.133) 1.207 ms 25.428 ms 25.424 ms

5 xe-3-0-0.cr2.iad1.us.nlayer.net (69.22.142.26) 18.156 ms xe-4-2-0.cr1.ewr1.us.nlayer.net (69.22.142.42) 19.640 ms xe-3-0-0.cr2.iad1.us.nlayer.net (69.22.142.26) 18.138 ms

6 eqix-ix-1.ntli.net (206.223.115.174) 113.808 ms ae2-50g.cr1.nyc2.us.nlayer.net (69.31.95.174) 20.141 ms eqix-ix-1.ntli.net (206.223.115.174) 113.128 ms

7 popl-bb-1b-as0-0.network.virginmedia.net (62.253.184.5) 114.086 ms 113.325 ms 114.062 ms

8 popl-bb-1b-ae5-0.network.virginmedia.net (213.105.159.5) 170.019 ms 170.000 ms 169.977 ms

9 popl-bb-1b-as0-0.network.virginmedia.net (62.253.184.5) 115.741 ms hari-core-1b-pc200.network.virginmedia.net (195.182.178.170) 116.225 ms 117.455 ms

10 hari-core-1a-v11.network.virginmedia.net (62.30.144.38) 116.691 ms 116.923 ms 119.129 ms

11 hari-core-1b-pc200.network.virginmedia.net (195.182.178.170) 121.379 ms camd-geam-1a-tenge71.network.virginmedia.net (62.30.250.34) 116.402 ms 114.404 ms

12 camd-cmts-13-ge130.network.virginmedia.net (81.97.255.2) 116.912 ms 117.823 ms 117.793 ms

13 * * *

14 * * *

15 * * *

 

As you can see the return inbound to your machine reaches what looks like your ISP's headend just fine. The machine at your step 2 and my step 13 is not responding to inbound ICMP traffic which is pretty normal for security reasons. The only thing I can suggest that might help diagnose the problem is to disconnect from your home network and go straight to your modem then check downloading again. This will just take your router at home out of the equation. If your router and modem are one and the same try resetting it. Past that the only other thing I can suggest is try a different machine and check your firewall settings.

 

Let me know how or if I can help further.

 

Erik

Share this post


Link to post
Share on other sites

My best guess is that a router was having a problem and it's since been fixed. If you look at our connection and consider the distance the fact that we originate, carry, and destinate on just 2 carriers is pretty great. Virgin can't be too bad given that. I've seen carriers who bucket buy bandwidth and will dump connections four times to another carrier before hitting a centralized hub. It's one reason I was really happy with our DC when they decided to carry on nLayer. Our connectivity has performed very well for us and I can't say enough good things about nLayer for the way they route in and out of our DC. Glad all is resolved, thank you for updating me.

 

Erik

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

×

Important Information

By using this site, you agree to our Terms of Use, Privacy Policy, and We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue..