Oh yes, one other tidbit. I am in the process of dropping my GoToMyPC subscription and changing over to LMI Pro2 (was just waiting for end of previous GTMPC subscription to make a clean changeover). As such, I did for a time have both hosts active on one of my target machines. AT the same time that LMI was failing, GoToMyPC was continuing to work. This is not any slight against LMI at all (have already disabled the other host and staying with LMI), just a data point that whatever is happening with HughesNet has this peculiar wrinkle that is sensitive to some difference between how the two hosts do business, and it at least suggests that LMI might have the potential to do a tweak on their end that sidesteps this issue. Not a sermon, just a thought. :)
Okay, here is another data point. The problem does not appear to be related to Web Acceleration/Turbo Page after all. I put my HN7000S into Turbo Page Bypass mode (using the methodology described at www.dslreports.com/faq/13533) and it did not affect the problem. Confirmed the Turbo Page Bypass mode via the event logs. Passing on the method at the link above in case anyone else wants to try it. Who knows, maybe it will work for someone else. The search goes on...
So I contacted Hughesnet today and here's is what they told me to try:
PROXY SETTINGS SECURE: 1. Click on the "TOOLS" menu from the top menu bar. 2. Select 'Internet options'. 3. Click on 'Connections' tab on the top. 4. Click on 'LAN Settings' at the bottom right corner. 5. Uncheck the option 'Automatically detect settings'. 6. Check the option 'Use a proxy server for your LAN'. 7. Click on the 'Advanced' button. 8. Type 192.168.0.1 in the http textbox, Port 87. 9. Type 22.214.171.124 in the secure textbox, Port 3128. 10. Make sure there are no other numbers in any of the textboxes below. 11. Type 192.168.0.1 in the 'Exceptions' textbox. 12. Click on the 'Ok' button. 13. Click on the 'Ok' button to close Internet options. 14. Restart "Internet explorer".
Of course the only thing this accomplished was to make it so I couldn't access https sites any longer. When I asked them to contact LMI so they could work it out together instead of the users being the middleman they said:
Since you are able to browse and access all websites there is no issue with HughesNet. It could be some technical issue with the software. You will have to contact them yourself as you are using the software.
If anybody solves this issue, please post how you did it.
I have two clients on Hughesnet one Cisco and one Sonicwall for VPN. Starting at the end on January I could not maintain a stable tunnel with either. Also LMI would not maintain a connection. Both Sonicwall and Cisco said it was Hughsnet in the finger pointing process. One engineer mentioned to me that if they were increasing their contention ratio this would have a profound effect. I know that DSL common contention ratio is around 1 to 125 and most satellite providers for consumer grade push it at 1 to 250 to get the most efficiency out of their bandwidth. The way LMI hands off after connecting is in essence a tunnel and stablitiy of it is on Hughesbet side.
I don't know if this would matter, but many years back I suffered issues with the service Starband. They used a "sliding or cascading proxy". Which on my secure connections created havoc.
Was wondering if this type of "proxy" issue could be at the heart of the matter with Hughesnet, besides the contention ratio???
I am having the same problem and it started at the same time as everyone else's problems. My call to HughesNet ended when they told me it sounds like a latency problem and that they would gladly transfer me to the sales department so I could upgrade my service plan. Not at all trying to solve the problem. Just wanting to charge me more for bad service. For some reason I am only having this problem connecting to three out of four computers. During my initial troubleshooting I disconnected from our HughesNet connection and connected to my Autonet router in my truck and everything worked fine so I knew it was a HughesNet issue. Hopefully someone can figure this out.
This has been going on for month with my hughesnet / Logmein connection too. I was able to get it to work yesterday. But today... nothing. I blame hughesnet as well. They have no concept that anyone would use the internet for anything other than browsing to the google home page.
I can confirm the same behavior here with HN7000S. Like you, I had tried Mozilla after IE to see if there was any browser dependence but apparently gave up on that path too soon. Chrome works for me same as you describe... Initial timeout on connect but F5 page refresh seems to kick start it into action. This suggests there might be a configuration change in IE that would produce success but have not found any tweaks that work yet. THANKS!
Add me to having this PROBLEM! You would think that the two companies involved could get together on a professional level and figure this out. They both will lose customers! When something as - as sick as this problem is - you need a Dr. and it takes professional to professional to just figure some issues out!! This is one of them. Some of the posts can tell you when exactly this started happening, look back and see what you did that might have started this to happening.
All the while........ If you are out there and having this problem sound off! Let both Hughes and LMI know you are having problems to where we can't get into our needed computers AT ALL - oh maybe one once in a great while.
One gets the impression that neither company much cares. In fairness, LMI claims they didn't change anything. Hughes, on the other hand, is hands-down the worst ISP on the planet. BUT, they have a captive audience and they know it. Most of us who have Hughes would switch to an alternative in a microsecond if we had another option. I know I would. They provide a valuable service to those of us in the broadband wilderness, but that has made them completely non-responsive to their customers and we long-time customers who have had the displeasure of dealing with their so-called customer service know that all too well. If you can browse to a simple website, they consider their obligation to the customer discharged. If Hughes fixes this on their end, it will be entirely by accident. Even if LMI contacted Hughes and tried to resolve this together, I'm not sure Hughes would pay any more attention to them than they do their paying customers.
The one hope here is that Chrome works for the moment (albeit with some delays, timeouts, and page refreshes required along the way), where Mozilla and IE do not. This suggests there is a non-Hughes solution to the problem possible from LMI end if they choose to pursue it. I tried changing some of the IE parameters that might possibly affect this (requires registry edits of things like KeepALiveTimeout and so forth) and have not yet found any that help so it may not be something directly accessible to the user. On the other hand, the script that Chrome runs is clearly different than the one run under IE and these differences may help in chasing this down. In the mean time, we are left to muddle through.