Text 1881, 65 rader
Skriven 2011-09-05 23:18:23 av Dave Yeo
Ärende: Re: eCS 2.1 and logging into Verizon DSL account
========================================================
Firefox/9.0a1 SeaMonkey/2.6a1
From: Dave Yeo <dave.r.yeo@gmail.com>

John Small wrote:
>>> I can do pertty much anything with my browsers... except to log into
>>> >  >  my Verizon account!?
>>> >  >
>> >
>> >  And how does logging in fail?
> There are two stages of failure:
> 1) With a fresh install (i.e. new profile, no cookies, no add-ons,
> etc.) the login page appears to load fully. But after I enter my
> userid and password, the browser looks busy (the IP monitor shows some
> traffic (not a lot), the CPU monitors are busy, the browser displays
> "busy" messages ("Connnecting to...", "Waiting for...") and the
> throbber is active. After a long while the URL changes in the location
> bar and the display goes blank. And there it stops!??

I just tested this, after the login page loaded I noticed it was just 
using HTTP so I added a S to make it HTTPS in the address field. Tried 
logging in with a bogus name and very quickly that part of the page 
became blank, no second try.
The page also says I need Flash 10 which I don't have, do you? I believe 
our Flash is missing some scripting capabilities which could be a 
problem but the page would have to be very badly designed and I did get 
the login field.
Reloading the page works fine.

> 2) After a failure like the one above, I cannot even get the login
> page to display fully. The userid and password fields are never
> displayed for me to log in.
>
> If I clear the history and cookies, I can return to stage 1 failures.
> So whatever causes the stage 1 failures seems to leave the cookies in
> a "corrupt" state that prevents successful loading of the login page
> until they are cleared.
>
[...]
> 4) Disabling Hyperthreading. (Is "Hyperthreading" an Intel term? I
> have an AMD system and could not find "Hyperthreading" in the BIOS. I
> found what I thought might be a synonym and set it to "1x". So I don't
> know if I did anything possibly constructive.)

HyperThreading is an Intel thing where part of the processor is 
duplicated and acts as a virtual second CPU. Helps performance sometime, 
sometimes not and ideally the operating system should support it.
You may have tested with only one CPU active, worth trying but if it 
didn't make a difference you might as well put it back to how it was.

> FWIW:
> 1) The URL for the login page iswww.myverizon.com  (which redircts to
> www22.verizon.com).

Sometimes I get similar results on pages which often turns out to be bad 
routing or a slow router. Since you're on Verizon you'd think the 
routing would be fine but you could try doing a tracerte 
www222.verizon.com. This will show you each hop, if it gets delayed 
you'll get *** and it'll need a ctrl-C to exit.
Here it actually resolves to e3.g.akamaiedge.net which is kind of a huge 
cache site used by busy sites. From the west coast of Canada it seems to 
have timed out in Seattle.
Dave

--- Internet Rex 2.31
 * Origin: Aioe.org NNTP Server (1:261/20.999)