Bandwidth is the rating of delivered bits per second. This is impacted by the transit time of packet to and from the endpoints. I suspect that the device you're watching *from* has had some network setting changed -- or the route from the sender to the receiver has gotten longer. This is increased round trip time (RTT) and as a result you're left with less available bandwidth. This could be as simple as an additional hop between you and the sender, or as drastic as now consuming data across a problematic Wifi network.
I am assuming that this is a TCP/IP stream.
To counteract the effects of a problem with latency you will need to modify TCP options on the receiver, increasing the TCP window size significantly to improve performance would be my first optimization step. This allows more packets to be in-flight while the ACK travels back to verify that packets were delivered. These settings can be defined at the endpoints which manage the connection, but at no point between.
For further technical discussion, this looks like it addresses all the relevant details :
Do a little math here to see how large the window size should be given the current and worst case scenario RTT.
Let us know how you get on with this.
I appreciate the response, but I don't think this is it.
1.) Ping times to the destination are ~30ms. You're not going to beat that.
2.) Speakeasy.net and speedtest.net both give me bandwidth download speeds 10x what is necessary to receive an HD signal. -- On both ends.
3.) Results are the same from here regardless of wether I am directly connected to the router via CAT6 cable, or using our Wireless N (which has an outstanding signal strength)
I'm fairly certain any applicable settings in my router are already optimized by the firmware, but if you (or anyone else) has something specific, please let me know. I visited the site you posted, and it's informational (nothing I wasn't already familiar with).
Examine the network stream in transit to see if there are packets which indicate window shortening (wireshark, tcpdump) or TCP window size renegotiation going on. If this is not occuring then you can not blame bandwidth and must target higher in your OSI stack. In fact, I'd start higher on the stack - log files ,etc.
I really appreciate the response, but it reads like cryptic chinese to me, and I'm pretty technically savvy. Put it this way, if you gave that response to your grandparents, think of the glossed over look you'd get.
I downloaded Wireshark and will launch it shortly. What is OSI? What log files (where)?
Conspiracy theory? I think not.
Obviously the test on my folks' system was to be expected since he was essentially watching the SlingBox internal to his own network.
I think people tend to forget that SlingBox (the company and not the device) IS an intermediary through this whole process.
So, anyone else find it "mildly coincidental" that I've been dealing with this issue for weeks, and found NUMEROUS posts from other users on this and other forums with the same exact problem, and as soon as I post here it magically is resolved this morning when I went to launch Wireshark to trace the problem?
Funny. Especially considering there has been no change to either network overnight (we were both sleeping).
Calling yourself technical, shooting me down for addressing you casually and stating there are a few places to look with a technical article and then coming back saying that I'm being too technical is poor form.
Choose netstat as your option to track window sizes. Use Linux or OSX since the windows one appears deficient for these options :
Local Address Remote Address Swind Send-Q Rwind Recv-Q State
Track on the Swind and Rwind.
Having a technical background does mean (in my mind) that I have a PhD in system administration and networking
Like I said, your posts have been most helpful and appreciative, but the intended audience should be *anyone* using this forum, from the ley person on up. My desire for more specific instructions/details was so that everyone, including myself, could benefit from your wealth of knowledge. I'm not sure where I "knocked you down" and that surely wasn't my intention. Apologies if there was any indication as such.