how-to block ads
diablo1892Plough, sew, water, harvest. Repeat.Reviews:
|reply to grohgreg |
Re: HT1000 Anyone seeing this
said by grohgreg:Here's What I do NOT get still.. CORROSIVE told me one day to try turning off web accelerator, few hours later and all red X's completely gone, nothing was wrong for about 4 hours later and it started spitting out RTT or LAN errors (or both) then i turn accelerator back on and whoa what ya know downlink red X's are back and RTT and LAN X's are gone
Mine looked like that too, every single Downlink red X associated with fragmentation errors. Quite a few other red Xs as well, but none as consistent as the Downlink. I had a 15/2 plan, but never saw anything higher than 10/1. I associate fragmentation errors with retransmissions, which in turn reduces throughput speed. After two weeks of uninterrupted red Xs, I sent back the modem and TRIA. Also faxed them a letter from the installer confirming that the issue existed on installation day. I eventually got a refund for the unused portion of the 1st months service, full hardware refund, full installation refund, $12 tax refund.
HT1000/ BeamID 32/ Power Max plan/ 4 pcs on a D-Link wired switch/ wireless D-Link router with password
Support only the gaming company's that matter the most, pay for something that actually is worth buying
or has a good reason for how much it's worth.
grohgregDunno. Ask The Chief
Dawson Springs, KY
Well, LLRTT thresholds are 1500mm (yellow) and 2000ms (red). But I can't see why turning off WebAccel should affect conventional PING times. The protocols are different. WebAccel only accelerates HTTP, PINGs are typically ICMP. The answer might be that Hughes is using a HTTP-PING system.
That said, one of the LAN category parameters that can trigger a red X is "LAN Ping Status". Can only speculate, but maybe it's some kind of ICMP/HTTP conflict as well.
I can now also envision a possible relationship to the Downlink red Xs as well. Assuming yours were fragmentation errors like mine, it's possible that the HT1000 diagnostic software is not coping with the HTTP acceleration algorithm. As a result, the accelerated packets might be mistaken for fragmentation. In other words, a false positive. Just guessing mind you, but it seems possible to link all three categories to HTTP acceleration.
HN7000S - 98cm Prodelin/2w "pure" Osiris - ProPlus - G16/1001H - NOC:GTN - NAT 188.8.131.52 - Gateway 184.108.40.206 - DNS 220.127.116.11 and 18.104.22.168 - Firefox 15/MSIE9 - AV/Firewalled by NIS2012