Dropped Connections
 

Hi,

I'm seeking some ideas on a problem I'm having.

I have my own dedicated server that I set up Shoutcast on to broadcast our church services.

The server is running fine and has plenty of available bandwidth.

I've done some testing from home (1.5meg DSL)and had a couple friends listen with no problems. I decided to go live today at church and had two listeners. Both listeners reported that they kept getting dropped after 6 minutes and 30 seconds of listening.

At church, I was broadcasting from my laptop through a Wi-Fi connection to a 256k up/down DSL connection.

As near as I could tell through WinAmp, I was not losing connection to the server. The status showed a continuous amount of bandwidth and connection time. If I was losing connection at the Wi-Fi level, I should be able to tell that from the WinAmp interface, right?

Before I start to pull 100' of cat5 through the insulation in the attic to get a wired connection to the sound booth, does anyone see any significance of the 6-1/2 minute connection then drop problem? Now, I don't know if both users were getting dropped at the same time, but they both did report that it was right at 6-1/2 minutes between drops.

Thanks for any advice you may have.
:)

Do you have access to the log file the DNAS creates?

Tom

Yes, I do. This is the entire log from the time I started broadcasting until I stopped.

There are so many "starting" and "connection closed" messages in the same second, I don't know what is normal.

<11/26/06@09:51:41> [main] Listener Max Connect of (300) Minutes, set.

That's what's responsible for kicking your listeners. It says minutes but your listeners are getting kicked at 301 sec and I thought I remember an issue of min vs. seconds on that setting. Anyway try changing or disabling that and see what that does for you, also there are no signs of you losing the source connection so there's no need to go into the attic.

Tom

Ah ha . . . thank you!

Now that you point it out and I see it, it should have been obvious. Timer set to 300, connections closed at 301. Since the config file said "minutes" I didn't even consider that.

I will completely disable the timer for next week and see what happens. I just thought I'd set it high in case I went off and forgot to turn off the stream and users forgot to close their players, they wouldn't be playing silent bandwidth all day.

I suppose in my testing, I was listening from other machines on a network with the same public IP so the timer ignored those . . . it makes sense.

Thanks again, Tom. Sometimes we just need someone to point out the obvious.

:up:

I have the same problem
 

Hello I have the same problem you can view my log:

<08/22/07@13:42:14> [dest: 201.230.103.60] starting stream (UID: 4)[L: 1]{A: NSPlayer/11.0.5721.5145 WMFSDK/11.0}(P: 0)
<08/22/07@13:42:14> [dest: 201.230.103.60] connection closed (1 seconds) (UID: 4)[L: 0]{Bytes: 17294}(P: 0)
<08/22/07@13:42:15> [dest: 201.230.103.60] starting stream (UID: 5)[L: 1]{A: NSPlayer/11.0.5721.5145 WMFSDK/11.0}(P: 0)
<08/22/07@13:42:16> [dest: 201.230.103.60] connection closed (1 seconds) (UID: 5)[L: 0]{Bytes: 56498}(P: 0)
<08/22/07@13:42:16> [dest: 201.230.103.60] starting stream (UID: 6)[L: 1]{A: Windows-Media-Player/11.0.5721.5145}(P: 0)
<08/22/07@13:42:17> [dest: 201.230.103.60] connection closed (0 seconds) (UID: 6)[L: 0]{Bytes: 14390}(P: 0)

What could be the problem? thank you.

Joel Guillen

Re: I have the same problem
 

This is the problem:
http://forums.winamp.com/showthread....hreadid=270847

Nothing to be too concerned about.

I am having the same problem - I have disabled the Listener connection timer, and have also re-loaded a fresh config file, but am still getting the same error.

Any suggestions?

Shoutcast running on a remote Linux box.