| View previous topic :: View next topic |
| Author |
Message |
Anonymous Guest
|
Posted: Mon Oct 02, 2006 9:01 pm Post subject: Unable to resolve socket |
|
|
I'm using Icecast in combination with the Oddcast Winamp plug-in... Without my router, I can get it to run PERFECT; no issues, what-so-ever.
But, when I attach my router, Icecast will connect, but when I try to connect Oddcast to Icecast, Oddcast is unable to resolve the port.
I have ports 8000 and 8001 forwarded as recommended by portforward.com and the configuration for both Oddcast and Icecast are set to use port 8000...
And like I said, if I just dettach my router and change no settings, it works just fine... Are there any other ports I need to forward or something else getting in the way? This is obviously a router issue, but I figured someone here might know what's goin' on. |
|
| Back to top |
|
 |
Anonymous Guest
|
Posted: Thu Oct 05, 2006 2:49 am Post subject: |
|
|
| Bump. Please, I need help. |
|
| Back to top |
|
 |
karlH Code Warrior

Joined: 13 Jun 2005 Posts: 5476 Location: UK
|
Posted: Thu Oct 05, 2006 11:57 am Post subject: |
|
|
The problem is that there's not enough information being presented to know what's going on. It would indicate a network issue but you haven't said what the structure is, is it a LAN, is DHCP getting used, what IPs are being used. With the router enabled, is the router between the source client and icecast, does the browser display the status page. This is the sort of information required.
karl. |
|
| Back to top |
|
 |
Anonymous Guest
|
Posted: Thu Oct 05, 2006 6:48 pm Post subject: |
|
|
I'm using DHCP with my WAN IP on both IceCast and Oddcast. Without the router, I can reach the status page just fine. But when I connect it, Oddcast reports an inability to resolve the socket.
If I set Oddcast to localhost and Icecast to WAN, I get a connection, but I can't reach the status page. If I invert this, Oddcast can't find Icecast.
I've gone into my router and found every possible option for opening ports and opened 8000 and 8001 (suggested by portforward.com). But still nothing. The router is a D-Link 624.
I'm still continuing to attempt to resolve the issue, myself... But I'm running out of options.
Anything else I'm forgetting? |
|
| Back to top |
|
 |
karlH Code Warrior

Joined: 13 Jun 2005 Posts: 5476 Location: UK
|
Posted: Thu Oct 05, 2006 7:29 pm Post subject: |
|
|
I gather you are only concerned about the setup which includes the router. Determine the IP address of the machine running icecast, I'm assuming you intend to portforward 8000 on the router to this IP. What are your listen-socket parameters because it sounds like you are using bind-address when you should not be.
karl. |
|
| Back to top |
|
 |
Anonymous Guest
|
Posted: Sat Oct 07, 2006 4:50 am Post subject: |
|
|
I'll just post my Icecast Configuration File. Would probably help more.
| Code: |
<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>******</source-password>
<relay-password>******</relay-password>
<admin-user>admin</admin-user>
<admin-password>******</admin-password>
</authentication>
<hostname>68.51.108.95</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: Sun Oct 08, 2006 1:55 am Post subject: |
|
|
The xml looks fine, no bind-address is used so all interfaces are being listened on. Unless you have configured a firewall (which is unlikely as you have access when you remove the router) then it's probably a routing issue. As you have not described your network setup, it's hard to say anything further.
karl. |
|
| Back to top |
|
 |
Anonymous Guest
|
Posted: Sun Oct 08, 2006 4:26 am Post subject: |
|
|
| What information would be relevant to helping you help me? |
|
| Back to top |
|
 |
|