Icecast Config

Forums › Online streaming services › Icecast Config

paul151

309 posts

Ultimate Geek

Trusted

#173333 19-May-2015 21:57

Please feel free to move this thread should I be in the wrong area. I looked about the forums but could not really see anywhere else to plonk it.

Try as I may I can't seem to get an Icecast server (windows version) set up and running so that you can connect to it from the Internet.

It's running fine via internal LAN fine and can listen via windows media player. I have opened a couple of ports on my router (8000-8001) and confirmed they are open using a port checking tool. But an attempt to connect using my windows media player pointed to the url http://myipnumber:8000/stream is just not doing anything.

I wonder about the <hostname> setting and had tried myipnumber there but also no joy

It's win7 OS and I believe I have opened up access to all inbound TCP ports for the icecast.exe in the Windows Firewall also.

Does anyone have some ideas / experience in this area?

Quic "Sprinter" UFB - Ref (free setup): R338237EFDIUJ

Agency BBS | fsxNet | Agency News | Total FM

rlevis

347 posts

Ultimate Geek

#1308104 20-May-2015 02:59

I take it in your router you have forwarded port 8000 to the internal LAN IP address of the PC with Icecast operating?

Quic Broadband

Move to New Zealand's best fibre broadband service (affiliate link). Note that to use Quic Broadband you must be comfortable with configuring your own router.

paul151

309 posts

Ultimate Geek

Trusted

#1308237 20-May-2015 10:16

rlevis: I take it in your router you have forwarded port 8000 to the internal LAN IP address of the PC with Icecast operating?

Yes, it's the business model Huawei router and I have opened 8000-8001 and pointed it to the PC running the server.
When I have both ports defined in the icecast config file and then do an open port test from the WAN side it reports both ports open.
It has me stumped as I thought it would be straight forward to get an external connection.
The thing is the server should be dishing up some HTML when i point to http://myip:8000 from the internet .. and it does not.. internally it's fine and I can listen to music from the server that is being fed from another machine (source) also on the home LAN.

Hmm...

xpd

Geek @ Coastguard NZ
13691 posts

Uber Geek

Retired Mod

ID Verified

Trusted

Lifetime subscriber

#1308252 20-May-2015 10:29

I know youve said youve opened the ports in Windows Firewall, but try turning off the Windows Firewall as a test and see if any different....

Gavin / xpd / FastRaccoon / Geek of Coastguard New Zealand

LinkTree - kiwiblast.co.nz - Lego and more

Support Kiwi music! The People Black Smoke Trigger Like A Storm Devilskin

NZ GEEKS Discord______________________________

wasabi2k

2094 posts

Uber Geek

#1308326 20-May-2015 11:21

http://myip:8000

is myip your EXTERNAL ip address? You're not trying to use your LAN IP from outside?

paul151

309 posts

Ultimate Geek

Trusted

#1308347 20-May-2015 11:51

xpd: I know youve said youve opened the ports in Windows Firewall, but try turning off the Windows Firewall as a test and see if any different....

Yep will do tonight when I get home. I had thought the same thing...

paul151

309 posts

Ultimate Geek

Trusted

#1308348 20-May-2015 11:52

wasabi2k: http://myip:8000

is myip your EXTERNAL ip address? You're not trying to use your LAN IP from outside?

Yes it's placeholder text for my external IP. No 169.198.x.x for this lad :-)

paul151

309 posts

Ultimate Geek

Trusted

#1309486 21-May-2015 19:24

Update - well it seems that I had set up the port forwarding correctly after all. I did run a test by nobbling the win7 firewall and still had issues connecting.

The eureka moment came when I tried connecting via mobile not using home wifi - and with a cellular data connection all was well. I could see the server and establish an audio stream connection.

Conclusion: it's my Huawei 659b router - it does not like me trying to access open ports as an external inbound connection when I try to do so from within my home LAN. It's a PITA
I have also found if I try and telnet into my BBS using the external IP address to reach it I hit a CLI login prompt for the router and get no further. So the router grabs port 23 (in this case) and wont allow an internal LAN system to see the system it should be forwarding port traffic to.

rlevis

347 posts

Ultimate Geek

#1309618 22-May-2015 02:54

Most routers don't seem to handle routing internal connections as if they are external connections. Some do. It is a big PITA. On a PC you can try entering a DNS record in the HOSTS file.
http://www.rackspace.com/knowledge_center/article/how-do-i-modify-my-hosts-file

paul151

309 posts

Ultimate Geek

Trusted

#1309659 22-May-2015 08:26

rlevis: Most routers don't seem to handle routing internal connections as if they are external connections. Some do. It is a big PITA. On a PC you can try entering a DNS record in the HOSTS file.
http://www.rackspace.com/knowledge_center/article/how-do-i-modify-my-hosts-file

Thanks will take a look in to this :-)

Quic "Sprinter" UFB - Ref (free setup): R338237EFDIUJ

Agency BBS | fsxNet | Agency News | Total FM

wasabi2k

2094 posts

Uber Geek

#1309716 22-May-2015 10:25

paul151: Update - well it seems that I had set up the port forwarding correctly after all. I did run a test by nobbling the win7 firewall and still had issues connecting.

The eureka moment came when I tried connecting via mobile not using home wifi - and with a cellular data connection all was well. I could see the server and establish an audio stream connection.

Conclusion: it's my Huawei 659b router - it does not like me trying to access open ports as an external inbound connection when I try to do so from within my home LAN. It's a PITA
I have also found if I try and telnet into my BBS using the external IP address to reach it I hit a CLI login prompt for the router and get no further. So the router grabs port 23 (in this case) and wont allow an internal LAN system to see the system it should be forwarding port traffic to.

So you were testing using your external IP from inside your network?

Yeah that ain't going to work 9 out of 10 times.

HOSTS file will assist with name resolution, nothing more.

paul151

309 posts

Ultimate Geek

Trusted

#1309724 22-May-2015 10:38

So you were testing using your external IP from inside your network?
Yeah that ain't going to work 9 out of 10 times.

Yep, that was the issue. I used to be able to with the router I had before I recently moved to fibre... so lesson learnt.

rlevis

347 posts

Ultimate Geek

#1309958 22-May-2015 15:18

HOSTS file will assist with name resolution, nothing more.

True. It would only be useful if you have a public domain name pointing to a local server and you want to resolve it internally.