User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; Trident/4.0; Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1) ; .NET CLR 1.1.4322; .NET CLR 2.0.50727; .NET CLR 3.0.04506.648; .NET CLR 3.5.21022; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729; .NET CLR 4.0.20506) Build Identifier: http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-trunk/firefox-3.6a1pre.en-US.win32.installer.exe I spent some time discussing this on the mibbit chat line earlier. They were unable to reproduce the bug, but suggested numerous troubleshooting steps. They said it had to do with dns, a .net extension and the css page display. We got it working, but as soon as I cleared my private data, my next visit to http://www.nlm.nih.gov/medlineplus/directories.html; http://webapps.ama-assn.org/doctorfinder/html/patient.html would either give me a message saying "firefox can't find the server" or cause the page to display something that looked like the text in notepad. Reproducible: Always Steps to Reproduce: 1. Install 3.5 (any version, apparently). 2. Try to access majorgeeks.com, freewarefiles.com or website above. 3. Wait a few minutes after firefox fails and then access same site in IE8. Actual Results: Go to altavista.com. Go to majorgeeks.com. Click on links at majorgeeks.com. Go to freewarefiles.com. Go to www.nlm.nih.gov/medlineplus/directories.html. Go to webapps.ama-assn.org/doctorfinder/html/patient.html. Page either won't display at all or look like notepad text. Then dns locks up (for lack of a better word) and can't access any websites at all for several minutes. Then can access all of these in IE8 without any problems. Seems like other users having similar issues from viewing support forum, but no one at mibbit was able to reproduce this so maybe it is something on my machine. I finally gave up and uninstalled 3.5. I went back to 3.0.11 and everything is back to normal. Expected Results: I tried everything you can think of, every possible way to fix the problem and nothing worked until I went back to 3.0.11. It should have worked. I can't imagine what software on my machine possibly would be different than the people at mibbit. I am really disappointed that 3.5 doesn't work and I won't ever update the software unless I can be sure that this problem is resolved.
http://www.nlm.nih.gov/medlineplus/directories.html;%20http://webapps.ama-assn.org/doctorfinder/html/patient.html doesn't seem to exist. I tried the first three, but I assume all your links are working. Sounds like a firewall problem. You should give the new version 3.5 permission to access the internet. Please read: http://support.mozilla.com/en-US/kb/Firefox+cannot+load+websites+but+other+programs+can
Ria Klassen, they are two different links, try first-- http://www.nlm.nih.gov/medlineplus/directories.html then from Doctors and Dentists--General select the first link for * AMA Physician Select: Online Doctor Finder (American Medical Association) which is http://webapps.ama-assn.org/doctorfinder/html/patient.html Regarding 3.5 permission to access the internet, I reset the permissions for it in the firewall multiple times and even uninstalled and reinstalled the firewall and then reset the permissions multiple times. The firewall was not the problem with 3.5. The problem was when I accessed http://webapps.ama-assn.org/doctorfinder/html/patient.html the css style sheet would not load in 3.5 and then all internet connections on the computer would lock up for a few minutes. However, if I loaded the same page in IE8 this would not happen and if I loaded the same page in 3.0.11 it would not happen. Someone at Mibbit gave me links to the css style sheets and then the page would load but then then it started having problems again several hours later. The only reason I am reporting this bug is because other people are having similar issues and there is something changed from 3.0.11 to 3.5 because it works perfect in 3.0.11. See this page-- http://support.mozilla.com/tiki-view_forum_thread.php?locale=en-US&forumId=1&comments_parentId=381737 That person has Windows Vista; I am using Windows XP Service Pack 3.
If you create a new profile, and you run this with the newly installed Firefox, what extensions do you see. Tools > Add-ons > Extensions. Are you ever using those extensions. If not, can you disable them.
You have also such a weird useragent string. Personally I can't see any pages if I use your UA string. So in about:config try to changing the value of the preference general.useragent.override to Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1) Gecko/20090624 Firefox/3.5 http://kb.mozillazine.org/About:config
(In reply to comment #5) > Personally I can't see any pages > if I use your UA string. Sorry, ignore this, there was a copy error.
Nothing in Tools > Add-ons > Extensions, just a blank window.
I just wanted to report that while I was looking online for more information regarding css rendering bugs, I found a link to a "test page" which does not display correctly in Firefox 3.0.11 http://www.zeldman.com/2009/07/09/firefox-test-page/ I have given up on 3.5 for the moment, but wanted to report that I visited the support forum and it appears others are having issues similar to mine. Please see http://support.mozilla.com/tiki-view_forum_thread.php?locale=en-US&forumId=1&comments_parentId=381737 Thank you
I can get this to fail on my machine within 2 min. I have been trying to find out whats going on for three days. As soon as I load ff 3.5 I loose connection to the internet, and I also loose it to IE8. I have nuked my machine three times to try to fix it. I am running vista premium. But I also have a pc running basic and have had no problems with it..........
Mozilla guys, please have a look at this. There is a HUGE thread about this problem on support.mozilla.com, the problem is _real_. Version 3.0.11 and previous don't have the problem! But version 3.5.x doesn't always load the pages, it says "server not found" sometimes. It's NOT normal.
Ok, on my own investigation asking others who have the same problem (via email, or on forums), it seems that MOST of us with the problem are running behind a Netgear router! This is a major clue, I hope. It mostly happens with older Netgear wireless/wired routers rather than the latest models too.
I do not have a Netgear router, I have a Linksys router. I am still convinced it is something to do with CSS rendering and am wondering whether the newest version of Firefox will correct this issue.
No, it has nothing to do with CSS. It is a DNS issue on Firefox's side. If ALL you get is some bad CSS here and there, then you have a different problem.
The only reason I thought it was a CSS problem with firefox 3.5 is because when I accessed http://webapps.ama-assn.org/doctorfinder/html/patient.html I would either get a message saying "firefox can't find the server" or the page would display as text, as if I had set "view/page style" to "no style". However, I never changed anything in "view/page style". I went to http://jigsaw.w3.org/css-validator/ to check out the css rendering of http://webapps.ama-assn.org/doctorfinder/html/patient.html in both firefox and internet explorer. The W3C CSS validator found one error and 102 warnings in both. However, when I would connect with firefox 3.5 and it said "firefox can't find the server" it would then cause a DNS problem whereby any computers connected to my router would be unable to access the internet for a period of time. When I would connect with internet explorer, there was no problem with the one error and 102 warnings on that page. I know that firefox 3.5 uses a different process in CSS rendering than 3.0.11 or than internet explorer. I was wondering if this was possibly triggering the DNS problem, that's all.
I am curious to know if anyone from Mozilla has looked at the thread at http://support.mozilla.com/tiki-view_forum_thread.php?locale=en-US&forumId=1&comments_parentId=381737? There are comments from 40+ different firefox users who are experiencing "server not found" problems with various webpages using firefox 3.5 or firefox 3.5.1. I realize you consider this problem unconfirmed because it isn't happening on any of your computers, but it would be really reassuring to the 40+ people who are having "server not found" problems if someone who works for Mozilla could respond if they have read the thread at http://support.mozilla.com/tiki-view_forum_thread.php?locale=en-US&forumId=1&comments_parentId=381737. Thank you.
I fixed the problem. The problem is DEFINITELY an incompatibility with older Netgear routers. I put up another router, from TrendNET, and all is peachy! I don't have the problem anymore. Heck, even this guy who had the problem had to redo the whole networking to fix the problem: http://forum1.netgear.com/showthread.php?p=194754 (and he was using a, surprise, netgear router). The bug is weird, because I had this PC for 4 years now, and the problem only started to occur a few months ago, with IE 7/8 (possibly after a Windows update). Firefox used to work ok. But with the 3.5 update, Firefox started to have these "server not found" errors all the time, just like my IE did. Which means, that Firefox 3.5 now uses a piece of the Windows code to access DNS the same way that IE does it. And that new piece of code seems to confuse netgear routers. Now, you are probably thinking that "if this is a Win/netgear incompatibility we can't do anything about it", but apparently Opera on the same PC doesn't have the problem (unlike IE/Firefox). Maybe Opera bypasses some Windows functions? Anyway, it seems that you either go back to a previous DNS-acquiring model, or the user has to buy a newer router. Getting Microsoft to fix this somewhat new incompatibility would probably be more difficult.
I have an older Linksys router. I have no trouble with firefox 3.0.11 or 3.0.12 or IE8. Maybe if I decide to buy a newer router, I will try using firefox 3.5 again. It is useless with older routers apparently.
I had the same problem last night with FF 3.5.1. I use a SMC router and it works fine when a clean FF 3.0.12 is installed, however when a clean FF 3.5.1 is installed, the "server not found message" will appear within minutes. The issue is not with the router or my DNS ip from my ISP as the same issue occurs when using OpenDNS.
I also tried OpenDNS on my old router and it made no difference with 3.5.1. Firefox 3.0.12 works great on my old router no matter what DNS I use. I wish Firefox would stick with the older DNS acquiring model. What good is the increased speed if people with old routers can't even connect?
The age of a router doesn't matter, it's a broken DNS forwarder in the router. >I also tried OpenDNS on my old router and it made no difference with 3.5.1. Don't put opendns in the router as DNS source, change the DNS server in your OS. >Firefox 3.0.12 works great on my old router no matter what DNS I use Firefox 3.5 is doing DNS prefetching and that causes more DNS request as usual in a short time and the DNS forwarder in your router doesn't seem to like this and that's a bug in the router, not Firefox. Firefox doesn't ask the router itself for a DNS resolution, it asks windows and windows asks the router. Easy to see if you try to load the same address that failed in Firefox with IE, it will also fail because Windows caches the broken DNS resposne. It will work again if you do a "ipconfig /flushdns" on the commandline. You can disable the prefetching : Please open about:config, confirm the warning, create (!) a new boolean pref with network.dns.disablePrefetch=true to disable the DNS prefetching for a test if my theory is correct. If disabling DNS prefetching does fix your issue or putting opendns in your OS as DNS source you can mark this bug as dupe of bug bug 475603
(In reply to comment #20) "The age of a router doesn't matter, it's a broken DNS forwarder in the router." How would I know if the DNS forwarder in the router works or doesn't work since I am not having any other connection problems? "Don't put opendns in the router as DNS source, change the DNS server in your OS." I have tried this also and it made no difference with firefox 3.5. "Firefox 3.5 is doing DNS prefetching and that causes more DNS request as usual in a short time and the DNS forwarder in your router doesn't seem to like this and that's a bug in the router, not Firefox." Are there some settings I can tweak in the router? I am a college student and I cannot afford to buy a new one at this time. "Please open about:config, confirm the warning, create (!) a new boolean pref with network.dns.disablePrefetch=true to disable the DNS prefetching for a test." I wish it was this simple. Unfortunately, that was one of the things I tried before I posted this bug and it made no difference. "You can mark this bug as dupe of bug 475603." I read the material on bug 475603, but I did not understand a lot of the technical language. I don't know if this is or is not a duplicate of that bug. I read on the support forum that users are having problems with the newest version, 3.5.2 and wanting to downgrade to 3.0.13 or lower. If it is a problem with my router and there are no settings to tweak, I will have to wait to try the latest and greatest version until I can afford to purchase a new router.
You have a different issue if using opendns in windows (TCP/IP settings) as DNS server or disabling DNS prefetching doesn't help and other browsers are working fine. Most posts in the support Forum are bug 475603 because they get the same issue if they immediately try to load the same domain name in IE after they got a Domain/address not found error in Firefox.
(In reply to comment #22) Any idea what the issue is then? Is there anything else I can tweak on my system or router? Or should I just use 3.0.13 until I can get new router? Thanks.
I have a thumb drive set up to add devices to my network. My wireless network will work, but IE and foxfire will not work. If I run the 'setupSNK.exe" program it immediately starts working. IE and foxfire will just randomly stop working. I keep a thumb drive loaded to fix it
Hi! Also having this Problem since FF 3.5 Update: Random sites dont load but I get an 404-Error. If i reload a few times, the sites sometimes load. Also carious sites (like amazon.com e.g.) tend to load corruptedly (dont know the proper english word right now), meaning the view of the site is completely disarranged (diffuse font size, pictures (e.g. banners or thumbnails) not loading, layout disarranged, etc.). I have - like many with this problem - a Netgear WGR614 v5 router (most-up-to-date firmware!) I'm using WLan and my machine is a quite new Laptop with Vista Home Professional. Tried everything I could find on the web, several reinstallations, router restarts, different DNS-settings. Problem wouldnt alter, always the same, always reproducible. Only thing that stroke me was, that in FF safe mode the problem didnt *seem to* occur, but i didnt test it often enough to be sure. Also a "clean" Firefox-Installation without any add-ons and anything else wouldnt work. (before i uninstalled Firefox cleanly following an instruction from the wiki-site as far as I remember) Went back to FF 3.0 and it works fine as always, and like it should. To all doubters: it is DEFINITELY NOT A SOFTWARE PROBLEM, apart from the new FF version of course. So it's some incompatibility of the ROUTER and FF3.5! (btw I have NO software firewall at all, only the free AntiVir and SpybotS&D) I hope anyone is working on this problem! dont want to linger on with FF3.0 infinitely and also dont want to have to buy a new router.. oh, btw: i have a laptop with Vista (most up-to-date), quite new one, definitely *clean* (viruses, trojans, etc), using only WLAN. no other specific background-programs than those mentioned above. Best regards from Munich, Germany Quirin K.
If someone wants to be sure that his case is really caused by Bug 453403, he or she can test the following two builds: http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/2008/11/2008-11-11-03-mozilla-central/ http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/2008/11/2008-11-12-03-mozilla-central/ The first build should not have the bug but the second one should have the problem.
2Wire 2701HG-G has the same issue. Guess I have to roll back. This is a real pain.
DEAR FIREFOX DEVELOPERS, WHY IS NO ONE WORKING ON A SOLUTION??? AND WHY IS THE STATUS STILL "UNCONFIRMED???" THIS IS DEFINITELY A MAIN ISSUE!!
I didn't run any tests(don't have the time or inclination). I just rolled back to 3.0.6 and everything's back to normal. No doubt about it being a bug. It does seem like there is very little time between editions. Maybe there should be a longer Beta period before final approval/release? Just a thought.
I've had this problem with 3.5. A rollback to 3.0X eliminates it. I'm using a Linksys wireless router. Will this be fixed?
ISSUE CONFIRMED: someone with "canconfirm", please confirm this bug ASAP. I had the SAME PROBLEM on Ubuntu 9.04_amd64 and found a workaround (see below) FF version info: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:22.214.171.124) Gecko/20090824 Firefox/3.5.3 Router info: Netgear WGT624v3 Wireless Firewall Router Verified latest firmware version is installed: V1.0.128_1.0.1 LOCAL FIX / WORKAROUND: Please open about:config, confirm the warning. FIRST create a new boolean pref named network.dns.disablePrefetch with a value of "true" to disable the DNS prefetching. ALSO toggle the value of the boolean pref network.dns.disableIPv6 to "true" to ensure FF doesn't try to use IPv6 DNS. Note FF3.5.3 STARTED WORKING PERFECTLY AFTER I MADE THE ABOVE about:config MODS. Recommended coding fix is straightforward: - Default BOTH of these settings to "true". - Add two checkboxes to Edit/Preferences/Advanced/Network panel, for the two choices. - Then, only use DNS prefetching if the user checks it off. - And, only use IPv6 DNS if the user checks that off. - Otherwise keep DNS working the way it has for years and years. Hope this helps! -Paul
Please do not request blocking for unconfiormed bugs. confirming means that this must be a bug in Firefox/Gecko but for example comment #31 is NOT a bug in Gecko, it's a router DNS forwarder bug (bu7g 475603)
So I can see how there are situations (for example, say, 100 clients behind the router) where the DNS forwarding infrastructure could become overwhelmed even without FF's prefetch. Matthias was kind enough to explain some of the details to me offline. The router is indeed doing the wrong thing when it's overwhelmed - rather than simply dropping the requests, it's returning "host not found" which is totally wrong to do. I agree now that this isn't a bug in Firefox and that it shouldn't be addressed with a coding fix. How about DOCUMENTATION though - it would be extremely useful to have this issue well documented, along with the fix of the two entries in about:config
Erm, no, this is not the case here. There are only 1-2 clients at the time in my home, not hundreds. Which means that something else is the problem, since there's a strong coloration of the problem with Netgear routers. However, I was able to reproduce the problem on my other Vista PC, with a DIFFERENT router, AFTER I had installed some VisualC++ standard libraries (part of a major application's installation), but the problem went away after I rebooted the PC. But the problem wouldn't go away on my XP PC with a Netgear router. Which means that the bug happens because of a lot of things, not just Firefox, not just because of the router, not just because of libs installed, and not just because of Windows.
Eugenia - I don't have hundreds of clients either. However, I think I can help you to understand how this is still the correct explanation for the problem. Unless you've told FF 3.5 not to use DNS prefetch (per the about:config tweaks recommended above) you'll see the problem even with only a few other clients. FF's new "DNS prefetch" can easily put a demand on DNS that's somewhat like having some hundreds of non-prefetch clients putting "reasonable" demands on DNS. That's what I was trying to communicate. ALSO - once the OS has a "host not found" response from a given host, it may well CACHE that answer, which is why others have seen I.E. fail and why you saw a problem until you rebooted. THANK YOU for your feedback though - it's helpful to have the experiences of others to learn from.
again per comment 26, IF YOU SEE A PROBLEM, test these two builds and report results http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/2008/11/2008-11-11-03-mozilla-central/ http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/2008/11/2008-11-12-03-mozilla-central/ The first build should not have the bug but the second one should have the problem.
Reporter, are you still seeing this issue with Firefox 3.6.13 or later in safe mode or a fresh profile? If not, please close. These links can help you in your testing. http://support.mozilla.com/kb/Safe+Mode http://support.mozilla.com/kb/Managing+profiles
Whiteboard: please test before commenting → [CLOSEME 2011-2-25]
(In reply to comment #37) > Reporter, are you still seeing this issue with Firefox 3.6.13 or later in safe > mode or a fresh profile? If not, please close. These links can help you in your > testing. > http://support.mozilla.com/kb/Safe+Mode > http://support.mozilla.com/kb/Managing+profiles As far as I am concerned, the issue can be closed. But as I bought a new router 2 years ago, maybe I don't qualify to say so. With the new router there never appeared a similar problem again.
This bug has had the CLOSEME tag for several weeks and the date in the tag is far gone. If the reporter can still see this issue, Please retest with Firefox 3.6.x or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). Then please remove the closeme tag in the whiteboard, mark the bug against the proper version and comment on the bug.
Status: UNCONFIRMED → RESOLVED
Closed: 9 years ago
Resolution: --- → INCOMPLETE
It is resolved finally! Using Mozilla Firefox 3.6.13. Thank you!
Resolution: INCOMPLETE → FIXED
You need to log in before you can comment on or make changes to this bug.