Update to "This site can't be reached--after HughesNet modem replacement"
This refers to a thread marked Solved.
The problem actually was NOT fixed by rebooting all of the equipment.
In the first reboot, to simplify things I did NOT restart a wireless D-Link modem I use to add ports and range to my network. I left it off, and everything worked ok, making me think the reboot solved the problem. After a couple of days, I plugged the D-Link router into the wall socket to restart it, and shortly thereafter some of my devices started having the "This site can't be reached" problem again.
I did the power-off/reboot everything routine, including the D-Link, but that did NOT work. I puzzled over this for a while, then I unplugged the D-Link. Everything starting working again. I plugged the D-Link back in, and the problem returned. Aha!
So the problem was that the D-Link modem was "polluting" the network with bad DNS addresses for some websites. I have no idea how this actually happens, nor have I tried to restore the D-Link modem to working condition. It is gathering dust in a box at the bottom of a closet, unplugged and no longer causing harm.
In other news, Hughes customer service is demanding that I return the old HT1100 modem (it was zapped by lightning, the original cause of my recent troubles). I'm being threatened with a $125 unreturned equipment fee. Oddly, the written instructions I received with the replacement modem directed me to NOT return the old failed HT1100, presumably because it is an out-of-date model.
Hello pferron,
Thank you for the followup, it is unfortunate about the router. Perhaps it can be used as a repeater later on. Regarding the return of the HT1100, you are correct it does not need to be returned. It is possible our agents are looking at an old guide, so I'll check out the case notes and find out what they were referencing so it can be updated.
-Amanda
