Forum Discussion

pferron's avatar
pferron
Sophomore
6 years ago

This site can't be reached--after HughesNet modem replaced

Short story:  Hughes replaced our modem and antenna transponder after a nearby lightning strike fried both.  We had no problems restoring our WIFI to our desktop PCs and smartphones, but we immediate...
  • MarkJFine's avatar
    MarkJFine
    6 years ago

    Humor me... It's very possible that there is a corrupted DNS record that is just hopping from one device to the other - it happens. They propagate between devices depending on what each device uses as it's DNS 'server', so switching things around wrt to the DNS is just complicating things. Please try the following steps in the order stated, which is the only way to ensure it's been eliminated:
    1. Turn every device using the internet off (computer, phone, tablet...) - everything but the modem must be powered off first.

    2. Reboot the HughesNet modem by unplugging its power plug from the wall socket.

    3. Wait a minute, and plug the modem back in.

    4. Wait another minute until the modem is fully online (all front panel indicators are back on) and start turning your devices back on, one by one.

MarkJFine's avatar
MarkJFine
Professor
6 years ago

There's currently an intermittent problem involving connections to Amazon and others that use Amazon Web Services servers with some installations. The fact that it happened with a replaced modem is likely coincidental. It's currently being researched and should be fixed soon.

  • maratsade's avatar
    maratsade
    Distinguished Professor IV
    6 years ago

    MarkJFine:  The Scourge of AWS. ;)

    • MarkJFine's avatar
      MarkJFine
      Professor
      6 years ago

      I've blocked them from every site I administer.

       

      Edit: Except for about 4 IPs that needed to be keyholed in to support one thing.

  • pferron's avatar
    pferron
    Sophomore
    6 years ago

    Wondering how changing the DNS on my desktop allowed me to get to the Amazon (and other AWS sites)...

    • MarkJFine's avatar
      MarkJFine
      Professor
      6 years ago

      Perhaps, in your case, there was an issue with corrupted entries with the DNS cache. This is actually a more common problem than you'd think.

    • Liz's avatar
      Liz
      Moderator
      6 years ago

      Hi pferron,

       

      I'm glad you found the community, thank you for posting and sharing your findings. I'll send this over to engineering so they are aware. Just to confirm, you had a HT1100 before this last modem replacement? And per your latest post, you resolved the issue by changing the DNS on your desktop, but that the issue persists on the mobile devices despite trying a DNS changer app?

       

        Your cooperation, patience, and understanding are much appreciated.

       

      • pferron's avatar
        pferron
        Sophomore
        6 years ago

        yes, Liz, that's correct, you've restated my problem exactly.