| View previous topic :: View next topic |
| Author |
Message |
Chrispy61
Joined: 24 Oct 2009 Posts: 8
|
Posted: Sat Oct 24, 2009 7:41 pm Post subject: Help me? |
|
|
Hello, i was hoping sombody could help me out. Im using icecast, winamp and oddcast. The guy who helped me sort out the setting up is using an apple mac and can connect to my stream no problem but for some reason i cant get anyone else connected not even using local host? I no this guy connected because the icecast was showing one listner and he told me what song was playing. Any ideas??
Cheers |
|
| Back to top |
|
 |
karlH Code Warrior

Joined: 13 Jun 2005 Posts: 5476 Location: UK
|
Posted: Sat Oct 24, 2009 10:23 pm Post subject: |
|
|
You will need to know what the address (IP or DNS name) and port of your icecast server is. Maybe you are using <bind-address> or maybe you are in a private LAN.
karl. |
|
| Back to top |
|
 |
Chrispy61
Joined: 24 Oct 2009 Posts: 8
|
Posted: Sun Oct 25, 2009 10:07 am Post subject: |
|
|
http://chrispy61.dyndns.org:8000/stream.ogg
Thats the link i sent my friend using a mac system and he connects no problem.
I update the dyndns site with the correct ip adress as you need too which matches the one in my belkin utility. Also in the belkin utility ive got the virtual server set with 8000 port to the correct ip address.
I cant understand why mac can connect using that link at the top, even shows in icecast i have 1 listner so im assuming its to do with windows??
Thanks for the reply. |
|
| Back to top |
|
 |
karlH Code Warrior

Joined: 13 Jun 2005 Posts: 5476 Location: UK
|
Posted: Sun Oct 25, 2009 2:01 pm Post subject: |
|
|
sounds like this belkin is a NAT forwarding box, so maybe you are not forwarding all networks packets on port 8000 to icecast or maybe the machine running icecast has a firewall. If what has happened ifs that the firewall or NAT is configured to only process the address of the working machine then everyone else will have trouble.
karl. |
|
| Back to top |
|
 |
Chrispy61
Joined: 24 Oct 2009 Posts: 8
|
Posted: Sun Oct 25, 2009 3:25 pm Post subject: |
|
|
So what do i need to do?
If i open itunes on the same computer running icecast and play somthing in winamp, it wont even play on itunes. |
|
| Back to top |
|
 |
karlH Code Warrior

Joined: 13 Jun 2005 Posts: 5476 Location: UK
|
Posted: Sun Oct 25, 2009 4:34 pm Post subject: |
|
|
are you now saying it plays with winamp but not in itunes? Have you tried using a web browser to get the web page from icecast? because it sounds like the issue is basic IP handling rather than icecast. Progress can only be made if you address the points that have already been raised, you have yet to say whether bind-address is actually used for instance. All I can say is that the URL given is not accessible from here.
karl. |
|
| Back to top |
|
 |
Chrispy61
Joined: 24 Oct 2009 Posts: 8
|
Posted: Sun Oct 25, 2009 5:57 pm Post subject: |
|
|
No no im saying i cant get it to play on the same computer. Im gunna update the ip and see if you can connect again. Im using the WAN IP in the url so it would look like this http://78.145.245.164:8000/stream.ogg
So if i enter that url in a web page what should it say?? Its so frustrating when you dont no what ur doing, the guy with the mac doesnt no much about windows or he mite be able to help me. seemed like id made progress when he could listen what my stream from his side.
Cheers for trying to help karl |
|
| Back to top |
|
 |
Widgeteye
Joined: 25 Oct 2009 Posts: 8
|
Posted: Sun Oct 25, 2009 7:16 pm Post subject: |
|
|
Dude open your port 8000 on your router.
I tried both of your addresses the dyndns and the ip and both timed out. Mine did the same until I opend port 8000 on the router. _________________ Take summa dis! |
|
| Back to top |
|
 |
Chrispy61
Joined: 24 Oct 2009 Posts: 8
|
Posted: Sun Oct 25, 2009 7:42 pm Post subject: |
|
|
The port is open with ip 192.168.2.2
??? |
|
| Back to top |
|
 |
karlH Code Warrior

Joined: 13 Jun 2005 Posts: 5476 Location: UK
|
Posted: Sun Oct 25, 2009 8:55 pm Post subject: |
|
|
so you are on a private lan, 192.168.x.x and you have configured your NAT to port forward, now you need to check the details on 192.168.2.2, to see if the firewall on there will let connections on port 8000 get to icecast. Also make sure that the server does have that IP or else the NAT won't be sending it to the correct address. Then check whether you can access http://127.0.0.1 in a browser then try http://192.168.2.2 in a browser.
karl. |
|
| Back to top |
|
 |
Chrispy61
Joined: 24 Oct 2009 Posts: 8
|
Posted: Sun Oct 25, 2009 9:49 pm Post subject: |
|
|
| I get failed to connect when i try those ip adreses. No idea, ive got everything allowing port 8000 open and ip 198.168.2.2 but no joy. any1 else using belkin? Ive also got mcafee installed and im running vista. changed all that to allow port 8000 ect |
|
| Back to top |
|
 |
karlH Code Warrior

Joined: 13 Jun 2005 Posts: 5476 Location: UK
|
Posted: Mon Oct 26, 2009 1:40 am Post subject: |
|
|
I should of expanded those urls fully, http://127.0.0.1:8000/ and http://192.168.2.2:8000
If neither of those work (especially 127.0.0.1) then you need to be clear on what is in the xml and show which ports are listed in the listen state. eg netstat -tnl
karl. |
|
| Back to top |
|
 |
Chrispy61
Joined: 24 Oct 2009 Posts: 8
|
Posted: Mon Oct 26, 2009 8:39 am Post subject: |
|
|
Neither of those work still getting connection failed
<icecast>
<limits>
<clients>100</clients>
<sources>2</sources>
<threadpool>5</threadpool>
<queue-size>524288</queue-size>
<client-timeout>30</client-timeout>
<header-timeout>15</header-timeout>
<source-timeout>10</source-timeout>
<burst-on-connect>1</burst-on-connect>
<burst-size>65535</burst-size>
</limits>
<authentication>
<source-password>xxxxxx</source-password>
<relay-password>xxxxxx</relay-password>
<admin-user>admin</admin-user>
<admin-password>xxxxxx</admin-password>
</authentication>
<hostname>localhost</hostname>
<listen-socket>
<port>8000</port>
</listen-socket>
<fileserve>1</fileserve>
<paths>
<basedir>./</basedir>
<logdir>./logs</logdir>
<webroot>./web</webroot>
<adminroot>./admin</adminroot>
<alias source="/" dest="/status.xsl"/>
</paths>
<logging>
<accesslog>access.log</accesslog>
<errorlog>error.log</errorlog>
<loglevel>4</loglevel> <!-- 4 Debug, 3 Info, 2 Warn, 1 Error -->
<logsize>10000</logsize> <!-- Max size of a logfile -->
</logging>
<security>
<chroot>0</chroot>
</security>
</icecast> |
|
| Back to top |
|
 |
karlH Code Warrior

Joined: 13 Jun 2005 Posts: 5476 Location: UK
|
Posted: Mon Oct 26, 2009 1:50 pm Post subject: |
|
|
Finally, after many postings, we can now rule out a bind-address being used. The fact that at least someone can connect would indicate that the server is running but the fact that you cannot get a web connection on the very same windows box using 127.0.0.1 would mean you have some strict limits on what can actually connect through the firewall. All you need to do is make sure port 8000 is available on windows.
karl. |
|
| Back to top |
|
 |
Chrispy61
Joined: 24 Oct 2009 Posts: 8
|
Posted: Mon Oct 26, 2009 3:35 pm Post subject: |
|
|
Well thanks for trying, i tryed taking all the firewalls down but still no joy.
Probly an easy fix for sombody who nos what there doing, im usless really with technical stuff like this. Could be to do with vista or somthing having better firewalls? |
|
| Back to top |
|
 |
|