• Welcome to Overclockers Forums! Join us to reply in threads, receive reduced ads, and to customize your site experience!

FTP transfers slow only between one server?

Overclockers is supported by our readers. When you click a link to make a purchase, we may earn a commission. Learn More.

Soichiro

Member
Joined
Sep 24, 2005
Location
Indianapolis
I have a server that I use for various tasks and frequently download large files from it via FTP. Normally I get 1 MiB/sec+ speeds from this server, but tonight I have been getting less than 100 KiB/sec. I can still get full speeds from other servers, and my server can still upload to other locations at full speeds. I recently moved and therefore am on different internet (although I can get 6 MiB/sec from other locations) and this is my first time using this FTP on this connection, so I wonder if that may be related. As a note, if I run 4 concurrent transfers, each transfer still runs at around 100 KiB/sec.
 
Do you own the other server that your connecting to via FTP or know its down/up speeds? It probably just has a 1mbit upload speed I assume. My old connection was 5/1 until now where it is 30/5. Maybe their ISP is throttling their speeds due to a bandwidth or type of connection?
 
It could be simply be bad routing between your current ISP and your server. Try downloading from the server with a different service such as http and see if you get the same poor speed. Also run traceroute to the server to see if the routes are long and congested.
 
It could be simply be bad routing between your current ISP and your server. Try downloading from the server with a different service such as http and see if you get the same poor speed. Also run traceroute to the server to see if the routes are long and congested.

I reread the OP and I guess I miseed this too. I thought he was still getting full speeds at some other places, just not the one specific server. I would first pause your transfer (if your able to) and try a speed test via speedtest.net and then if that shows you are "low" try a speedtest with your isp (most will have one on their homepage). That can possibly eliminate some error from where it is coming from.
 
Sorry for taking a while to respond, have been very busy lately.

I am still getting good speeds at other places, both on my home connection and on my server connection, and speedtest.net has confirmed this. It's just between my home computer and my server that it's slow. It seems to alleviate late at night, but most of the time I end up with 100-200 kb/sec per connection. Btw, it is a 100/100mbps dedicated server, and my home connection has 50mbps down. This problem started occuring after I moved, I didn't have this problem at my previous residence, but I still can download at 6+ MB/sec from other locations at this new address.

Here is a log of my tracert:

Code:
Tracing route to railgun.no-ip.org [69.64.46.90]
over a maximum of 30 hops:

  1     1 ms    <1 ms    <1 ms  10.0.0.1
  2    35 ms    26 ms    28 ms  68.58.140.1
  3     9 ms     9 ms     9 ms  te-0-0-0-4-sur01.northwest.in.indiana.comcast.net [68.87.209.217]
  4    17 ms    13 ms    14 ms  te-1-0-0-5-ar01.indianapolis.in.indiana.comcast.net [68.87.231.73]
  5    18 ms    16 ms    30 ms  pos-1-14-0-0-ar01.area4.il.chicago.comcast.net [68.87.231.17]
  6    18 ms    18 ms    19 ms  he-3-7-0-0-cr01.350ecermak.il.ibone.comcast.net [68.86.90.53]
  7    16 ms    16 ms    15 ms  he-0-11-0-1-pe04.350ecermak.il.ibone.comcast.net [68.86.83.62]
  8    58 ms    57 ms    56 ms  23.30.206.134
  9    75 ms    57 ms    58 ms  be2004.mpd22.ord01.atlas.cogentco.com [154.54.5.9]
 10   194 ms   207 ms   214 ms  te7-2.ccr01.stl03.atlas.cogentco.com [154.54.2.217]
 11    64 ms    64 ms    65 ms  te7-1.ccr01.stl04.atlas.cogentco.com [154.54.88.122]
 12    64 ms    65 ms    61 ms  38.88.130.6
 13    65 ms    60 ms    63 ms  static-ip-209-239-125-3.inaddr.ip-pool.com [209.239.125.3]
 14    64 ms    63 ms    63 ms  dragon141.startdedicated.com [69.64.46.90]

Trace complete.

As a note, I am in Indianapolis and the server is in St. Louis. I'm not actually sure if this is a "good" traceroute, although some of the ping times seems pretty high. Though when I ping the server directly I get this:

Code:
Pinging railgun.no-ip.org [69.64.46.90] with 32 bytes of data:
Reply from 69.64.46.90: bytes=32 time=64ms TTL=51
Reply from 69.64.46.90: bytes=32 time=63ms TTL=51
Reply from 69.64.46.90: bytes=32 time=62ms TTL=51
Reply from 69.64.46.90: bytes=32 time=61ms TTL=51
 
Last edited:
Back