Okay, I'm not sure if this is easy to answer, but how can I accomplish this? I have an ADSL connection, and it takes awhile to log into my FTP account for my website. Tech support said it was my high latency. So, can I tweak anything to decrease this?
Thanks!
Bryan
<font color=red><A HREF="http://www.btvillarin.com" target="_new">btvillarin.com</A> - My Windows XP-based Website</font color=red>
As long as your cabling is fine and there's not exxessive traffic on your network(at home, which i doubt unless your having a lan party with a 100 people) then it's the ISP =).
I guess there's nothing I can do about it, unless SBC Pacific Bell cares. Here's what the Cyberwings tech support replied when I asked about this:
<font color=green>There's not alot we can do about this. This is called latency, and it has to do with the number of router hops you are taking to reach the server. I am getting good response times from the server of around 40ms.</font color=green>
Anymore suggestions would be appreciated, even it's to say that I have to grin and bear it.
Thanks <b>Zlash</b>!
<font color=red><A HREF="http://www.btvillarin.com" target="_new">btvillarin.com</A> - My Windows XP-based Website</font color=red>
The only thing you can do is switch ISPs. Its their slow/congested hardware.
Heres some info i found:
<i>Q: My latency (ping times) are high, even though my transfer rate is good.
A: If your latency is consistently high, you need to question your provider as to your routing. Many ISPs are not national, but are able to sell DSL nationally. In certain cases, they must route traffic all over the place even if you are trying to use local game servers or sites. In other cases, the ISP has real (and hopefully temporary) routing problems, or a critical failure and they are on backup.
Normally network specialists plan for optimal routing, but during fast growth, your ISP may have got into a situation where customers pay penalty in ping time while the ISP figures out how to resolve the problem.
The first step in diagnosis of high latency is to figure out the ping time to your default gateway. You may do this by using the Line Quality tool at this site, or by using Visual Route from Datametrics (<A HREF="http://www.visualroute.com" target="_new">http://www.visualroute.com</A> ).
If your default gateway ping is good, the next step is to get a trace to a server that you believe should be nearby. Ideally, nearby servers are available with a few number of hops and low total latency.</i>
<i>If you have a slow connection speed, It could be a network problem(routers or ATM Cloud). You can go to the MS-DOS prompt and do a "tracert ". The first 3 pings are going to be the routers on your ISP's network. The destinations just after the first 3 pings are going to be the backbone provider's routers. If you have high latency(100+ ms) on the first 3 routers, it could be a bad router or problem with the ATM cloud. If your 4th hop is really bad, then they are having problems with their backbone in that area.</i>
You can get a nice trace program (VisualRoute) and see where you are picking up the lag and report it to your ISP if it's thiers. Maybe even try to get them to report it to whoever if it's not thiers.
Latency can be caused by alot of differnt factors, if you are going through sbc then it could be a ATM problem, or a gateway issue or possibly even a backbone problem in which sbc has no control. Id have sbc run atm traces and pings to rule out there horrible atm network, and see if you can find anything out.
Dude, I can't believe I forgot to check on my post here. It's been like over a week since I've checked this post. So, I'm really sorry.
Anyways, both sides can't do anything about it. But, it's weird because it takes a long time <b>in Windows XP</b>, but logs in quick with <b>Windows 2000</b>. So, there might be a setting problem that I'd have to find and tweak, but I'm not sure where.
As for doing a trace route for all the routers are getting less than 100ms.
Tracing route to btvillarin.com [64.246.28.123]
over a maximum of 30 hops:
1 20 ms 20 ms 20 ms adsl-63-204-179-254.dsl.lsan03.pacbell.net [63.204.179.254]
2 20 ms 20 ms 20 ms dist4-vlan60.lsan03.pbi.net [216.102.181.18]
3 20 ms 20 ms 10 ms edge1-ge1-0.lsan03.pbi.net [206.13.29.144]
4 20 ms 20 ms 20 ms sl-gw28-ana-13-0.sprintlink.net [144.228.75.161]
5 20 ms 20 ms 20 ms sl-bb21-ana-11-0.sprintlink.net [144.232.1.29]
6 40 ms 50 ms 40 ms sl-bb20-fw-10-0.sprintlink.net [144.232.8.97]
7 40 ms 50 ms 40 ms sl-gw20-fw-8-0.sprintlink.net [144.232.11.126]
8 40 ms 51 ms 40 ms sl-savvis-2-0-0.sprintlink.net [144.232.194.14]
9 50 ms 50 ms 50 ms everyoneint-1.s2333b.ushstn2-j20c.savvis.net [64.243.79.14]
10 60 ms 60 ms 60 ms tayhou-223-36.ev1.net [207.218.223.36]
11 60 ms 60 ms 60 ms 64.246.28.123
Trace complete.
</font color=green>
So, it has to be something with Windows XP. BTW, if it matters, I'm using WS_FTP Pro 7.04. Thanks again!
<font color=red><A HREF="http://www.btvillarin.com" target="_new">btvillarin.com</A> - My Windows XP-based Website</font color=red>
Maybe you can try some of these <A HREF="http://www.speedguide.net/Cable_modems/cable_reg_win2k.shtml" target="_new">tweaks</A> or somehow find what those settings are in win2k and compare it to winxp.
Is you ISP also your web space provider? If it is one of those 10mb free with your isp account, they often lower the bandwidth priority to those subwebs. Causing huge latencyeven when your traceroute comes back fine. If you change to a different web service provider or host it yourself, you shouldn't have those problems.
Don't know what else you can do. Maybe try a different ftp program or upgrade your WS_FTP Pro 7.04 to the newest version 7.5. You can also try to login at a friends/relatives computer in the same area who uses an different internet provider.
You are about to answer a thread that has been inactive for more than 6 months. If you still wish to proceed, please ensure that your posting is original and does not duplicate or overlap any prior responses to this thread.