RnTNuGseeFGCE/dp1daMi0PClNMc!pNvB0xzJe7TpAoqI+nztKtnfi+QZEBazaxm   
   vRTO9gDlSMah54K8Eg0aP5HHJtzPy7gLXtKDTtrH!AmmBKk42SMlGQBhtUASVEYI=   
   properly   
   From: "John Small"    
      
   On Thu, 1 Sep 2011 00:03:42 UTC, Dave Yeo     
   wrote:   
      
   > John Small wrote:   
   > > On Thu, 25 Aug 2011 14:28:12 UTC, Shmuel (Seymour J.) Metz   
   > >   wrote:   
   > >   
   > >> In<4rkzjBzzMnpe-pn2-dnlyRwUn87WW@A8N.westell.com>, on 08/25/2011   
   > >>     at 08:16 AM, "John Small"  said:   
   > >>   
   > >>> I recently enrolled in Verizon DSL. And I cannot login into my   
   > >>> Verizon account using the DSL connection using a variety of versions   
   > >>> of  Firefox and Seamonkey under eCS 2.1.   
   > >>   
   > >> Are you sure that you have a connection? Did you try to ping anything?   
   > >> How are you configured?   
   > >   
   > > 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!??   
   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.   
      
   > If it is session timing out issues see    
   > https://bugzilla.mozilla.org/show_bug.cgi?id=648360   
      
   I never get any messages regarding timeout errors. Nevertheless I went   
   ahead and tried everything I found while reading the page you    
   reference (and the relevant links). I have tried:   
   1) Trying the 20110731 version of Firefox (in addition to several    
   others, including the "official" v6.0)   
   2) Allowing session-only cookies for that website   
   3) Setting NSPR_OS2_NO_HIRES_TIMER=1   
   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.)   
      
   FWIW:   
   1) The URL for the login page is www.myverizon.com (which redircts to    
   www22.verizon.com).   
   2) The error console shows many warning messages regarding various    
   Verizon script errors.   
   3) The error console shows informational messages regarding "...    
   server does not support RFC 5746 ..."   
      
      
   --    
      
   John Small   
      
      
   --- Internet Rex 2.31   
    * Origin: The gateway at Omicron Theta (1:261/20.999)