Forum Discussion
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...
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.
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.
By rebooting everything, you likely cleared the DNS cache(s), which may have fixed it.
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.
Good morning pferron,
Thank you for this additional information, I've sent it over to the engineers for their insight. Your cooperation, patience, and understanding are much appreciated.
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, I did those steps exactly as you described--and it seems to have worked! Have been able to access all the usual sites including Amazon and others (AWS-powered?) without issues from our two desktops and my two smartphones. It's been about 90 minutes and all is well.
I think I need to have my wife turn off her smartphone before she gets home, then boot it up when she gets here, so (a) she will be able to access Amazon etc. sites, and (b) so her phone doesn't pollute our network with any corrupted DNS stuff.
Many thanks for the help. I'll wait until tomorrow to confirm all is still well before marking this problem solved.
