Hi, John...
On 06/16/12 09:33 am, John Small thus wrote :
Typical. Their coding is an absolute mess. I suspect that this is what's
causing the trouble, though as we appear to be hitting on the same DNS
results (see below), I'm still not sure why you are getting the symptom
you are and I am not.
<snip>
>> Maybe your DNS provider is having difficulty. You can try using
>> different servers (I tend to rely on the old GTE ones a lot, because the
>> addresses are easy to remember: 4.2.2.1, 2, and 3).
>
> Does my output from dig suggest that I try alternate DNS servers?
>
I don't think so. They are using round robin DNS. This is a way of
distributing the load based upon current demand, available servers, and
(usually; hopefully!) performance tuning. Thus, any one of a number of
servers might be hosting the page. For example, I just ran dig again
(11:33pm EDT), and got:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 35299
;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 13, ADDITIONAL: 0
www22.verizon.com. 300 IN CNAME
www22.verizon.com.edgekey.net.
www22.verizon.com.edgekey.net. 1440 IN CNAME
e3.g.akamaiedge.net.
e3.g.akamaiedge.net. 20 IN A 23.65.224.29
I think we're just getting different servers for the same page, and not
getting redirected to some questionable network for nefarious purposes.
So, we're back to square one (almost) to try to determine what is
causing the difficulty.
You tried a fresh profile. What plugins (not extensions, as I'm assuming
when you tried the fresh profile it had no extensions added) are you
loading? The url "about:support" can reveal a wealth of information,
including non-default config entries. Have a look from your virgin
profile and see what might turn up there.
Reviewing this thread...
Toward the beginning, you determined that in safe mode (disabling
add-ons, including plugins), Facebook login was working again, but
Verizon was not. This led to a bit of a tangential discussion concerning
the Innotek Java plugin. Please post the contents of your plugin
directory, if you would. There may be some dead wood in there.
Next, when you upgraded last, you *did* start with a clean program
directory, and didn't install *over* an existing installation, correct?
To be sure, and to clean out any broken files, I would suggest renaming
your existing program directory, and unzipping a fresh package into the
parent directory, to create a new one (or try Gregg Shaw's Firefox
Drag&Drop install script:
http://www.os2notes.com/os2firefoxdd.html -
the full version supports TB & SM, as well as FF).
I also see that you mentioned experiencing this issue with various FF &
SM builds, which almost rules out an extension (add-on) unique to one or
the other (but not impossible, as more than one might be to blame).
However, if you are in the (bad) habit of installing one version on top
of another, all bets are off. ;-)
As has been discussed, add-ons (extensions) and plugins are different
things. While extensions are not shared between applications and
profiles (usually!), plugins likely are. It is common to have a
MOZ_PLUGIN_PATH in your environment (set in CONFIG.SYS), which points to
a shared plugin repository. Thus, FF, SM, and TB (and other Mozilla
apps) will look for plugins there, causing an issue either created or
exposed by something in that directory to impact any or all of those
apps, depending upon whether they support a given plugin (and in this
case, FF & SM pretty much support the same plugins on the same
platform). That's a common factor to be ruled out.
To rule out some connection issue beyond your machine, do you have
access to one or more of the following:
1. Another machine on the same network, running either the same OS or a
different one;
2. Another bootable partition, with networking support and a web browser;
3. Another web browser in this same eCS installation, such as Arora
(which is Qt-based)?
Just trying to eliminate outside factors.
Cheers/2