My understanding is that a 2hr HD movie is about 2 gigs so how did I use more than that in 2 minutes.Actually, it can use up to 3GB per hour, so about 6GB for a two hour film. And, with regard to DirecTV on demand, it's usually advised against connecting a DirecTV receiver to Hughesnet, as there is no way to control what data the receiver will use, even when not watching anything on demand. It's possible that it could burn through your entire monthly allotment of data without you ever watching an on demand film or TV show.
It doesn't resolve inconsistent, slow, frustrating service provided by Hughesnet.Yes, it does. It may take time, but troubleshooting usually does. If the tech couldn't figure out the problem, maybe it's not with the Hughesnet installation.
"Liz I understand you want me to run test."
Yes she does, and for good reason.
Here is the Community the Hughes employees are at the corporate level. They have greater knowledge, more experience, and greater latitude with dealing with customer issues.
"That is all that HughesNet ever asks me to do but do not follow up with anything"
At this level of support your issue is first: Document baseline system performance in a controlled set of conditions that generate data points that can be used by Engineering to determine the root cause of the problem.
You are getting an opportunity here in the Community to "short-cut" the support system and get a high level remote diagnosis performed while at the same time getting an immediate escalation to Engineering if that data warrants.
"This is not a solution"
Yes it is. Engineers deal in data, not maybe's, not guess work, not supposition. ....
Data. With out data it's just another opinion.
" I want to speak to someone that can actually solve this"
Do you actually expect to speak directly to an Engineer and have him/her spend an hour attempting to explain to a novice user why you need to connect directly to the modem so as to eliminate any router misconfigurations, QoS bandwidth shaping and a host of other related issues?
Troubleshooting is a matter of Conquer & Divide.
It starts "locally" (read as equipment on your end, both yours and Hughes's) and progresses outward.
The tests performed as specified are essential data points needed to determine the root cause and to then effect corrections.