This site can’t be reached The connection was reset error message.

[pankr003]

On Monday I went into town and was able to use www.treasurydirect.gov with a tablet computer with Chrome. When I got back home I tried the same computer with the Hughes network and got the same message as seen in the subject line of this post.  I sent an e-mail to Hughes yesterday and the reply was the problem is being worked on by an advanced engineering group so should wait for a call. So for now no resolution in sight.  

[pankr003]

For curiosity I unplugged the modem and then started it up again. I was able to get at Treasury Direct. I clicked the logon button and got a logon screen. I entered my account number and clcked the submit  icon but then got the error message again. Is this progress by the engineers or merey concidence? 

[MarkJFine]

No, there is something in the TLS handshake that is getting cleared by a reboot, but looks like is triggering an internal security issue later.

[budgeta]

I'm experiencing this same issue.  I'm assuming Hughes is still working on it...

[pankr003]

I talked to a  very helpful tech support guy yesterday and he said he was going to resubmit the problem since nobody got back to me when it was first passed up to an advanced engineering group. Please also call them and say there is a problem. I am not sure this one can be fixed but squeaky wheels tend to get more grease. 

[pankr003]

I called them yesterday and the person l talked with tried to get the problem to the engineering group  again. Nobody got back tp me the first time tney tried. If you are having trouble getting 

I hope you will also call them. Squeaky wheels get more grease. I am not sure this problem can be fixed because of the way Treasurydirect does security but hope they do not give up too soon.

[budgeta]

I will call them.  Thanks.

[pankr003]

Bad luck on my end. We got a call this morning from an unknown caller according to Caller ID similar to some people who almost got my wife to give them her Medicare number this week so I let it ring. When I  Googled the telephone number it turned out it could have been Hughesnet getting back in two days. I called back but it must not have been a number people answer.  If anyone gets any more information I hope they will post it. I will start again when I get time to see if I can learn why they called. 

[maratsade]

I wouldn't have picked up either -- I would imagine though that Hughesnet would not come through as unknown.

[GabeU]

---

@pankr003 wrote:

Bad luck on my end. We got a call this morning from an unknown caller according to Caller ID similar to some people who almost got my wife to give them her Medicare number this week so I let it ring. When I  Googled the telephone number it turned out it could have been Hughesnet getting back in two days. I called back but it must not have been a number people answer.  If anyone gets any more information I hope they will post it. I will start again when I get time to see if I can learn why they called. 

---

I don't blame you.  I don't pick up "unknown" calls, either.  And, really, even if there is a number and name, if I don't recognize it I still don't pick it up.

Gotta be very careful these days, unfortunately.