February 18, 2009 8:55 AM
updated: February 18, 2009 9:06 AM
MikeKV said:
manuel2 said: Ok, after not accepting being charged $30 to fix their own error, I decided to try the fix described here. Guess what: worked perfectly, now I'm back to the usual constant 600 kbps with no drops at all. Mine is a Slingbox tuner, the buggy FW was 1.2.8 and now its "downgraded" back to 1.0.1. Slingmedia support LIED to me when they tested my slingbox and told me everything was ok. They misled me by telling me it that the problem was in my own network/router. And then they tried to RIP ME OFF those $30. I am grateful not everyone is like that. Do you think BBB would listen to me?
While I don't disagree that a FW downgrade has fixed some users streaming issues I do disagree that sling would release FW that is known to be "buggy". I had the very same issue as you and it turned out to be a bad internal wireless nic in my laptop...not FW in the slingbox.
I have a couple questions for you.
1) Are you or were you having the streaming problem on ALL of your machines (PCs and laptops)?
2) If you did a continuous ping from a PC or laptop to your slingbox (ex. ping 192.168.1.254 -t)Â on more than one of your PCs/laptops (wired or wireless) that is connected to your internal/home router what are the response times for your internal/home network? I'm assuming your slingbox is using an IP address of 192.168.1.254. If not replace the IP address that I have here with your correct one. Also, when you do the ping make sure the slingplayer software and any other software that may use the network is NOT running on the PC/laptop.
I'm curious to see the results.
Thanks.
ok maybe they din't know it was buggy before releasing it but the fact is that IT IS buggy. Not a single doubt about it. I can recreate the problems as many times as needed, and i can fix them again those many times by downgrading FW. There are several users with the exact same testimonial.
If thats not a bug I will need a very good explanation from Sling.
to answer your questions:
1) the problems were in all the machines I tried of course, since the problem was not on my pc/network
2) The slingbox is not local, its at a data center with its own public ip address and 10 Mbps of upload bandwidth.
truncated ping:
6.40.15.51: bytes=32 time=249ms TTL=240
6.40.15.51: bytes=32 time=251ms TTL=240
6.40.15.51: bytes=32 time=259ms TTL=240
6.40.15.51: bytes=32 time=256ms TTL=240
6.40.15.51: bytes=32 time=250ms TTL=240
6.40.15.51: bytes=32 time=259ms TTL=240
6.40.15.51: bytes=32 time=243ms TTL=240
6.40.15.51: bytes=32 time=258ms TTL=240
6.40.15.51: bytes=32 time=250ms TTL=240
6.40.15.51: bytes=32 time=254ms TTL=240
6.40.15.51: bytes=32 time=246ms TTL=240
6.40.15.51: bytes=32 time=244ms TTL=240
6.40.15.51: bytes=32 time=249ms TTL=240
6.40.15.51: bytes=32 time=250ms TTL=240
6.40.15.51: bytes=32 time=257ms TTL=240
6.40.15.51: bytes=32 time=249ms TTL=240
6.40.15.51: bytes=32 time=249ms TTL=240
6.40.15.51: bytes=32 time=249ms TTL=240
6.40.15.51: bytes=32 time=252ms TTL=240
6.40.15.51: bytes=32 time=251ms TTL=240
6.40.15.51: bytes=32 time=1438ms TTL=240
6.40.15.51: bytes=32 time=258ms TTL=240
6.40.15.51: bytes=32 time=248ms TTL=240
6.40.15.51: bytes=32 time=259ms TTL=240
6.40.15.51: bytes=32 time=271ms TTL=240
6.40.15.51: bytes=32 time=251ms TTL=240
6.40.15.51: bytes=32 time=247ms TTL=240
6.40.15.51: bytes=32 time=245ms TTL=240
6.40.15.51: bytes=32 time=261ms TTL=240
6.40.15.51: bytes=32 time=269ms TTL=240
6.40.15.51: bytes=32 time=256ms TTL=240
6.40.15.51: bytes=32 time=245ms TTL=240
6.40.15.51: bytes=32 time=251ms TTL=240
6.40.15.51: bytes=32 time=255ms TTL=240
6.40.15.51: bytes=32 time=255ms TTL=240
6.40.15.51: bytes=32 time=261ms TTL=240
6.40.15.51: bytes=32 time=255ms TTL=240
6.40.15.51: bytes=32 time=248ms TTL=240
6.40.15.51: bytes=32 time=252ms TTL=240
6.40.15.51: bytes=32 time=248ms TTL=240
6.40.15.51: bytes=32 time=264ms TTL=240
6.40.15.51: bytes=32 time=257ms TTL=240
6.40.15.51: bytes=32 time=243ms TTL=240
6.40.15.51: bytes=32 time=255ms TTL=240
3) thats at home, which is very far from where the SB is.
Previous Thread
RSS
