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.
Product Discussions
