ghostmaster

Fikester, The modems may change, but the service plans for each specific modem to not. Both residential plans for the DW6000 were, and still are 500/50 plans. Now, I always saw 1Mbps, but my plan was still 500/50. But that was back when Hughes was more honest about what they could offer. Its no different than not being able to get the ProPlus plan for a DW7000, because that service plan does NOT match the DW7000, only the HN7000s. Also, the problem with Testmy's first test always being faster than retesting is a problem with Testmy, it's been happening since the facelift earlier this year....so in other words, I agree with you about the testing, just not for the same reason, it's not a speed burst.

Yep. It's like a stripped down, user friendly Nero, and it's free...

CDBurnXP

Trying changing your DNS to 4.2.2.2, as suggestedd in this thread: http://www.dslreports.com/forum/remark,17456289

I also noticed that you have recieved the infamous Nov. 17th firmware update that completely F*cked up everything. Before then your pings should have been between 550 -- 800ms. Yep looks like a broken route. Here's Mine: Tracing route to www.wellsguitars.com [68.178.232.95] over a maximum of 30 hops: 1 1 ms <1 ms <1 ms 192.168.1.1 2 * * * Request timed out. 3 1432 ms 889 ms 839 ms dpc67142142002.direcpc.com [67.142.142.2] 4 892 ms 649 ms 709 ms dpc67142131174.direcpc.com [67.142.131.174] 5 994 ms 1188 ms 959 ms dpc67142131149.direcpc.com [67.142.131.149] 6 880 ms 769 ms 699 ms dpc67142128138.direcpc.com [67.142.128.138] 7 633 ms 719 ms 639 ms 67.96.217.41 8 796 ms 819 ms 679 ms p1-2-0.c0.hywr.broadwing.net [216.140.3.37] 9 702 ms 839 ms 848 ms s3-0-0.a1.hywr.broadwing.net [216.140.0.66] 10 735 ms 650 ms 799 ms G2-5.rp0.snjs.broadwing.net [216.140.2.14] 11 770 ms 669 ms 759 ms 216.140.3.146 12 701 ms 847 ms 689 ms 192.205.33.69 13 746 ms 719 ms 849 ms tbr1-p013004.sffca.ip.att.net [12.123.12.2] 14 1088 ms 889 ms 689 ms tbr1-cl3.la2ca.ip.att.net [12.122.10.26] 15 742 ms 759 ms 919 ms tbr1-cl3214.phmaz.ip.att.net [12.122.10.85] 16 838 ms 949 ms 979 ms 12.122.108.5 17 927 ms 759 ms 749 ms 12.122.255.106 18 781 ms 809 ms 820 ms mdf001c7613r0003-gig-10-1.phx1.attens.net [63.24 1.130.170] 19 * * * Request timed out. 20 754 ms 787 ms 690 ms ip-68-178-232-95.ip.secureserver.net [68.178.232 .95] 21 694 ms 892 ms 899 ms ip-68-178-232-95.ip.secureserver.net [68.178.232 .95] Trace complete. For a test, try tracing my Godaddy site at http://www.heresthething.org. I would sugguest that you go to http://www.dslreports.com/forum/sat, click on the Wildblue tab, and ask others to trace the route. If you can get enough people there to complain about it, you might be able to get WB to do something about it.

Sounds like a case of a broken route. If i'm not mistaken, Wildblue uses AT&T networks at their NOC. Could you post one of the Tracert's here. I'm just curious....

If you have "pan and scan" on your DVD player, or your TV, I think that will spread it back out.. Otherwise, like Dlewis said, the format doesn't match your TV

Nice Fike.... One day I'll have that....one day....

Because they only have limited amounts of bandwidth. They are holding our for the new platform (spaceway 3) next year. Then things should improve.....maybe.....

I doubt it. It would be nice though.

this mornin...still going strong... :::.. Download Stats ..::: Download Connection is:: 2118 Kbps about 2.1 Mbps (tested with 12160 kB) Download Speed is:: 259 kB/s Tested From:: https://testmy.net/ (Server 1) Test Time:: 2006/12/01 - 6:35am Bottom Line:: 37X faster than 56K 1MB Download in 3.95 sec Tested from a 12160 kB file and took 47.031 seconds to complete Download Diagnosis:: Awesome! 20% + : 98.69 % faster than the average for host (direcpc.com) D-Validation Link:: https://testmy.net/stats/id-3YIMJPDRB User Agent:: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; .NET CLR 1.1.4322; .NET CLR 2.0.50727; InfoPath.1) [!]

pam is good, but sticky lol. It might get grime buildup...but you could try it...

Next time you can, put a ton of RAINX on the dish. Ice shouldn't form on it anymore after that...

:::.. Download Stats ..::: Download Connection is:: 1625 Kbps about 1.6 Mbps (tested with 12160 kB) Download Speed is:: 198 kB/s Tested From:: https://testmy.net/ (Server 1) Test Time:: 2006/11/30 - 9:11pm Bottom Line:: 28X faster than 56K 1MB Download in 5.17 sec Tested from a 12160 kB file and took 61.281 seconds to complete Download Diagnosis:: Awesome! 20% + : 52.44 % faster than the average for host (direcpc.com) D-Validation Link:: https://testmy.net/stats/id-HSPB5VOYD User Agent:: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; .NET CLR 1.1.4322; .NET CLR 2.0.50727; InfoPath.1) [!] Needless to say, it will be interesting to see if this holds up tomorrow...

:::.. Download Stats ..::: Download Connection is:: 1647 Kbps about 1.6 Mbps (tested with 20972 kB) Download Speed is:: 201 kB/s Tested From:: http://www.testmy.net Test Time:: 2006/11/30 - 9:09pm Bottom Line:: 29X faster than 56K 1MB Download in 5.09 sec Tested from a 20972 kB file and took 104.312 seconds to complete Download Diagnosis:: Awesome! 20% + : 54.5 % faster than the average for host (direcpc.com) D-Validation Link:: https://testmy.net/stats/id-2BK10A59W User Agent:: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; .NET CLR 1.1.4322; .NET CLR 2.0.50727; InfoPath.1) [!]

Further proof

:::.. Download Stats ..::: Download Connection is:: 2016 Kbps about 2 Mbps (tested with 2992 kB) Download Speed is:: 246 kB/s Tested From:: https://testmy.net/ (Server 1) Test Time:: 2006/11/30 - 8:45pm Bottom Line:: 35X faster than 56K 1MB Download in 4.16 sec Tested from a 2992 kB file and took 12.156 seconds to complete Download Diagnosis:: Awesome! 20% + : 89.12 % faster than the average for host (direcpc.com) D-Validation Link:: https://testmy.net/stats/id-L0PS5YDXT User Agent:: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; .NET CLR 1.1.4322; .NET CLR 2.0.50727; InfoPath.1) [!] I for one AM blazing tonight. I just can't say why.....literally.....I'll get in trouble....

Thanks for letting us know the outcome Van. A lot of people get on the boards, complain a lot, and then don't take anyone's advice. Just remember, when it comes to Hughes, YOU are your best tech support. Congrats on getting it fixed!

I actually cut a thin slit in mine. No probs in a year. Bugs couldn't survive in there anyways with it transmitting..... Although dirt, grime, and other things might get in there....

That's basically what I did. Some people preach covering the holes back up with sealant, or taking the thing apart to let it dry. But cmon, people have used dishes like this for years with no feedhorn cover at all.

ALSO, if you can look at your dish, look to see if there is water in your feedhorn. There was a manufacturing defect which allows water to leak into it. It will cause MASSIVE transmit failures also. Check it out. Please check your grounding as well. You may save yourself a lot of headache...

This sounds like a standard case of "transmitter not grounded". If you get these types of problems while surfing for a little while, then they go away when you stop, then start again. It sounds like static buildup in the modem. Is your dish accessible? Is it on a pole, or the roof? http://www.dslreports.com/faq/2626 Pay attention to the top right graphic. If there isn't a copper wire going from the screw labeled "GND" on the transmitter to the ground, then that is most likely your problem. This is a very common problem, because for some reason (read with a hint of sarcasm), many Hughes installers don't find it necessary to ground the transmitter.

Run-around = 4 levels of support beauracracy. Level 1 and 2 will have you do the same crap over and over again, and blame it on something else. Level 3 will "look" into your modem and check stats/errors and tell you everything looks good. Level 4 will "call you back", but only when you aren't at home.

and expect the run-around...

Thats the funny thing....it doesnt go out during storms..... It's just slow as hell during primetime....