2 major unsolved yp.shoutcast problems

Unorthodox Behaviour · 26th May 2000, 01:32

I am a shoutcaster for over a year now - relaying a low stream for www.splungeradio.com (progressive rock). Recently I am not able to get listed on yp, and since the dawn of time i cannot have my correct IP displayed on yp. Details:

PROBLEM 1 (recent):

In thread "Hmm yp.shoutcast.com" started by AndyB on 8 May 25, 2000 05:58 PM , i understood other people have the same problem with me: starting recently, every second we all get the same error:
[yp_add] yp.shoutcast.com gave extended error (Connection refused)
[yp_add] yp.shoutcast.com gave error (nak)

Changing ports or everything does not help. Also I NEVER used icecast or any other relayers like live365.com. Therefore I am not banned or something

PROBLEM 2 (never solved):
I am behind a cache that caches port 80. This causes my yp.shoutcast listing to show the cache's IP and not mine. The shoutcast online docs mention "alternate" port 800 can be used - but this never worked for me. (BTW, and in a satanic context, the .ini mentions an alternate port of 666...)

I am not lazy and have sent several letters to Tom, nullsoft, Bill Gates, George Clinton and others. Tried #scoutcast in IRC, Efnet. Never got reply. Hope someone can enlighten me. TIA.

1st June 2000, 04:16

I am getting the exact same* problems with mine. Whats up with this damn company? How come they don't report what the hell is going on? Or give users info or fixes for the problem?

I'm still hacking on a cure - but I feel the problem is on Shoutcast's end. They must* have some major problem thier not telling thier users about.. And thats freakin' lame WinAmp!

1st June 2000, 05:29

*jaws music* waves ~~~~~~~~~~~~~~*AOL*~~~~~~~~~~~~~~~ waves

Highway 420 · 1st June 2000, 07:26

Patience, people...I've been doing this for awhile, and I can tell you all the yp.shoutcast.com stuff is due to their new security protocols. There's always something crashing somewhere - it's a relatively new technology. So, have patience and they'll get things straightened out. By the way, if you just let your broadcast run, it'll eventually be listed on Shoutcast's site. It takes some time, but there's not much else to do about it right now.

peppert · 1st June 2000, 18:38

Your webcache is, indeed, the problem. Your ISP should be able to disable it for you if you have a static address.

I'm *still* pushing to get an alternate port working on the yp servers, but the going is slow (imagine AOL's delight at opening port 666 in the firewall to these hosts

)

calseeor · 1st June 2000, 19:34

What is wrong with you people? This service is free. If something does not work, while that sucks, it is still free. The shoutcast people and winamp people have given us all an amazing product. Try being more productive in solving your own issues rather then swearing at these people. It seems, the more people get for free, the more they expect.

2nd June 2000, 01:48

What I have found...

The way the new yp listing works is fairly straightforward...When the SC_SERV goes to list your broadcast it makes a call to addsrv (yp.shoutcast.com/addsrv) and passes it all your broadcast info (title, genre, etc) *and* the port number (of the locally running SC_SERV). Addsrv (CGI script) then turns around and determines where the request came from (getenv("REMOTE_ADDR")) and then does a connect on that IP at the port specified in the request. If it cannot connect, then you get the connection refused error back from the yp_add, if it does connect and does not find a valid shoutcast stream (I think it looks for 2 things, first, an ICY 200 OK return *and* 8192 bytes of valid mp3 data - within a 10 second period of time). If it does not find a valid shoutcast stream, you get the 404 error.

So, you might ask, why is it not working ?

Most problems I have seen so far with regards to the listing have come from people who are behind proxies (some didn't know they were) or using NAT devices such as bandwidth sharing gizmos (linksys, etc)...

Try the following :
From a machine *outside* your internal network try to connect to the IP

ort of what you think is your externally accessible IP

ort is and send it a GET request, either telnet to it and send a :
GET / HTTP/1.0
or use lynx...And make sure you are doing this from outside your NAT configuration.
If it seems to be working, then from your broadcast machine (behind your NAT device) goto : http://www.oddsock.org/test/wherefrom.php3
This will tell you where yp.shoutcast.com *thinks* your request is coming from. Is this the same as what you thought ?

If all of this checks out and yet you are still not being listed, then it is *possible* (although unlikely) that the yp.shoutcast servers are so overloaded that they cannot connect to and recieve the 8192 bytes of mp3 data within the 10 second timeout.

sorry if I restated/overstated things...

oddsock

Unorthodox Behaviour · 3rd June 2000, 15:14

Oddsocks and the rest thanks a lot for trying to help.
However it seems I am doomed, cause I am behind a national-level http cache (have you ever heard of anything like this before ? If you know any other country in the known Universe that uses a national cache ?).
And i know that the IP of the cache is reported. However things have even worsened the past 2 weeks. I get a new extended error "connection refused", it lists the (cache's) IP and points at the troubleshooting faq. So, without an additional yp port nothing can be done via Winamp.

I think I will migrate to Icecast, use Sonique, unsubscribe to this forum and kiss you all goodbye.

I am not ranting. I am just wondering. In the 20th century (last year) there were good free things on this planet that really worked. Seems that from this century on things have dramatically changed. Perhaps time has come to sell our computers and delve in reading and fishing... the 16th century way. At least that era there was true customer support.

Kas · 3rd June 2000, 17:15

Sonique & IceCast? Dude, that's a lot of DIY stuff and you don't sound like the type. I would keep working with Winamp/ShoutCast.

Or, you can sell your computer and start fishing and reading, but you'd starve to death after about 3 days.

--
Kas

4th June 2000, 15:25

I have the same problem [ <06/04/00@08:13:57> [yp_add] yp.shoutcast.com gave error ()
<06/04/00@08:14:09> [yp_add] yp.shoutcast.com gave error (nak)
<06/04/00@08:14:09> [yp_add] yp.shoutcast.com gave extended error (Connection timed out 128.205.2XX.XXX:8000 check shoutcast.com troubleshooting) ]

i just upgraded my server and sorce sender after i keft getting fatal error so i'm not gonna bitch like some people i love technology and the nullsoft shoutcast winamp team do a GREAT JOB just wondering

:-( if you could foucus more on this problem patch this security thingy please i need listeners :-)

6th June 2000, 09:00

well dude the Nak error is due to the server being the new 1.60 and your using the most recent DSP or your using the recent dsp on an older server version we noticed it does that on the oldest running shoutcast server as well as the first... ragradio. the solution is to make sure that you fill in description genre url at the very least.

as for the IRC channel and the ICQ # and the AIM name. you can leave those blank. If you still get errors put n/a in each of the for mentioned feilds. Its not shoutcast or the website its the way the new dsp is designed.
In my humble opinion they (programmers ) get rushed cuz we want this new stuff so fast that sometimes it seems the little simple things are forgotten. You will also note that some people have problems with the DSP when xmiting on the rec/linein mode thing.... all you hear is an open mic

6th June 2000, 09:03

I gave you the full explaination above please read if you have further questions you may contact me on aim pgpman0024

<BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by Unorthodox Behaviour:
I am a shoutcaster for over a year now - relaying a low stream for www.splungeradio.com (progressive rock). Recently I am not able to get listed on yp, and since the dawn of time i cannot have my correct IP displayed on yp. Details:

PROBLEM 1 (recent):

In thread "Hmm yp.shoutcast.com" started by AndyB on 8 May 25, 2000 05:58 PM , i understood other people have the same problem with me: starting recently, every second we all get the same error:
[yp_add] yp.shoutcast.com gave extended error (Connection refused)
[yp_add] yp.shoutcast.com gave error (nak)

Changing ports or everything does not help. Also I NEVER used icecast or any other relayers like live365.com. Therefore I am not banned or something

PROBLEM 2 (never solved):
I am behind a cache that caches port 80. This causes my yp.shoutcast listing to show the cache's IP and not mine. The shoutcast online docs mention "alternate" port 800 can be used - but this never worked for me. (BTW, and in a satanic context, the .ini mentions an alternate port of 666...)

I am not lazy and have sent several letters to Tom, nullsoft, Bill Gates, George Clinton and others. Tried #scoutcast in IRC, Efnet. Never got reply. Hope someone can enlighten me. TIA.<HR></BLOCKQUOTE>

Unorthodox Behaviour · 7th June 2000, 10:11

My Server is 1.6.0 rc2 (16 May 2000)
My dsp is 1.5.0b2
My winamp is 2.63

description/genre/url FILLED

IRC/ICQ/AIM tried BOTH blank and N/A in all combinations.

<06/07/00@10:06:33> [yp_add] yp.shoutcast.com gave extended error (Connection refused 194.177.210.197:8010 check shoutcast.com troubleshooting)
<06/07/00@10:06:35> [yp_add] yp.shoutcast.com gave error (nak)

194.177.210.197: my national-level FORCED cache. I tried several ports, same results.

stoicite · 8th June 2000, 00:06

<BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>My winamp is 2.63<HR></BLOCKQUOTE>

that very well could be your problem. Go back to 2.62 of winamp and give it a try. Most people find that solves the problem as 2.63 has known bugs.

------------------
kPOT Amped Out: it's like god is rubbing your tummy.

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

26th May 2000, 01:32	#1
Unorthodox Behaviour Junior Member Join Date: May 2000 Posts: 3	I am a shoutcaster for over a year now - relaying a low stream for www.splungeradio.com (progressive rock). Recently I am not able to get listed on yp, and since the dawn of time i cannot have my correct IP displayed on yp. Details: PROBLEM 1 (recent): In thread "Hmm yp.shoutcast.com" started by AndyB on 8 May 25, 2000 05:58 PM , i understood other people have the same problem with me: starting recently, every second we all get the same error: [yp_add] yp.shoutcast.com gave extended error (Connection refused) [yp_add] yp.shoutcast.com gave error (nak) Changing ports or everything does not help. Also I NEVER used icecast or any other relayers like live365.com. Therefore I am not banned or something PROBLEM 2 (never solved): I am behind a cache that caches port 80. This causes my yp.shoutcast listing to show the cache's IP and not mine. The shoutcast online docs mention "alternate" port 800 can be used - but this never worked for me. (BTW, and in a satanic context, the .ini mentions an alternate port of 666...) I am not lazy and have sent several letters to Tom, nullsoft, Bill Gates, George Clinton and others. Tried #scoutcast in IRC, Efnet. Never got reply. Hope someone can enlighten me. TIA.

1st June 2000, 04:16	#2
pj Guest Posts: n/a	I am getting the exact same* problems with mine. Whats up with this damn company? How come they don't report what the hell is going on? Or give users info or fixes for the problem? I'm still hacking on a cure - but I feel the problem is on Shoutcast's end. They must* have some major problem thier not telling thier users about.. And thats freakin' lame WinAmp!

1st June 2000, 05:29	#3
BIGDADDY Guest Posts: n/a	jaws music waves ~~~~~~~~~~~~~~AOL~~~~~~~~~~~~~~~ waves

1st June 2000, 07:26	#4
Highway 420 Senior Member Join Date: May 2000 Location: Lawrence, KS Posts: 161	Patience, people...I've been doing this for awhile, and I can tell you all the yp.shoutcast.com stuff is due to their new security protocols. There's always something crashing somewhere - it's a relatively new technology. So, have patience and they'll get things straightened out. By the way, if you just let your broadcast run, it'll eventually be listed on Shoutcast's site. It takes some time, but there's not much else to do about it right now.

1st June 2000, 18:38	#5
peppert UID 0 Join Date: May 2000 Location: a tent outside forums.winamp.com Posts: 230	Your webcache is, indeed, the problem. Your ISP should be able to disable it for you if you have a static address. I'm still pushing to get an alternate port working on the yp servers, but the going is slow (imagine AOL's delight at opening port 666 in the firewall to these hosts )

1st June 2000, 19:34	#6
calseeor Junior Member Join Date: Jun 2000 Posts: 1	What is wrong with you people? This service is free. If something does not work, while that sucks, it is still free. The shoutcast people and winamp people have given us all an amazing product. Try being more productive in solving your own issues rather then swearing at these people. It seems, the more people get for free, the more they expect.

2nd June 2000, 01:48	#7
oddsock Guest Posts: n/a	What I have found... The way the new yp listing works is fairly straightforward...When the SC_SERV goes to list your broadcast it makes a call to addsrv (yp.shoutcast.com/addsrv) and passes it all your broadcast info (title, genre, etc) and the port number (of the locally running SC_SERV). Addsrv (CGI script) then turns around and determines where the request came from (getenv("REMOTE_ADDR")) and then does a connect on that IP at the port specified in the request. If it cannot connect, then you get the connection refused error back from the yp_add, if it does connect and does not find a valid shoutcast stream (I think it looks for 2 things, first, an ICY 200 OK return and 8192 bytes of valid mp3 data - within a 10 second period of time). If it does not find a valid shoutcast stream, you get the 404 error. So, you might ask, why is it not working ? Most problems I have seen so far with regards to the listing have come from people who are behind proxies (some didn't know they were) or using NAT devices such as bandwidth sharing gizmos (linksys, etc)... Try the following : From a machine outside your internal network try to connect to the IP ort of what you think is your externally accessible IP ort is and send it a GET request, either telnet to it and send a : GET / HTTP/1.0 or use lynx...And make sure you are doing this from outside your NAT configuration. If it seems to be working, then from your broadcast machine (behind your NAT device) goto : http://www.oddsock.org/test/wherefrom.php3 This will tell you where yp.shoutcast.com thinks your request is coming from. Is this the same as what you thought ? If all of this checks out and yet you are still not being listed, then it is possible (although unlikely) that the yp.shoutcast servers are so overloaded that they cannot connect to and recieve the 8192 bytes of mp3 data within the 10 second timeout. sorry if I restated/overstated things... oddsock

3rd June 2000, 15:14	#8
Unorthodox Behaviour Junior Member Join Date: May 2000 Posts: 3	Oddsocks and the rest thanks a lot for trying to help. However it seems I am doomed, cause I am behind a national-level http cache (have you ever heard of anything like this before ? If you know any other country in the known Universe that uses a national cache ?). And i know that the IP of the cache is reported. However things have even worsened the past 2 weeks. I get a new extended error "connection refused", it lists the (cache's) IP and points at the troubleshooting faq. So, without an additional yp port nothing can be done via Winamp. I think I will migrate to Icecast, use Sonique, unsubscribe to this forum and kiss you all goodbye. I am not ranting. I am just wondering. In the 20th century (last year) there were good free things on this planet that really worked. Seems that from this century on things have dramatically changed. Perhaps time has come to sell our computers and delve in reading and fishing... the 16th century way. At least that era there was true customer support.

3rd June 2000, 17:15	#9
Kas Member Join Date: May 2000 Posts: 67	Sonique & IceCast? Dude, that's a lot of DIY stuff and you don't sound like the type. I would keep working with Winamp/ShoutCast. Or, you can sell your computer and start fishing and reading, but you'd starve to death after about 3 days. -- Kas

4th June 2000, 15:25	#10
TdB for TOMdaBOMB Radio Guest Posts: n/a	I have the same problem [ <06/04/00@08:13:57> [yp_add] yp.shoutcast.com gave error () <06/04/00@08:14:09> [yp_add] yp.shoutcast.com gave error (nak) <06/04/00@08:14:09> [yp_add] yp.shoutcast.com gave extended error (Connection timed out 128.205.2XX.XXX:8000 check shoutcast.com troubleshooting) ] i just upgraded my server and sorce sender after i keft getting fatal error so i'm not gonna bitch like some people i love technology and the nullsoft shoutcast winamp team do a GREAT JOB just wondering :-( if you could foucus more on this problem patch this security thingy please i need listeners :-)

6th June 2000, 09:00	#11
Nick Guest Posts: n/a	well dude the Nak error is due to the server being the new 1.60 and your using the most recent DSP or your using the recent dsp on an older server version we noticed it does that on the oldest running shoutcast server as well as the first... ragradio. the solution is to make sure that you fill in description genre url at the very least. as for the IRC channel and the ICQ # and the AIM name. you can leave those blank. If you still get errors put n/a in each of the for mentioned feilds. Its not shoutcast or the website its the way the new dsp is designed. In my humble opinion they (programmers ) get rushed cuz we want this new stuff so fast that sometimes it seems the little simple things are forgotten. You will also note that some people have problems with the DSP when xmiting on the rec/linein mode thing.... all you hear is an open mic

6th June 2000, 09:03	#12
Nick Guest Posts: n/a	I gave you the full explaination above please read if you have further questions you may contact me on aim pgpman0024 <BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by Unorthodox Behaviour: I am a shoutcaster for over a year now - relaying a low stream for www.splungeradio.com (progressive rock). Recently I am not able to get listed on yp, and since the dawn of time i cannot have my correct IP displayed on yp. Details: PROBLEM 1 (recent): In thread "Hmm yp.shoutcast.com" started by AndyB on 8 May 25, 2000 05:58 PM , i understood other people have the same problem with me: starting recently, every second we all get the same error: [yp_add] yp.shoutcast.com gave extended error (Connection refused) [yp_add] yp.shoutcast.com gave error (nak) Changing ports or everything does not help. Also I NEVER used icecast or any other relayers like live365.com. Therefore I am not banned or something PROBLEM 2 (never solved): I am behind a cache that caches port 80. This causes my yp.shoutcast listing to show the cache's IP and not mine. The shoutcast online docs mention "alternate" port 800 can be used - but this never worked for me. (BTW, and in a satanic context, the .ini mentions an alternate port of 666...) I am not lazy and have sent several letters to Tom, nullsoft, Bill Gates, George Clinton and others. Tried #scoutcast in IRC, Efnet. Never got reply. Hope someone can enlighten me. TIA.<HR></BLOCKQUOTE>

7th June 2000, 10:11	#13
Unorthodox Behaviour Junior Member Join Date: May 2000 Posts: 3	My Server is 1.6.0 rc2 (16 May 2000) My dsp is 1.5.0b2 My winamp is 2.63 description/genre/url FILLED IRC/ICQ/AIM tried BOTH blank and N/A in all combinations. <06/07/00@10:06:33> [yp_add] yp.shoutcast.com gave extended error (Connection refused 194.177.210.197:8010 check shoutcast.com troubleshooting) <06/07/00@10:06:35> [yp_add] yp.shoutcast.com gave error (nak) 194.177.210.197: my national-level FORCED cache. I tried several ports, same results.

8th June 2000, 00:06	#14
stoicite Registered User Join Date: Jun 2000 Posts: 194	<BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>My winamp is 2.63<HR></BLOCKQUOTE> that very well could be your problem. Go back to 2.62 of winamp and give it a try. Most people find that solves the problem as 2.63 has known bugs. ------------------ kPOT Amped Out: it's like god is rubbing your tummy.