Never had this problem before. After using internet about 2 or 3 hr,
both IE and Firefox suddenly refuses to open new ip address. The new
address bars remains in blank while no problem on other online activity.
For solution, did some cleanup memory and change firewall thing didn't
solve the problem. The only solution is log off or restart.
Any suggestion?
Have you added any new software to the computer ?
To give an example, I installed an Intel MEI package, to remove
a duff entry from Device Manager (so there are no yellow entries).
Little did I know, that Intel added two plugins to my browser.
I attempted to do a download, and the Intel plugins prevented
the downloaded file from being fully written to disk! As soon
as I checked the browser for plugins, I noticed what had happened,
and disabled the intel plugs. A retest showed downloads worked again.
So plugins can affect browser behavior. And any kind of executable
software could change system behavior as well. (Check Task Manager
to see what is running.)
Other possibilities include your AV package, which may include
clever browser protections, Family filter, nonsense of that sort.
AV packages contain solid core functions worth having, plus bloat
baggage that should be turned off. So have a look through your
AV settings, or check online for known issues with your AV.
An AV is functionally like a rootkit, and "gets into everything".
*******
A program like "WGet" or "CURL", are examples of programs that
just do fetching using web protocols.
http://en.wikipedia.org/wiki/Wget
http://gnuwin32.sourceforge.net/packages/wget.htm
The idea of trying one of these, is to see if any
error messages can be generated, to show there is a
DNS problem, or something else is going on.
Note that, your test case should be very carefully
constructed. You want to form a command that downloads
a single file from a single website. Don't ask the program
to crawl an entire website. You want a single, reproducible
command, that can be used to prove a URL can be converted
into a fetch operation. Sort of like a skeletal browser
operation. Wget will recursively descend a web server,
and pull a lot of data, if you're careless with it.
The idea would be, you'd try the wget operation,
right after the browser exhibited its problem.
On at least one AV, the capability exists to disable
notifications. That certainly avoids "nagging", but also
prevents the AV from telling you when "it has dropped
the hammer".
To use a Gnuwin32 program, you need the binary file from
the bin download, plus resolve the .DLL dependencies
(put the DLLs in the same folder as the bin). When
running the command from the command line, you CD
to the folder containing those files, and then a program
like Wget for Gnuwin32 will work. If you use all the automated
stuff available on the download page, it doesn't seem to
update your %path% variable so that the program
executes immediately in command prompt. So some
navigation is required to get to the folder with
the runtime stuff.
When I download "wget-1.11.4-1-dep.zip", the DLLs are in there,
ready to be added to the folder holding wget.exe.
Paul
