Re: Pages Time Out

I'll do that, I'm trying to remember all the different sites I've had problems with. But the screenshots will most likely be identical to what GabeU posted - the TSL handshake is where it hangs.

At work with my laptop now, and have no problems whatsover. I've seen other posts about this spanning on this forum spanning several months, but no definitive answers. But for me, it just started in the last 3-4 weeks.

Re: Pages Time Out

Screenshots are identical to the ones Gabe posted in old post. Except for Outlook - no message ever comes up, it just remains a blank screen. All day, all night, nothing different on refresh or restart or shutdown/restart.

I have already unplugged both HughesNet modem and router, checked tightness of all connections, repowered modem and router. No changes.

Re: Pages Time Out

Sometimes you have to bring the modem and router down, then reboot everything that was using them (e.g., your computer) before you bring the router/modem back up. The reason is that if the computer (or other device) already contains the corrupted entries, it could just be re-corrupting the modem/router again once they connect to it.

As I say that, once everything is back up, might want to use the HughesNet app to check the wifi levels where each wifi device is normally used. The DNS can easily get corrupted on several devices if the wifi signal to one device is very weak or intermittent.

* Disclaimer: I am a HughesNet customer and not a HughesNet employee. All of my comments are my own and do not necessarily represent HughesNet in any way.

Re: Pages Time Out

Well, this is frustrating. As recommended, I spent considerable time going through the list of questions posed by Liz, and trying all suggestions. My resulting reply, with screenshots, was marked as spam and won't post. I've done the submit to the moderators, but wow, I hate to think all that effort is wasted.

* Powered up router and connected back to modem and laptop on wifi. Miracle, everything worked.

* IPad working too, just as slow as before, but connecting to sites now.

So I guess it was, as suggested, a DNS issue. I would like to hear from some of the gurus out there - how do these sorts of problems occur? Where do they originate? At the server level somewhere? I do not recall ever having this problem before. Have been on satellite for 2 years, after many years on fiber/cable and dialup before that (I shudder to even recall dialup!).

Re: Pages Time Out

@KatBro wrote:So I guess it was, as suggested, a DNS issue. I would like to hear from some of the gurus out there - how do these sorts of problems occur? Where do they originate? At the server level somewhere? I do not recall ever having this problem before. Have been on satellite for 2 years, after many years on fiber/cable and dialup before that (I shudder to even recall dialup!).

First, glad everything worked out.

A DNS is essentially a database that converts a textual server name like 'www.hughes.net' to a numeric IP address that the internet actually deals with, like '69.35.40.37'.

All wifi is not 100% immune to packet errors, especially if you have a weak or intermittent signal. If the device does a DNS lookup across the network while the signal is iffy, the lookup itself can get corrupted.

Almost everything on the internet has these 'databases' cached to try to make things quicker. So, if the device has a corrupted entry and doesn't know it, it's always going to try to go to a bad IP address.

What's worse is that these databases can propagate over a local network, basically embedding bad entries and wreaking havoc all over the place.

The simplest thing is to try just rebooting the modem to see if that fixes things, and 9/10 it does. But as you've found out, if it has propagated, the only way to solve it is just to do what you did: Bring everything down, then incrementally bring everything back up.

It happens to all wireless routers, not just the 2000W. I used to use a Linksys 4500 backed into my 1100 when I had it. This invariably happened when trying to use my phone to listen to TuneIn, Spotify, TalkSport apps while in my back yard. It still happens occasionally with something like RunKeeper as the phone switches from LTE or 3G from/to wifi as I'm leaving/arriving the house during a run - that's always fun.

* Disclaimer: I am a HughesNet customer and not a HughesNet employee. All of my comments are my own and do not necessarily represent HughesNet in any way.

Re: Pages Time Out

You are correct on the DNS lookup, the TLS handshake takes place after a successful connection when the connections are negotiating the encryption to be used. My problems resolved before doing anything, but the day after Hughes did their maintenance. My guess would be that there was a problem with Hughes since a new version of TLS (1.3) became the standard in August and they didn't get it incorporated until this maintenance. In any case I imagine that everyone now has their problems solved.

Re: Pages Time Out

There's really only a few things that can affect TLS, regardless of version (for which the network should be transparent), namely latency and port blocking.

The only thing in the system that could feasibly make latency worse across the board is congestion, and the only port being blocked is 25, not 8080 (https). Therefore, it's not real likely that HN's maintenance would have cleared it up.

There's a slim possibility that they could have balanced the load on increased capacity to make congestion lighter and response time quicker wrt internal hops. There's also a possibility that they changed upstream providers (which might have an effect). But it's doubtful that any of these would have crowbarred it back within the timeout threshold of all those sites.

So, unsure what cleared your issue up. Maybe a slight power glitch forced it to reboot on it's own. Who knows.

That said... didn't v1.3 become the standard last summer? I think I remember having to completely rewrite a Twitter bot's OAuth because of it (when it suddenly started failing to authenticate for no reason, lol).

* Disclaimer: I am a HughesNet customer and not a HughesNet employee. All of my comments are my own and do not necessarily represent HughesNet in any way.