We would need an expert on DNS resolution at Mozilla to look into this. Sometimes they load and then they stop loading, and then if you hit refresh a lot they sometimes then load again, or you have to wait a minute or two and then they load.įor some reason using an external DNS server has stopped this problem completely, as does going back to FF35. #How to stop imac spinning wheel non responsive upgrade#Whereas the problem a lot of us have is that when we upgrade from FF35 to FF36 we get a lot of Server not found errors when trying to load webpages. Hopefully this will help the developers to pin down the real cause of the problem and fix it in the next release.Īg - your problem does seem different as you had FF36 working. I even copied over a full working profile and the program files directory for Mozilla from my portable which was having no problems and the problem still existed on the desktop, which is why I started looking at the network adapater since everything else between the working PC and the non working one was identical. It is nothing to do with add-ons, profiles or firewall software as I have tried all of these things and only the DNS change made a difference. Something has changed in FF36 and either the way it handles DNS or the way it works with some network adapters. Not a clue why this works but it is 100% successful on my desktop PC, whereas before I could hardly connect to a webpage with FF36 without multiple page refreshes and much frustration, even though FF35 was fine and rolling back to FF35 was also fine. ![]() I set mine to use the two google DNS servers: If you manually set your network adapter DNS to an external DNS server (as opposed to your local ISP) then the problem goes away. ![]() I have found a work around for all the people having server not found problems with FF36.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |