Online connection turtle-slow

[NoOp]

On 01/31/2009 03:25 PM, NoOp wrote:
> On 01/31/2009 08:13 AM, Jim Kvarnberg wrote:
>> Thank you guys for trying to help me with the slowness problem of 
>> connection with online banking and other websites that requires my login 
>> sign and password.  I still want to stick to using the FireFox Web 
>> browser because before Ubuntu 8.04 (now 8.10), I had no problem.  I 
>> tried some different Linux based web browsers such as SeaMonkey and 
>> Epiphany Web Browser.  Still the same problem.     I assumed that the 
>> updates or security buildup were hard on them trying to get in 
>> connection with my computer.  The statement at the bottom bar, 
>> "Transferring data from www.txn.banking.XXXXX..." been there for a long 
>> time say several minutes or so before it finally came on.  Does this 
>> ring a bell? 
>> 
> 
> Seems that others are having problems with their site as well:
> <http://www.google.com/search?complete=0&hl=en&q=+www.txn.banking>
> 
> [be sure to look at the next few pages as well]
> 
> I'd complain to your bank.
> 
> Then again...
> <http://forum.eeeuser.com/viewtopic.php?pid=457873>
> 
> <quote>
> Well this is your lucky day.   I have the same bank and the same problem.
> 
> Here is the fix:
> 
> sudo gedit /etc/sysctl.conf
> 
> add this to the very bottom of the page:
> 
> # PC Financial Website Fix
> net.ipv4.tcp_window_scaling = 0
> 
> save the file and reboot; problem solved.
> 
> Kryspy
> </quote>
> 
> Interesting...
> 
> The actual command should be:
> 
>  gksu gedit /etc/sysctl.conf
> 
> Note: I've not tried it as I don't want to reboot on this machine for
> awhile. I'll try it on another in a while.
>

OK. I just tested on another machine (Hardy) by first trying to load
<https://www.txn.banking.pcfinancial.ca/a/authentication/preSignOn.ams?referid=loginBox_banking_go>
and it took forever. Did as the above instructions, rebooted, made sure
that I had cleared all cache etc., in Fx 3.0.5 and tried the link again;
result is that it came up almost instantly. So, just to be sure that it
wasn't a cache, I tried the same in SeaMonkey (1.1.14 and 2.0.3aPre);
same instant results.

So, give that a try & see if it works for you. *AND* complain to your
bank as the fix indicates a problem on their side.

Note: had you just given us the URL in the first place you would most
likely have had a solution after your first post on the 24th!