Announcement

Collapse
No announcement yet.

listen.pls wrong IP address / admin page NG

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • listen.pls wrong IP address / admin page NG

    I'm having 3 issues. I've searched the forums, and read through many threads, but I haven't found one that looks like an answer for me.

    I have Shoutcast 2 setup:


    Win XP Professional SP3 32 bit
    sc_serv.exe v2 0.0.19.0 2/25/11 (upgraded from earlier version which did the same thing)
    sc_trans.exe v2 0.0.40.0 12/14/10

    Both are on the same box, running as a service. I am using live capture on sc_trans from the sound card line in.

    Problem #1:
    The server plays from any computer on the LAN, using the local IP http://192.168.1.139:8000/listen.pls. When I test with an outside network to the public IP, http://n1bs.dyndns.ws:8000/listen.pls it does not work. Also does not work from the YP directory.

    I have port forwarding configured in the router, and dyndns is being updated with the correct public IP. Here's the twist - the listen.pls file that is being sent to external listeners has the wrong IP address in the playlist! Looking at it with a text file (again this is from an external network), I get the following:

    [playlist]
    NumberOfEntries=1
    File1=http://192.168.1.139:8000/ka1rci.mp3

    I can't really see where that gets "programmed" for the correct address.

    Problem #2:

    http://192.168.1.139:8000 brings up gibberish. Same thing happens when accessing the public IP.

    Partial paste:

    ICY 200 OK icy-notice1:
    This stream requires Winamp
    icy-notice2:SHOUTcast Distributed Network Audio Server/win32 vFeb 25 2011
    icy-name:KA1RCI Amateur Radio Network icy-genre:Misc icy-url:http://ka1rci.net content-type:audio/mpeg icy-pub:1 icy-br:48 ÿó`P.¨\¬þ––¯ëè* ´}ÛUê™/;üä3Zd%6Í‹‡Ü²LÀ‚îÊ0„§0‚E¼À îÀp~dðžù_Jù,ó™¹~ÿkåU8HŘM–¥/Š§dü*¶Û’Km üÝOOt*


    Problem #3

    My log is filled with this - YP seems to list the station OK though.

    2011-02-26 10:36:43 I msg:[YP2] Connecting to yp.shoutcast.com
    2011-02-26 10:42:11 I msg:[DST 208.20.225.130:53729 sid=1] SHOUTcast 1 client connection accepted. Mozilla/5.0
    2011-02-26 10:42:11 E msg:[DST 208.20.225.130:53729 sid=1] Socket error while waiting to send data. err=Connection reset by peer.(10054)
    2011-02-26 10:42:11 I msg:[DST 208.20.225.130:53729 sid=1] SHOUTcast 1 client connection closed (0 seconds) [Bytes: 41808] Agent: `Mozilla/5.0'
    2011-02-26 10:46:44 I msg:[YP2] Connecting to yp.shoutcast.com
    2011-02-26 10:52:11 I msg:[DST 208.20.225.130:54440 sid=1] SHOUTcast 1 client connection accepted. Mozilla/5.0
    2011-02-26 10:52:11 E msg:[DST 208.20.225.130:54440 sid=1] Socket error while waiting to send data. err=Connection reset by peer.(10054)
    2011-02-26 10:52:11 I msg:[DST 208.20.225.130:54440 sid=1] SHOUTcast 1 client connection closed (0 seconds) [Bytes: 41808] Agent: `Mozilla/5.0'

    Any ideas welcome.

    Thanks,
    Brian

  • #2
    One additional data point for problem #1:

    On the listening client, if I edit listen.pls with notepad, and replace the local IP with the public address, it works fine from external network. In this case I save listen.pls and double click it on the listening computer. Still doesn't work accessing it from the server.

    [playlist]
    NumberOfEntries=1
    File1=http://n1bs.dyndns.ws:8000/ka1rci.mp3

    Brian

    Comment


    • #3
      If your having a socket error? Either somethings running on that port, or the port above it. Make sure what ever port your running on (IE 8000) has that port open dedicated for the server and has the next ports free (8001) If your running SC_serv on 8000, this could be the issue.
      KNSJ.org 89.1 FM San Diego

      Comment


      • #4
        Regarding problem #1, I changed sc_serv.conf and sc_trans.conf to use absolute addressing rather than relative, after reading a note about that. No change.

        Does anyone know how the stream address gets loaded into listen.pls when it is generated? Why is my server plugging in the local IP address rather than the public address?

        Brian

        Comment


        • #5
          #1 - have you set destip or dstip in the config file. if so remove them. with the recent builds of the v2 DNAS, it will attempt to work out the ip / address from the connection attempt made to the listen.pls action and so fill it that way (apparently how the v1 DNAS did it from what i've been told). though there's nothing working in your posts that i can try to connect to inorder to see if my guess is correct or not.

          #2 - you need to access /index.html to get to the status page as otherwise it's trying to play the stream in the browser.

          #3 - that's from the above attempts to access the root of the stream in the browser.

          -daz
          WACUP Project <‖> "Winamp Ramblings" - Indie Winamp Dev Blog

          Comment


          • #6
            results of experimentation

            Hi Daz,

            I did not have destip or dstip in the sc_serv configuration file. I thought I would add in the WAN address as a workaround, but when I do that sc_serv service starts then stops with the following in the log:

            2011-03-01 20:17:36 I msg:<***> Logger startup
            2011-03-01 20:17:36 I msg:<***> version 0.2.0.0 build 0.0.19.0
            2011-03-01 20:17:36 D msg:<***>
            2011-03-01 20:17:36 I msg:*******************************************************************************
            2011-03-01 20:17:36 I msg:** SHOUTcast Distributed Network Audio Server (DNAS)
            2011-03-01 20:17:36 I msg:** Copyright (C) 1999-2011 Nullsoft, Inc. All Rights Reserved.
            2011-03-01 20:17:36 I msg:** Use "sc_serv filename.conf" to specify a config file.
            2011-03-01 20:17:36 I msg:*******************************************************************************
            2011-03-01 20:17:36 I msg:[SHOUTcast] DNAS/win32 v 0.2.0.0 b 0.0.19.0 (Feb 25 2011) starting up...
            2011-03-01 20:17:36 I msg:[MAIN] PID: 2120
            2011-03-01 20:17:36 I msg:[MAIN] Loaded config from c:\Program Files\SHOUTcast\sc_serv_brian.conf
            2011-03-01 20:17:36 I msg:[MAIN] Calculated CPU count is 1
            2011-03-01 20:17:36 I msg:[MAIN] Starting 1 network threads
            2011-03-01 20:17:36 I msg:[MICROSERVER] Listening for connection on port 8000
            2011-03-01 20:17:36 I msg:[MICROSERVER] Listening for connection on port 8001
            2011-03-01 20:17:36 I msg:[MICROSERVER] Listening for connection on port 8000
            2011-03-01 20:17:36 E msg:Error opening port 8000 because Could not bind to http://74.103.201.59:8000 because Address already in use.
            2011-03-01 20:17:36 I msg:[MAIN] Terminating sources
            2011-03-01 20:17:36 I msg:[MAIN] Waiting for final YP remsrvs
            2011-03-01 20:17:36 I msg:[MAIN] Runner shutdown
            2011-03-01 20:17:36 I msg:<***> Logger shutdown

            sc_serv starts OK if I comment out destip, but of course I still have the other problem. By the way, problem #2 is good with what you said, I had forgotten about that.

            Here is my config file. I have taken out the commented out lines for space. I have left the server up is you want to try again to access it. After the intro file you may hear dead air, that's normal, it's a scanner-type feed.

            Thanks for the help Daz...

            Brian


            logfile=c:\Program Files\Shoutcast\logs\logfile.log

            w3clog=c:\Program Files\Shoutcast\logs\sc_w3c.log
            banfile=c:\Program Files\Shoutcast\control\sc_serv.ban
            ripfile=c:\Program Files\Shoutcast\control\sc_serv.rip

            yp2=1

            publicserver=always
            streamauthhash=12345678901234567890

            portbase=8000

            ; manually set a destip as a workaround because DNAS is
            ; loading the wrong address into listen.pls
            destip=http://74.103.201.59

            password=fubar

            adminpassword=differentfubar

            buffertype=1
            adaptivebuffersize=5

            streamid=1
            streampath=/ka1rci.mp3




            Originally Posted by DrO View Post
            #1 - have you set destip or dstip in the config file. if so remove them. with the recent builds of the v2 DNAS, it will attempt to work out the ip / address from the connection attempt made to the listen.pls action and so fill it that way (apparently how the v1 DNAS did it from what i've been told). though there's nothing working in your posts that i can try to connect to inorder to see if my guess is correct or not.

            #2 - you need to access /index.html to get to the status page as otherwise it's trying to play the stream in the browser.

            #3 - that's from the above attempts to access the root of the stream in the browser.

            -daz

            Comment


            • #7
              that destip entry isn't right. it needs to just be the raw ip without the htp:// on the front.
              other than that, it should just be working unless something is messing around with the handling internally. will try to reproduce the issue though i've not been able to get it to fail on any of my test setups so far.

              -daz
              WACUP Project <‖> "Winamp Ramblings" - Indie Winamp Dev Blog

              Comment


              • #8
                I tried the destip entry without http://, and it did the same thing (sc_serv started then stopped). It's commented out again and the server is running now.

                Were you able to see what I was talking about with the listen.pls file?

                Thanks again,
                Brian

                Comment


                • #9
                  yeah am seeing http://192.168.1.139:8000/ka1rci.mp3 in the generated pls file. even when trying to access http://74.103.201.59:8000/listen.pls (was wondering if maybe it's something from using n1bs.dyndns.ws but doesn't seem to be) which is weird as there shouldn't be an attempt to provide a local ip when doing a remote connection.

                  at the moment i can either try to make a test build of the dnas to get a better idea of what is going on or if you've got some sort of access to the machine i could have then that will probably make it quicker for me to look into and try to see what the issue is (i.e. if it is in the DNAS or something else interfering with things).

                  -daz
                  WACUP Project <‖> "Winamp Ramblings" - Indie Winamp Dev Blog

                  Comment


                  • #10
                    Remote login

                    I'll set up a remote login for you, and I'll send you a PM. Thanks

                    Comment


                    • #11
                      SOLVED - update

                      Hi all,

                      Just an update for closure on this one. I tried the SHOUTcast installation on another computer (Win7), and it worked fine. So that ruled out router / firewall / DDNS problems.

                      At that point, since I had reinstalled the SHOUTcast components twice, I figured the problem had to be in the OS. I took the drastic step of reinstalling WinXP SP3 and rebuilding the server.

                      And the good news is: it works now. The bad news: I still don't know what the original problem was, but I don't care so much now.

                      Thanks DrO for the help.

                      Brian

                      Comment


                      • #12
                        rightio, had been wondering what was going on as things had gone quiet. i have made a few changes for the next drop to hopefully make it a bit more reliable either way though is good to know that it's otherwise working ok. will scrub it off my todo list

                        -daz
                        WACUP Project <‖> "Winamp Ramblings" - Indie Winamp Dev Blog

                        Comment


                        • #13
                          I am currently having this exact same problem right now...

                          Server is here:


                          If you open the listen.pls from the 'Listen' Link, you'll see the playlist entry it contains points to a completely different IP address than the one it should.

                          Was working fine until this morning, no idea why it picked up that random IP that it's handing out in listen.pls, it's not an IP on the server it's running on at all...

                          I just downloaded this DNAS yesterday, so it's the most current version.

                          Comment


                          • #14
                            the IP for that part is determined based on what the DNAS can work out from the request made to access it. if it was working beforehand then something external of the DNAS (possibly what it is running on or where in the network) has changed.

                            the easiest option is to specify the external IP/address using the 'destip' config option e.g. destip=radio.everfreeradio.com (or the IP of it) and see if that works as something is obviously messing with the DNAS trying to work things out now.

                            -daz
                            WACUP Project <‖> "Winamp Ramblings" - Indie Winamp Dev Blog

                            Comment


                            • #15
                              I managed to fix it by setting a dstip= as specified above, but I also had to re-specify the srcip as 127.0.0.1 (for sc_trans) or else it would try to duplicate the 5800 port on the same IP, say it cant open it twice, and crash.

                              Still very odd, no idea where it got that last IP from.

                              Comment

                              Working...
                              X