| reply to digitalking
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. |
|
 EGThe wings of lovePremium
join:2006-11-18
Union, NJ
kudos:9 | said by digitalking: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. |
|
 jlivingoodPremium,VIP
join:2007-10-28
Philadelphia, PA
kudos:1 | reply to digitalking
said by digitalking: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.
--
JL
Comcast |
|
|
|
