"Error connceting socket"

[imlomax]

That is the message I get (No, I didn't spell it wrong by accident). This comes up in a small box named "A" with an OK button when I begin to stream audio (e.g. when I press play in Winamp). Does anyone know what is causing this and how I find out which socket it's trying to connect to? I am trying to run Wingate off the same machine and it may be interfering but not on any of the ports listed in the Shoutcast ini file.

FYI, Shoutcast still funtions normally even with this error message. However, if I leave it going, the message boxes keep coming up (apparently trying a different socket each time) until Windows says it is out of sockets. Then I have about 80 of those boxes to close when I get back.

This is annoying and I haven't seen any other posts that mention the exact same error.

[Chris @ RCN]

Are you serving off the same box or a remote site?

[castmaster@kx96]

Seems I get the same thing and I am serving off the same box. Hope someone can answer.

Thanxs

[pyremage]

I'm having the same prob. It seems to have started when I upgraded the server to the new "SHOUTcast WIN32 Console/GUI server v1.7.1," running on my Win2k ws. I also upgraded to the newest winamp player at the same time. The problem stems from trying to pass the song title from the source over to the server...thus the port errors. If you uncheck the song title box in the source plug-in, and hit apply, it will stop the port errors, but that's it...I had to back-grade both my installations to get a useable stream again. I still don't have the song titles anymore, though. (This also affects how the song tilte shows up in web pages and on the ShoutCast server.

Someone please help!!!!!!

------------------
Till We Net Again,

PyreMage

[Snag]

I have the same problem running the plugin and the server on the same Windows 2000 desktop. The error comes up every few minutes, and over time fills up my task list.

-Jeff Vogelsang
jjv7q@virginia.edu