Firefox not finding websites on first attempt

User Help for Mozilla Firefox
Locked
tigersnake
Guest

Firefox not finding websites on first attempt

Post by tigersnake »

hello together, I had the same problems using firefox with xp sp2 and ZoneAlarm (51_033)... When I read the statement about backstep from ZA51_033 to ZA51_011 I had an idea: The only solution on my system was, to define a proxy server in ZoneAlarm, now everything works fine, and every internet-adress is opened by the first attempt, maybe it works somewhere else too... :-)
User avatar
Frank Lion
Posts: 21178
Joined: April 23rd, 2004, 6:59 pm
Location: ... The Exorcist....United Kingdom
Contact:

Post by Frank Lion »

Glad to help, tigersnake. :)
"The only thing necessary for the triumph of evil, is for good men to do nothing." - Edmund Burke (attrib.)
.
dsearles
Posts: 4
Joined: October 23rd, 2004, 4:36 am

Post by dsearles »

Frank, Thanks. Switching back to the previous version of Zone Alarm solved the problem. Obviously the most recent version of Zone Alarm conflicts with Firefox. Given the popularity of Zone Alarm, not a good situation for trying to bring Firefox to the masses.

Tigersnake, would you mind posting a little more detail on the steps you took to fix the problem by defining a proxy server in the most recent version of Zone Alarm. I'd like to give it a try but I'm not sure how to define a new proxy server. Thanks

If anyone else knows how to do this in Zone Alarm, please feel free to post in case Tigersnake doesn't check back.
Guest
Guest

Post by Guest »

Toggling the network.dns.disableIPv6 fixed the problem of reaching web sites for me. I have a 500mhz Windows 98 PC. I've been fighting almost the identical problem with Internet Explorer 6.0. This issue, along with all the spyware I recently cleaned from my system, is what drove me to switch web browsers. Thanks Mozilla! And thank you SpeedyGonsales for the very accurate and very crisp soluton.
tigersnake
Guest

Post by tigersnake »

sorry, been at sports yesterday evening...
Here my modifications in ZA in detail:
- open main ZA-control-center
- choose <Overview> - <Preferences> - <General>
- there is a button <Options>
- in the new tab in sub-area <Proxy Configuration> check <Enable Proxy Server>
- and fill in your proxy server. I put in the proxy of my provider (german telekom)
<http-proxy.t-online.de> port <80>
from there on everything has worked fine...
I assume there is a kind of timing problem accessing the dns when establishing the automatic internet connect, because I hadn't got the problems when connecting first and started firefox after that... but however, the probs are gone... looking forward your attempts :-)
Guest
Guest

Post by Guest »

Thanks Tigersnake. I also went on the ZoneAlarm Forum and found comments about Zone Alarm ZA 5.1.033 being a "trouble version" and either recommending people go backwards in versions (removing 5.1.033) or download the new beta version 5.5.035. Thanks again for the response.
jillelaine
Posts: 5
Joined: October 27th, 2004, 12:24 pm

Post by jillelaine »

This (network.dns.disableIPv6, true) fixed my constant "Operation timed out while contacting <website>" too. I was having this problem both at work and at home, with and without various firewall(s), and with completely different configs and OS.

Seems like this is a common problem (look at all the messages in the forums about "time out" issues) that it should be a STICKY. Just my opinion! Anyway, THANK YOU so much SpeedyGonsales for the fix! :-)
Guest
Guest

Post by Guest »

Try adding a public DNS entry in your router or in your network properties.
SpeedyGonsales
Guest

Post by SpeedyGonsales »

I am glad that "my" solution helped (I used google, ping, traceroute and nslookup to solve the issue), but even now sometimes I have problems, and now I checked, it occurs both in IE and FF.
Problem is that some providers use crappy caching-only DNS (crappy isn't for caching-only, but for implementation, although serious provider shoudn't use caching-only DNS).

As I am pleased with my current provider in all ways except DNS, there is simple solution as written above: "Use public DNS server".
How? Find out which public DNS exists in your area, and then go to Control Panel/Networking/TCP/IP Properties/DNS configuration,
and put there x.y.z.q numbers of DNS you have found. If problems become more frequent, then you know that somebody have more
problems than you, and you should try another DNS, or revert to your provider DNS.

And finaly, combining both solutions (public DNS and disableIPv6) should solve all DNS issues for good (if you find good DNS server :-))

HTH

--
God speed
Guest
Guest

Post by Guest »

wheres location bar
Guest
Guest

Post by Guest »

i have the same problem, but the solution doesn't work.

I have ZoneAlarm too.
hybucket
Posts: 418
Joined: September 8th, 2004, 6:55 pm
Location: Boston

Post by hybucket »

I was having his problem occasionally when I read Speedy Gonzales post of 10/12 - so I went to about:config and changed the setting as suggeted...it made it worse! So I went back to the default....but the question remains...is there a definite solution to this and is it being worked on? ANyone know? Like anohter posting, once I go to the site in IE, it works for FF. Strange.
I'm on XP with Verizon DSL
Guest
Guest

Post by Guest »

I just tried what Jadugar posted on page 2. It seems to have worked...ff took awhile to load though. It's the comment about adding a user.txt with a ton of some language.
Guest
Guest

Post by Guest »

just tried to see if there was a bug listed in the bug report site, and of course, the fix I just listed as working above didn't work...sorry. This is something that really really does need fixed in FF.
Guest
Guest

Post by Guest »

I Quit! Until FF fixes it it's back to IE for me. I am not experienced enough to figure this out! IE didn't do this crap every freakin page I load!
Locked