Comment #92 on issue 89 by [email protected]: Error 2
(net::ERR_FAILED): Unknown error.
http://code.google.com/p/chromium/issues/detail?id=89
Same error snafu (no sites accessible w/this error, but IE's browser works
fine)
started right after I unticked NIS2009 from (msconfig's) 'services' list
and re-
booted). I disable NIS that way because of Symantec's mindlessly
exacerbated
process of disabling it's molassis-ware AV (which is too much of a headache
to
disable it's propensity to interfere with my uses of media editoring and
capturing
software).
Without remedy to this 'chrome' issue, I tried all suggested recommendations
mentioned above, disk cleanup, clearing browser history, cookies, etc. But
oddly
noticed that despite NIS's not running (as I've as said, diabled it's
service),
still NIS's firewall is lisyed as running when I checked the Windows
Security
Center. See below for added enlightening.
So I tried re-ticking NIS' in msconfig, exited msconfig w/o re-booting and
tried
manually staring NIS. Instead of NIS starting up, instead it's 'One Click
Support'
window popped up briefly, was replaced by a window displaying the same
Symantec
article mentioned earlier in post 86 ('recommending NIS uninstall, etc').
Anyway after I re-booted, NIS' started up w/o issue, and only then did
Google's
Chrome browser begin working again. I tested the scenario again, this time
I first
turned off NIS's 'smart firewall' (before my later disabling/un-ticking NIS
in
msconfig's services) and this time Chrome worked fine both before and after
re-
booting.
Ipsofacto, firewall is the underlying issue, but at the very least, the
Chrome
browser's inability to prompt us of that isn't helpful at all.
FWIW, in that I never run Windows default firewall and I noticed that I'd
left NIS's
'smart' firewall enabled (before I 'disabled' NIS in msconfig), obviously
NIS's last
firewall setting was still casched in the Windows Security Center, but
moreover it
was still running despite NIS's having been removed/disabled in msconfig's
services'?
While nobody can deny Symantec doesn't have issues, I'm guessing that
the 'unknown'
browser issue isn't necessarily a Symantec matter, but is caused by some
issue
directly related to some sort of compatability problems between Windows
Security
Center (a running firewall regardless of it supposedly not being able to
run) and
moreover, the Google browser's inability to diagnose and prompt us of a
firewall
issue. Chrome's error should be telling us something like 'check Windows
Security
Center and/or running firewall'.
Happ-e-trails to all
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
--~--~---------~--~----~------------~-------~--~----~
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/group/chromium-bugs
-~----------~----~----~----~------~----~------~--~---
