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.

GabeU's avatar
GabeU
Distinguished Professor IV

pferron 

 

With regard to the phone, it's possible that the app isn't properly overriding HughesNet's own DNS.  I found the following concerning a way to change the DNS directly in the phone without having to use any 3rd party app...

 

https://www.dignited.com/33627/change-your-phone-dns-server/

 

Also, have you tried changing the DNS in the HT2000W?  I have mine set to Google's DNS and I don't have any of the issues you're experiencing.  Then again, it's possible that it's your connection path due to your ground station's location that makes the difference, but it still might be worth a try.  To change your HT2000W's DNS, do the following from a LAN cable connected device (in case something causes a WiFi connection loss)...

 

1.  Go to this page, and use admin as the password to enter the WiFi Settings.

2.  On the left, click on Advanced Setup, the DNS.  

3.  Uncheck "Obtain from ISP", enter the DNS info (8.8.8.8 and 8.8.4.4 for Google), then click Save Settings.  

4.  After the settings are saved, log out of and exit the WiFi Settings page.  

 

After this, anything that is connected to the modem and set to automatically obtain the DNS should resolve to using Google's DNS, including your phone (you should disable or uninstall that DNS app if you do this, though make sure to set it back to automatic before doing so).  You can leave the desktop set to Google's, or set it back to automatic.  Either way, it should still use Google's DNS as long as the HT2000W is set this way.

 

pferron's avatar
pferron
Sophomore
6 years ago

Thanks, GabeU.  

 

This morning, before I saw your note, I found that my old Android phone WAS able to reach Amazon and other sites that hadn't been working.  Coincidentally, I just received a new Android phone, and though it connects to my WIFI, it WAS NOT able to reach Amazon and the other sites.  Puzzling.

 

Then I saw your note, and applied the DNS remapping to the Hughes modem.  I rebooted everything after that.  My desktop can reach Amazon etc. as before, but NEITHER of the Android phones can, the old one or the new one.  Drat.  I've just confirmed that the DNS remapping "took"--obtain from ISP is unchecked, and the DNS addresses are 8.8.8.8 and 8.8.4.4.

 

Now I'm thinking that either Hughes applied an overnight fix that made my old Android phone work briefly this morning and that fix was overcome by something else, or the problem itself is intermittent.  But I still have the problem.  

  • MarkJFine's avatar
    MarkJFine
    Professor
    6 years ago

    By rebooting everything, you likely cleared the DNS cache(s), which may have fixed it.

    • pferron's avatar
      pferron
      Sophomore
      6 years ago

      No, perhaps I wasn't clear.  After redirecting the Hughes modem DNS and rebooting everything, my phones CANNOT reach the Amazon etc. sites.  My desktop's access was unaffected by the reboot--it's been able to reach Amazon etc. since I changed its default DNS to Google a few days ago.  

       

      Net-net:  Except for a brief period this morning, my phones can't reach Amazon and other sites thru the Hughes modem, both before and after changing the modem's DNS setting.  

      • MarkJFine's avatar
        MarkJFine
        Professor
        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.