Old 28th February 2015, 01:08   #1
LEON GOAD
Junior Member
 
Join Date: Feb 2015
Posts: 6
Shoutcast

I use shoutcast to stream a feed to another location has worked for 10 years stopped working 2 week ago, set as private, http://24.75.193.150:8000 my server is sending out ok but is block at shoutcast.com can some one help Leon Goad

Last edited by LEON GOAD; 28th February 2015 at 01:14. Reason: put in url of 2nd location by mistake
LEON GOAD is offline   Reply With Quote
Old 28th February 2015, 01:23   #2
DrO
 
Join Date: Sep 2003
Posts: 27,873
the DNAS url doesn't work so if that is a running DNAS, then that would explain why it is not listed as it is not accessible on the internet. best to check the DNAS's logs for any errors and resolve them. additionally, a DNAS set as 'private' will not be listed either.
DrO is offline   Reply With Quote
Old 12th March 2015, 21:51   #3
LEON GOAD
Junior Member
 
Join Date: Feb 2015
Posts: 6
Shoutcast

I realize that it is private. But for over 10 years we have streamed from our main studio to our tower site where our transmitter is. We would type in our IP which was 74.95.130.121:8000. The station would connect.

We have two other ports on that same static IP that works great streaming two other stations. One of them is private and one is public. The port 8000 stopped working about two months ago.

The station feed on that port would cut on and off then it just quit. We have checked our server to make sure that we are getting out to the internet. It is going out to the web but it is blocked at the shoutcast server.

I have talked to one of my internet providers and they traced it back and confirmed that was the problem. They tell me it isn't anything that they can fix, but it is a problem on shoutcast's end.

We have been trying to resolve this. It looks like we are going to have say goodbye to shoutcast, and deaden those ports and put us in another network with new ports. We were totally unaware that shoutcast controlled those private ports.

But to our misunderstanding now we are in a mess because shoutcast won't fix their problem. If anybody can help please do so. This has been very successful especially with streaming our internet station. We would like to continue on, but shoutcast has a major problem and won't fix it. They are up and down with the service on the others. Please help. Leon Goad
LEON GOAD is offline   Reply With Quote
Old 12th March 2015, 22:12   #4
DrO
 
Join Date: Sep 2003
Posts: 27,873
nothing can be fixed on SHOUTcast's side since at the moment, i've still got very little information to go on in-order to help you with the listing issue.

as neither of the IP addresses you have mentioned are intentionally blocked on the SHOUTcast Directory side i.e. the part that handles the listings (which I'm not even sure is what you mean by SHOUTcast server in this case) and is not the same as that server that provides the stream which even if you were being blocked, would still allow your DNAS to run and be accessed as long as there is a valid source connected and the stream is accessible on the internet.

so if your DNAS is being blocked from being listed in the Directory in some way then there will be a YP error message in the DNAS's log (as was asked to look at in my prior reply). if it is not due to being blocked but some other issue, then again, that will be noted in the DNAS's log.

so without knowing that actual link for the DNAS that is meant to be listed (as well as being able to actually access said DNAS), if this is something you're self-hosting or using a hosting provider and most importantly what errors, etc are being reported in the DNAS's log, i cannot help you to get back and listed (and with almost 2 weeks between replies, it makes it hard to do anything if there is an issue on our side).


and if you don't want to post information publically, plus use the support @ shoutcast . com support address and reference this thread and provide any / all applicable information so anything that is under SHOUTcast's control can be checked (which isn't a lot especially if this is all happening on a hosted setup).
DrO is offline   Reply With Quote
Old 12th March 2015, 23:19   #5
LEON GOAD
Junior Member
 
Join Date: Feb 2015
Posts: 6
SHOUTcast

sorry for not get back to you I not know the way these forms works , things work good for 10 years do not know who to talk to, i went to my internet provider they was to weeks or more getting back to me they say they can ping me at 74.95.130.121:8000 but we can not connect when they or us try to connect it pulls up a SHOUTcast site with that ip but will not connect i have seen this with my own eyes time and time again, i am told the we will need to set up a new port and let the old port go, i am try to get new equipment and new programs to put in just need the shoutcast and winamp to work for now.it would save me a lot of money, thank you for your help Leon Goad
LEON GOAD is offline   Reply With Quote
Old 12th March 2015, 23:35   #6
DrO
 
Join Date: Sep 2003
Posts: 27,873
is this a DNAS you're running on a home computer ? if yes, have you made sure that port 8000 is open on the router as well as the Operating System's Firewall ?

or are you paying someone to host it for you and you then connect the source (I assume Winamp on the post above) on a home computer to the DNAS server ?

also provide a screenshot of what you're seeing when you access that server address, as again, I cannot view anything on that address (it times out).
DrO is offline   Reply With Quote
Old 13th March 2015, 16:55   #7
LEON GOAD
Junior Member
 
Join Date: Feb 2015
Posts: 6
Shoutcast

Thank you for your help. We will check out the DNAS logs. I do know that when we connect on our server which is a commercial server (we have 3 of them-one assigned to each station on the ports 8000, 8002, and 8004 all with the same static IP) the logs immediately flash shout cast has been touched. The address for the WHHV station port 8000 that we are having trouble with is http://74.95.130.121:8000/listen.pls The other two station ports are working fine. I talked with some other network specialists. They say the same thing that my local internet providers say the port is being blocked most likely on shoutcast's end. Our server is working good. I went into my router and I connected to a computer on our internal network system. All three ports are sending out a stream to the world wide web. Like I say, it is confusing and beyond me, but I don't believe that all my sources are wrong. The problem seems to be with shoutcast connections. I am calling in two more specialists next week to make their evaluations. I already have myself and three other specialists that have made their diagnosis and they all agree. Shoutcast must fix their problem or I must do as I stated in an earlier thread. I must set up new ports and go to another program that has nothing to do with shoutcast/winamp. I'd like to stay with them for one of my stations is 30 miles away and we stream our programming to the transmitter there. Again, thank you for your help. Leon Goad
LEON GOAD is offline   Reply With Quote
Old 13th March 2015, 17:08   #8
DrO
 
Join Date: Sep 2003
Posts: 27,873
re-posting the same IP address is of no use when it is not accessible. and an internal network connection to the DNAS will most likely work, but this not the same as a public connection i.e. what I (and anyone else) are only able to do.

we [SHOUTcast] cannot fix anything if the DNAS is not accessible, especially as this seems to be pointing to nothing we'd have any control over to start with.

you keep saying it's our [SHOUTcast's] fault but when we [SHOUTcast] cannot even see the index page of your DNAS via a standard web connection, the issue pretty much has to be due to something on your side i.e. port 8000 is not open on something that you / your host / whoever is under the control off and is preventing anything from being seen.

we [SHOUTcast] cannot block access to a specific port. we can only block you from being listed in the SHOUTcast Directory. as the address you keep posting is not working, that is pretty muich pointing to a configuration issue on your side (most likely it'll be some sort of port-forwarding issue) and is not something SHOUTcast has any means to block.

also please use paragraphs in your replies, it makes it really hard to read them when it's just a wall of text.


so without providing any DNAS logs (as original requested), i'm sorry but at this point in time, there is very little that can be done to assist you with your issue (and I have to expect this is something that we [SHOUTcast] wouldn't be able to resolve anyway due to the inability to even see the DNAS to begin with).
DrO is offline   Reply With Quote
Old 13th March 2015, 21:40   #9
LEON GOAD
Junior Member
 
Join Date: Feb 2015
Posts: 6
SHOUTcast

will work on this from our end, thank you for your help had to start some were, Leon Goad
LEON GOAD is offline   Reply With Quote
Old 20th March 2015, 14:03   #10
LEON GOAD
Junior Member
 
Join Date: Feb 2015
Posts: 6
SHOUTcast

whhv not working for some time, now today our other non public not working wgfc,and our public WNLB not working all three are feeding out to the WWW from our 3 servers, need help Leon Goad
LEON GOAD is offline   Reply With Quote
Old 20th March 2015, 14:15   #11
DrO
 
Join Date: Sep 2003
Posts: 27,873
the information you need to provide has already been mentioned a number of times and still saying "it's not working" is not the way to go about getting help from anyone on here. if you really want help, then you need to provide the information that has been requested.
DrO is offline   Reply With Quote
Old 31st March 2015, 17:18   #12
mjbrown
Senior Member
 
Join Date: Aug 2001
Posts: 114
Leon,

On your computer, in Winamp, you have the SHOUTcast DSP, which is a plug-in that creates the "source stream"—that is, it takes whatever's playing and sends it over the network to the publicly accessible SHOUTcast "DNAS" server(s). Listeners connect to the DNAS servers.

The people who maintain the SHOUTcast software and who run this forum have nothing to do with this process whatsoever. The audio does not go through any computers under the control of the SHOUTcast high command. The computers and the software on them are 100% under the control of you and your hosting provider.

So when you were told the problem is "on SHOUTcast's end," what they meant was that they aren't blocking anything on their network, so maybe the computer running the DNAS has a firewall that is now blocking the port, or some other software on that computer is using that port, or the DNAS is not listening or is in a confused state. If you did as you said (you said "We will check out the DNAS logs") then maybe we would know more.

The logs will indicate whether the DNAS is even receiving the source stream, or if it starts to receive it and then disconnects, or whatever. They'll also indicate whether listener connections are failing. DrO and staff can help diagnose if you show them the logs.

Also there is a chance that your DSP is not even able to send the source stream out to the DNAS, which would mean the problem is on your computer or your local network configuration. You didn't mention anything about what is happening on your end. Is the DSP showing that is able to connect to the DNAS, or is it always Reconnecting? If you enable the connection logs in your DSP, maybe we could have a look at those, too. Also do you use a VPN, by chance?
mjbrown is offline   Reply With Quote
Reply
Go Back   Winamp & Shoutcast Forums > Shoutcast > Shoutcast Technical Support

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump