To put it mildly, this error indicates that "YOU" cannot send data fast enough to the target server. Very rarely is this a problem with the server itself. The list below is just a few ways to troubleshoot the problem.
First, copy your stream URL, and paste it into your browser. If you come to your D.N.A.S. page or SHOUTcast Stream Status Page, the server is fine. Now you have to find the culprit.
SIDE NOTE: If the black D.N.A.S. page says "Server Is Currently Down", it simply means that no one is streaming on it at the moment. If the server were truly down, you would not be seeing the page.
1 - Are you, or someone else in your home, downloading anything or listening to your playback while you are streaming? This includes using electronic devices such as smartphones, or tablets. If yes, stop downloading and/or stop listening.
2 - Are you running a lot of programs on the computer? If yes, start closing down additional programs that may be open. This can result in your computer processor overworking itself for the moment.
3 - Is Windows downloading or installing any updates to your PC? If yes, try to stop it, or wait it out. This can consume your bandwidth.
4 - It is possible that the combination of SAM and Second Life will tax your computer processor, regardless of how beefed up your system is. When this happens, your computer is basically doing things in order one after the other as it receives them. The next task may not start until the previous one is completed. You'll find this more on older or non-gaming computers or computers that have been "on" for a long time. Short term fix... lower your bit-rate and see if that helps. Ultimately, you may just need a computer reboot.
5 - Is your ISP doing any kind of maintenance? If yes, wait it out.
6 - There may be something happening between you and the server. This is the Internet and things like this happen at various carrier hotels when networks slow down, or get DDoS Attacked, or just simply get congested. Sometimes the only solution is to just wait it out. Running a TRACERT will help identify if this might be the issue.
So what in the heck is network congestion? Well, think of it this way. You go to work every day. You take the same road every day to your office. One day, there is an accident at one of the intersections. Traffic is backed up. You can't move. Your office, with everyone in it is functioning normally, but you can't get there. That is network congestion. Something in the route to your server has become backed up/congested.
Oh... but you say that if you stream to this OTHER server you have no troubles! Yes! Yes! Yes! That's because your ISP is using a different route to that particular server. It's like the congestion is east of you and your stream server is further east of that congestion, but the other one that works fine is north of you. You're ISP takes a different path to get there.
7 - Sometimes a simple reboot of your router and modem is all it takes. We recommend rebooting the router at least once a month to keep things fresh. It should be done in the following order:
- Shut down the computer
- Unplug the router
- Unplug the modem
- Wait 30 seconds to 1 minute
- Plug the modem in and wait for it to fully initialize
- Plug the router in and wait for it to fully initialize
- Restart your computer.
8 - Try Lowering your bitrate. It may be that the Internet is acting up at the moment or might be your computer. Reducing your bitrate might help.
So, the next time you get this pesky error, ask your provider if they are having trouble with that particular server. If they say no, then you have some options to determine what the cause is. In most cases, it will clear up once the company affected in the routing cleans up its mess - but if the problem is other users in your home downloading large files, or your router or modem or ISP, then you know what you need to do.
When this error hits, keep calm. Remember the actual cause of the issue may be one of thousands. The INTERNET is not a perfect place and things will happen. Streaming media is a "constant" data flow that can be upset by one-millisecond hiccup.
Updated: Aug. 8, 2007
