I'll assume you have a Slingbox Pro-HD since none of the other slingboxes will go near 8k. Your connection should be a point to point connection. If your Slingplayer (client) is on the same subnet as your Slingbox (server) then it should maintain a fast connection.
During the server fiasco, there were several posts suggesting to downgrade to Slingplayer 1.5 which isn't able to accept encoding streams higher than 640x480. Therefore the connectivity would probably top out around 2k. By pressing [Alt]+[Shift]+[i] on either Slingplayer Desktop 1.5 or 2.0, you can verify the encoding resolution within the statistics window.
Another point of contention is using the public IP address of the Slingbox Directory entry while you're on the local subnet. This makes the Slingplayer thing that you're connecting to it remotely. If this is the case, you should either revert back to the Sling ID or add another entry with the private IP address of the Slingbox.
". If this is the case, you should either revert back to the Sling ID or add another entry with the private IP address of the Slingbox."
How do I do this? I'm having a hard time figuring out which IP address my router assigned to my slingbox as I have 7 computers and 2 printers hooked up to it and not all are listed properly in the ip table on my router.
How do I "revert back to my sling ID or add entry with a private IP?"
Thanks for the reply- hoping this does the trick- I'm pretty frustrated
Thanks for the screen shot. I think may show your issue. On the bottom line there is a fin_wait 2 for ip 192.168.1.246 on port 5001. What process is that? What device is 192.168.1.246? Few devices use port 5001. I suspect something in your router or pc networking (tcp offload perhaps) settings are a miss. Is the sling configured as a static ip?
arp -g will list the devices your pc sees. What model is the hub you run? Remove the hub and test.
It could be many things but mostlikely something you changed.
Try pinging the sling continously then start the sling
ping 192.168.1.237 -t
OK, so I sat down 7-8 days ago and opened the player and boom- back to 8000 kbps
I did nothing, I changed nothing and as mysterously as the problem started it went away.
I maintain I think it was on Sling's end and had to do with whatever server/software issues they were having.
I'll be back to continue this if it ever happens again but I had owned my slingbox pro hd for 6 months and never had a problem and don't anticipate problems again...
thanks for your help!
I'm also having bitrate problems. I can connect to my slingbox locally, so I'm talking to my sligbox from my PC with is 15 feet away. The picture is out of sync with the sound. There are missing video frames. The connection between the two devices is 100Mbs. I did a network trace, it looks like there are checksum erros between thePC and slingbox. I have experminted with different PC settings to adjust flow control and packet errors, nothing seems to work. All of this did work a few weeks ago.
I have tried to connect through my browser, firefox 3.6.8, and sometimes is seems to work better than the direct connect.
I have a droid phone and it works just fine. I have also tried another laptop PC, using the browser, and it works just fine.
I'm thinking there is a problem with the IP stack configuration or the video processing on the local PC, but cannot verify this.
It is frustrating, because there are so many "helpful" things going on in the background that cannot be viewed or configured.
Does anyone have any thoughts or ideas as to what to look for or how to fix?
I was having similar problems for the last 3 weeks or so. First it would not connect/failure to find my profile. Then it started connected but the video was super choppy/snowy with a bitrate of only 40 (normally 500).
I went through the set up assistant again and reconfigured the input and that fixed the problem! It's working again at the normal bitrate.....
*** Edited to observe Slingbox Answers Forum House Rules by Moderator. ***