Jump to content

Orf

NEW MEMBER
  • Content count

    5
  • Joined

  • Last visited

Everything posted by Orf

  1. I have been trying to get the Convair Model 201 Shipboard Fighter 1.0 from http://combatace.com/files/file/13080-convair-model-201-shipboard-fighter/. I ensure I am logged in. I am using Chrome v19.0.1084.56 m I have tried both the file download at: http://combatace.com/files/download/13080-convair-model-201-shipboard-fighter/ and the download mirror at: http://combatace.com/files/download/13080-convair-model-201-shipboard-fighter/page__mirror__1 Chrome starts the download and gets to 0.5/58.3MB and shows interrupted I have tried the same download with Firefox v12.0 with similar results Firefox throws an error saying the source file could not be read I have validated my connection to your server and latency times. My ping time to your server (resolved to 216.104.36.210) shows: **************************** C:\>ping combatace.com Pinging combatace.com [216.104.36.210] with 32 bytes of data: Reply from 216.104.36.210: bytes=32 time=63ms TTL=46 Reply from 216.104.36.210: bytes=32 time=61ms TTL=46 Reply from 216.104.36.210: bytes=32 time=61ms TTL=46 Reply from 216.104.36.210: bytes=32 time=62ms TTL=46 Ping statistics for 216.104.36.210: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 61ms, Maximum = 63ms, Average = 61ms ************************ A tracert to your server shows 20 hops: ************************ C:\>tracert 216.104.36.210 Tracing route to trinity.combatace.com [216.104.36.210] over a maximum of 30 hops: 1 1 ms 1 ms <1 ms home [192.168.1.254] 2 12 ms 11 ms 13 ms adsl-72-152-87-1.asm.bellsouth.net [72.152.87.1] 3 13 ms 14 ms 15 ms 70.159.176.143 4 14 ms 15 ms 13 ms 70.159.176.149 5 11 ms 15 ms 15 ms 70.159.176.38 6 13 ms 15 ms 15 ms 12.81.16.90 7 14 ms 13 ms 11 ms 12.81.16.15 8 14 ms 15 ms 15 ms 74.175.192.86 9 20 ms 20 ms 21 ms cr1.attga.ip.att.net [12.122.141.186] 10 14 ms 13 ms 15 ms attga02jt.ip.att.net [12.123.22.25] 11 38 ms 15 ms 15 ms 192.205.35.234 12 13 ms 39 ms 15 ms xe-1-0-0.mpr3.atl6.us.above.net [64.125.31.45] 13 28 ms 29 ms 31 ms xe-2-1-0.cr2.iah1.us.above.net [64.125.31.50] 14 29 ms 31 ms 29 ms xe-0-0-0.cr1.iah1.us.above.net [64.125.30.65] 15 33 ms 34 ms 48 ms xe-2-1-0.cr1.dfw2.us.above.net [64.125.30.58] 16 61 ms 62 ms 62 ms xe-2-0-0.cr1.ord2.us.above.net [64.125.25.133] 17 61 ms 62 ms 62 ms xe-1-1-0.er1.ord2.us.above.net [64.125.26.186] 18 62 ms 62 ms 62 ms 64.124.200.138.allocated.above.net [64.124.200.138] 19 62 ms 62 ms 62 ms asw-c11.r03.ord02.singlehop.net [65.60.6.66] 20 61 ms 62 ms 62 ms trinity.combatace.com [216.104.36.210] Trace complete. ********************** This is not the first time I have had this issue with files from your site. In the past I have kept trying, and eventually I will be able to get the files. I have seen others mention this issue and I know your response is typically to try another browser, but I have done so with no change in outcome. If you would like any more information, please ask I thoroughly enjoy your site and don't want this post to be taken as a complaint. I just wanted to let you know it is not a browser issue. Please don't say flush your cache/cookies/history or toilet. I have tried all of those (as appropriate of course) with no change. I would seriously consider going to a paid membership, but I fear the frustration would out weigh the benefit.
  2. As requested: ***************************** C:\>ping files.combatace.com Pinging files.combatace.com [66.208.223.141] with 32 bytes of data: Reply from 66.208.223.141: bytes=32 time=89ms TTL=47 Reply from 66.208.223.141: bytes=32 time=91ms TTL=47 Reply from 66.208.223.141: bytes=32 time=86ms TTL=47 Reply from 66.208.223.141: bytes=32 time=84ms TTL=47 Ping statistics for 66.208.223.141: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 84ms, Maximum = 91ms, Average = 87ms C:\>tracert 66.208.223.141 Tracing route to 66-208-223-141-Pima.hfc.comcastbusiness.net [66.208.223.141] over a maximum of 30 hops: 1 1 ms 1 ms <1 ms home [192.168.1.254] 2 12 ms 13 ms 13 ms adsl-72-152-57-1.asm.bellsouth.net [72.152.57.1] 3 13 ms 14 ms 15 ms 70.159.176.143 4 13 ms 15 ms 15 ms 70.159.176.149 5 14 ms 14 ms 20 ms 70.159.176.216 6 15 ms 15 ms 15 ms 12.81.16.98 7 13 ms 13 ms 13 ms 12.81.16.7 8 15 ms 15 ms 15 ms 74.175.192.62 9 17 ms 21 ms 19 ms cr1.attga.ip.att.net [12.122.141.186] 10 17 ms 15 ms 15 ms gar24.attga.ip.att.net [12.122.141.181] 11 20 ms 25 ms 23 ms be-200-pe01.56marietta.ga.ibone.comcast.net [75.149.228.85] 12 17 ms 17 ms 19 ms 68.86.88.177 13 37 ms 74 ms 36 ms pos-1-10-0-0-cr01.dallas.tx.ibone.comcast.net [68.86.86.129] 14 70 ms 68 ms 66 ms pos-0-9-0-0-cr01.losangeles.ca.ibone.comcast.net [68.86.87.253] 15 81 ms 114 ms 78 ms te-7-2-ar02.pimaco.az.pima.comcast.net [68.86.91 16 83 ms 78 ms 78 ms pos-2-2-ar01.pimaco.az.pima.comcast.net [68.87.172.30] 17 77 ms 76 ms 76 ms te-3-0-0-ten01.pimaco.az.pima.comcast.net [69.139.177.158] 18 88 ms 86 ms 84 ms 66-208-223-141-Pima.hfc.comcastbusiness.net [66.208.223.141] Trace complete. *************************** The Comcast hops were a little slow. As I mentioned, I'm not really complaining. I have the patience and realize that eventually the internet gods will let me get the file (Even if I do get mad when failed downloads count against the 24 hour download limit - lol). I have just seen a few different folks mention the issue and thought I could give some data to take a look at.
  3. It's not a firewall issue. I got the files fine earlier today with no changes. Not sure what you mean by "Windows web browser". Are you referring to Internet Explorer? If you are I may just have to live with the issue. Nope. Hardwired.
  4. As a side note, I was able to get the file this morning. Not sure what the issue may be.
  5. Nice vid. Here's hoping you get the chance to do the radar guided version.
×

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..