FTP throttling? (No, it is some other issue)

When using FTP applications to download from a server, I only get 5-10KB/s transfers. On the same computer, if I then connect through a secure VPN using PPTP, my speeds jump to 800-900KB/s. I am guessing because the data is encrypted, the FTP data can no longer be identified and is not blocked.

Yes. It is a routing problem confirmed with tracert.I know this is a very stupid question, but is there anyway go through a different route to that FTP server? My VPN has limited bandwidth usage, so VPN is not a permanent solution. Tracert gets stuck at some backbone Comcast IP address in Chicago. I found the IP listed in a forum where others were having the same issue. One guy had a tracert time with that server of 1720ms. This routing problem has been going on for almost 2 weeks now for me.

Re: FTP throttling? (No, it is a routing issue)

It is definitely an ibone.comcast.net server, I do not have the IP at the moment. I can provide that later.When doing a tracert, it pauses at the ibone.comcast.net server for a while, then reports a 76ms time at that server. The other servers in the route are way less. Thanks for the help everyone.

When doing a tracert, it pauses at the ibone.comcast.net server for a while, then reports a 76ms time at that server. The other servers in the route are way less. Thanks for the help everyone.

It could be ICMP de-prioritization at that router hop. Maybe the router was busy passing real traffic so it delayed it's response to the returning of the ping packets. Using ICMP packet based troubleshooting tools on today's internet networks is by no means gospel.

Wouldn't it be simpler to just provide the trace route as in it's entirety then post a arbitrary IP?

My guess is EG is correct and the traceroute data will show ICMP rate limiting (which does not impact traffic). If there was a real problem at an ibone level more than just this one FTP session would be impacted (millions of subs). While I don't have direct facts to support my hypothosis, the lack of postings from many users does.

digitalking if you provide the traceroute we can quickly rule out your incorrect assumtion and get to the real issue which I expect will turn out to be something in your home, in your local node or at the destination server.

It is definitely an ibone.comcast.net server, I do not have the IP at the moment. I can provide that later.When doing a tracert, it pauses at the ibone.comcast.net server for a while, then reports a 76ms time at that server. The other servers in the route are way less. Thanks for the help everyone.

That won't really tell you much at all. You need to post a traceroute with your VPN and without your VPN.--JLComcast

Re: FTP throttling? (No, it is some other issue)

This is not an issue with Comcast at all. Is there a way to have my post deleted, so no rumors start that Comcast is FTP throttling. GBLX.NET is where the lag starts. Everything after the Comcast servers, my lag times are over 100ms.How do I go about getting this lag issue resolved?

I connected to the FTP server on the AT&T network at a friends house, and I am not having any issues. With AT&T, my route never goes through GBLX.NET. Why does AT&T take one route and Comcast another, to the same place and from the same city? Would Comcast be able to resolve this issue?

How do I get the extremely slow connection to the FTP server resolved on the Comcast network? I also tried it without a router being used and a direct connection to the modem. Like I stated, I do not have this issue using a VPN on the Comcast network or on the AT&T network at someone elses home.