Icecast Streaming Media Server

Sains · Joined: 16 Sep 2008 Posts: 4

Hey everybody, recently I've been attempting to start a radio stream for various reasons (something to do, friends can listen in, as well as some newscasts). Knowing my luck, the problem is going to be something mediocre that I looked right over like a fool...

However, whenever somebody attempts to get into the server using their own computers, they always get the error
"Windows Media Player cannot play the file because a network error occurred. The server might not be available. Verify that you are connected to the network and that your proxy settings are correct."

I'm currently having somebody test it out in WinAMP (just got access to it, so I wasn't able to get it tested). Currently awaiting a reply, but not all of my listeners will have WinAMP and I don't think it would be fair to force people to download WinAMP just to listen to this.

I believe I've managed to get IceCast configured correctly, as well as OddCastV3 configured. I've searched Google for various answers, all of which haven't worked, searched these forums, but I wasn't able to get much fixed.

I noticed that the only way I can connect (either in my web browser, WinAMP, or WMP), I have to insert "http://localhost:8000/stream.mp3". Nothing else will work, such as replacing "localhost" with my IP address as I've seen so many times on here.

In short: Listeners cannot connect at all, but I can only connect by using "localhost" instead of my IP.

I've seen it asked previously, so I supose here is my IceCast Win32 error.log:

karlH · Code Warrior Joined: 13 Jun 2005 Posts: 5476 Location: UK

seeing that you don't have bind-address specified then the only other possibility is firewalling blocking. get the IP of the machine running icecast and from another on the LAN try to access the web pages via that http://IP:8000. If that works then access is possible on the icecast server so you then need to look at the router/NAT port forwarding setup.

karl.

Sains · Joined: 16 Sep 2008 Posts: 4

karlH · Code Warrior Joined: 13 Jun 2005 Posts: 5476 Location: UK

bind-address will only limit access, not increase it. don't use it unless you know that you need it. Any tests to be done initially should involved a browser, html pages show easily, players can have problem with codecs so go for the simple testing first.

When I say find an IP of your machine, I mean find the IP of the machine, not the IP reported by an external website, as that is telling you the external IP not the internal IP on your LAN. typically 192.168.x.x

If localhost access is working as expected then the server is running and your stream is playing ok. you need to widen the testing further by testing access from another machine within the LAN, then externally via the NAT.

karl.

Sains · Joined: 16 Sep 2008 Posts: 4

Sains · Joined: 16 Sep 2008 Posts: 4

Just searched and edited to my abilities, no luck. Listeners are still timing out when attempting to connect to the stream.

If I were to switch the stream from Icecast to Shoutcast, would I be able to still use the same links to connect, or would I need to use a different address?

Also, I know it's a double post, however editing the previous post wouldn't exactly show up as having additional info and a question.

karlH · Code Warrior Joined: 13 Jun 2005 Posts: 5476 Location: UK

I asked about testing with a browser first, if you don't want to follow instructions then how do you expect to proceed. A browser will test the connectivity, a time out in any application indicates it is not connecting at all.

If someone external to your LAN is attempting to connect to icecast then they need the correct external address, the port needs to be forwarded from the NAT and any firewalls needs to allow the connection to occur. If those are not done then you will get a timeout no matter what application is being used.

karl.