Disconnect! Is it Shoutcast? Is it v1.9.2? Is it the Router?
I am looking for some help. This may stray outside a strictly Shoutcast technical discussion, but I've tried everything (and everyone) else. There also appears to be a dedicated group of expert moderators so I hope you can help.
Here is my situation:
I am trying to run the audio from a remote studio of an actual radio station in NC to the transmitter site using Shoutcast. Both sites are on the same Cox Roadrunner cable system (less than 10 miles away and on the same node, 24.172.111.xxx and 24.172.111.yyy) and bandwidth does not appear to be a problem. I am using a dedicated Windows 98 machine which appears to be working fine ordinarily. The only software operating is Winamp 2.8, along with Shoutcast plug-in. The live audio goes into Winamp (into a Soundblaster) at the same sampling rate as it goes into Shoutcast. I have no problems operating either Shoutcast (which is v 1.9.2) or Winamp, nor do they have problems talking to one another.
I can access the Shoutcast server fine (and remotely) and no errors show up. In short, everything works. I have a Belkin router on this side with the port forwarding on 8000-8005. I can access the server anywhere both on the lan or outside in a variety of ways (via Winamp, a Lansonic box, a Exstreamer). The problem is that after everything is running great, the system ultimately crashes. Sometimes is appears to be at the Client end, but most of the times it appears to be the Shoutcast server, but there are disconnects. Sometimes it takes about 5 days, then it occurs much more frequently, (at irregular intervals: 35 hours, 21 minutes, or 2 hours, 10 minutes). Many times the Shoutcast server is not accessable remotely. It says it is connected (1/5 clients connected), but the client is not getting anything and is searching. Once you reboot the machine with Winamp and Shoutcast, then try to reconnect from the client,-- IT WORKS AGAIN.
So, there does not need to be any reboot of the router (which I'd suspect, if it were a router problem). The router is doing DHCP, but the leases are forever and the IPs never change. I've also examined the log files and don't see any apparent attacks on the router, either internal or external. I've tried with and without DMZ, same result. Anyone who'd like to help, I'd appreciate it, and I'd be happy to privately give urls so we can try-out whatever.
Is it unrealistic to imagine this technology to work for more than 5 days in a row 24/7? Might upgrading to XP help? Let me stress that the machine has not "frozen" in the standard Windows way. System resources are available and I can access Winamp, see the audio coming on the VU meters, access MS-DOS, etc. It just stops Shoutcasting. I've looked at upgrading Shoutcast, although I've seen no mention of this bug being fixed--thats why I'm using the old Winamp, after hearing about Winamp 5 problems with Shoutcast.
Anyone's help will be greatly appreciated and thanks for reading all this. I'm sorry about the length, but it seems that someone might respond thoughtfully to a laid-out question rather than the standard, "HELP ME FIX WHAT I KNOW NOTHING ABOUT" and a million back-and-forths.