Firefox not even attempting to open some sites

Page 1 of 2 12 LastLast

  1. Posts : 65
    Windows 10
       #1

    Firefox not even attempting to open some sites


    I have two desktop PCs, both running Windows 10 version 22H2 build 19045.4046. On each I'm using my preferred browser Firefox v 88.0.1 with updates disabled. Both installations have exactly the same extensions and plug ins, configured identically. Both machines have Windows Defender running.

    So why is it that one PC cannot access some websites while the other can? Two of the sites I use (or try to use) regularly are twitter.com and avforums.com: the non-co-operative machine doesn't even appear to attempt the connection: whether I type the address in the address bar, click on it from a bookmark, or enter it from a Google search, nothing happens.

    I'm completely baffled by this and would greatly appreciate any thoughts. Many thanks.
      My Computer


  2. Posts : 8,111
    windows 10
       #2

    What DNS are you using are they both the same. From a CMD prompt ping twitter and the other site that will give you the IP then try the IP in ff if it works with IP it's a DNS fault you could check host file as that could stop it
      My Computer


  3. Posts : 65
    Windows 10
    Thread Starter
       #3

    Samuria said:
    What DNS are you using are they both the same. From a CMD prompt ping twitter and the other site that will give you the IP then try the IP in ff if it works with IP it's a DNS fault you could check host file as that could stop it
    Thanks for that: the results were interesting:

    The AV Forums' IP was reported by both machines as 104.22.78.251, but the site doesn't allow direct access so on both computers I got an Error 1003 message. This perhaps represents a step forwards for the non-co-operative machine, which at least recognised the IP address and attempted to open it.

    The IP for Twitter was reported by both PCs as 104.244.42.193. On both computers, putting that in the address bar generated a completely blank screen. Possibly Twitter also bars direct access but for some reason doesn't throw up the error message. Still, again, a step forwards for the non-co-operative PC.
    Last edited by Bert Coules; 17 Feb 2024 at 10:04.
      My Computer


  4. SPB
    Posts : 78
    Windows 10 Home 22H2 x64
       #4

    My first thought was your outdated browser version 88.
    Out of curiosity I tried your twitter IP 104.244.42.193 with Firefox v115.7.0 ESR and it showed not secure: http://104.244.42.193/ in the URL bar.
    I then changed the http to https and Firefox issued a warning regarding a possible safety risk.
    I clicked continue anyway and it showed an empty white screen.

    So it is probably not the browser's fault.

    Did you try to flush the DNS cache of your non-co-operative machine?
      My Computer


  5. Posts : 65
    Windows 10
    Thread Starter
       #5

    SPB said:
    My first thought was your outdated browser version 88.
    But if that were the case why does exactly the same browser work in the other PC?

    Thanks for trying the IPs: I didn't see a warning text in the URL bar on either site but there was icon which when I checked was there on every other (working) site I tried and which I'd never really previously noticed: something like a small shield. I just tried the IP addresses again and this time I clicked on the icon: on both sites: the icon text came up as "No trackers known to Firefox were detected on this page" together with a note that "Enhanced tracking protection is ON for this site".

    Did you try to flush the DNS cache of your non-co-operative machine?
    Thanks for the thought. I just tried it but unfortunately it made absolutely no difference.
      My Computer


  6. SPB
    Posts : 78
    Windows 10 Home 22H2 x64
       #6

    What about your firewall rules / settings? Identical on both machines?
    Can you try to temporarily turn off Defender (Antivirus) on your non-co-operative machine?
      My Computer


  7. Posts : 65
    Windows 10
    Thread Starter
       #7

    SPB said:
    What about your firewall rules / settings? Identical on both machines?
    Can you try to temporarily turn off Defender (Antivirus) on your non-co-operative machine?
    I just tried it: having Defender switched off made absolutely no difference.

    It really is bizarre. The setups on the two PCs must differ in some way but I haven't yet found what it is. Perhaps the next step is to compare the Mozilla entries in the two registries.
    Last edited by Bert Coules; 18 Feb 2024 at 05:33.
      My Computer


  8. Posts : 295
    Windows 10 Pro
       #8

    SPB said:
    My first thought was your outdated browser version 88.
    Out of curiosity I tried your twitter IP 104.244.42.193 with Firefox v115.7.0 ESR and it showed not secure: http://104.244.42.193/ in the URL bar.
    I then changed the http to https and Firefox issued a warning regarding a possible safety risk.
    I clicked continue anyway and it showed an empty white screen.

    So it is probably not the browser's fault.

    Did you try to flush the DNS cache of your non-co-operative machine?
    LOL That's what SHOULD happen!
      My Computer

  9.   My Computer


  10. Posts : 65
    Windows 10
    Thread Starter
       #10

    Thanks for the thought. I'm still convinced that there must be some - possibly very minor - difference somewhere between the two desktop machines, and you've given me another avenue to explore.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 11:21.
Find Us




Windows 10 Forums