Forum Discussion

GabeU's avatar
GabeU
Distinguished Professor IV
8 years ago

Website connection failures starting last evening....

Toggling web acceleration makes no difference.  Restarted modem numerous times.  IE, Edge and Chrome...it does it with those (Firefox yesterday, but not so far today).  It took four attempts just to ...
Performance
  • GabeU's avatar
    GabeU
    8 years ago

    Liz

     

    On a whim I decided to flush my DNS cache, and since doing so everything is fine.  I had tried Google's DNS servers and was still having the problem, so I didn't think flushing the DNS cache would make any difference, but I guess it did.  

     

    I did notice, while using Firefox, that the TLS handshake was the most prominent thing showing during the process of a web page opening, which I could see on the lower left of the page.  From discussion with Corrosive, I understand that Firefox basically takes a longer time to try to open a web page before it gives up, and this may be why Firefox was not messing up like the other three.  It would take a while to open the page sometimes, and, as mentioned, I could see that it was performing a TLS handshake during these delays.  I guess the other three would give up too quickly.  

     

    I'll keep an eye on it (it'll be kind of hard not to) and will post again when I know for sure whether the problem is solved or not.  

     

    Thanks again for the help.  

GabeU's avatar
GabeU
Distinguished Professor IV

Liz

 

On a whim I decided to flush my DNS cache, and since doing so everything is fine.  I had tried Google's DNS servers and was still having the problem, so I didn't think flushing the DNS cache would make any difference, but I guess it did.  

 

I did notice, while using Firefox, that the TLS handshake was the most prominent thing showing during the process of a web page opening, which I could see on the lower left of the page.  From discussion with Corrosive, I understand that Firefox basically takes a longer time to try to open a web page before it gives up, and this may be why Firefox was not messing up like the other three.  It would take a while to open the page sometimes, and, as mentioned, I could see that it was performing a TLS handshake during these delays.  I guess the other three would give up too quickly.  

 

I'll keep an eye on it (it'll be kind of hard not to) and will post again when I know for sure whether the problem is solved or not.  

 

Thanks again for the help.  

Liz's avatar
Liz
Moderator
8 years ago

No, thank YOU for the detailed updates. 

 

  • GabeU's avatar
    GabeU
    Distinguished Professor IV
    8 years ago

    Liz

     

    I think I can say conclusively that the issue has been resolved.  Whether by flusing the DNS cache or coincidence, I've not had one issue since doing so.  It's working perfectly now.  

    • Gwalk900's avatar
      Gwalk900
      Honorary Alumnus
      8 years ago

      DNS values are stored in several places:

      The Modem, The Router and the OS.

      Powering off the Modem will dump that one, powering off the Router will dump that one as well.

      Opening a command prompt and doing a ipcong/flushdns will dump the OS values.

       

      Cleaning out all the dust bunnies is the only sure way.

       

      • MarkJFine's avatar
        MarkJFine
        Professor
        8 years ago

        If loading errors are from the TLS Handshake, DNS could have been at fault, but it'd think it's more likely due to latency.

        Resetting the modem could have popped you into a less populated outroute with less latency.

    • Liz's avatar
      Liz
      Moderator
      8 years ago

      Thanks for the update, Gabe. Glad it's all back to normal. :)