Announcement

Collapse
No announcement yet.

Error 200 in SAM Broadcaster (encoders)

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

  • Error 200 in SAM Broadcaster (encoders)

    Dear Shoutcast,

    My friend is hosting his station on my server, he uses two ports, 8000 & 8010 for the main stream and an iPhone aac stream.

    The problem is with the port 8000, it gives him the error 'Disconnected (200)' in the encoders tab.

    I have also tried connecting with the WINAMP DSP thing and it doesn't connect.

    Attached is a picture of the admin page on port 8000. Is there anything wrong with it?

    The only thing I can see possibly wrong with it is that the incoming interface is already there, despite the server being 'down'.

    I have killed the port at least 5 times and restarted the server more. It just doesn't want to work...

    Any help?

    Jamie Skinner
    Attached Files

  • #2
    Is port 8001 open in the server firewall ?

    4 ports need to be opened
    8000-8001 and 8010-8011
    So Long, and Thanks for All the Fish.

    Comment


    • #3
      Yes, it was all working for the past 2 weeks. Just suddenly stopped today

      Comment


      • #4
        that is strange can you provide sc dnas logs from today ?
        So Long, and Thanks for All the Fish.

        Comment


        • #5
          <08/13/[email protected]:58:09> [SHOUTcast] DNAS/Linux v1.9.8 (Feb 28 2007) starting up...
          <08/13/[email protected]:58:09> [main] pid: 32551
          <08/13/[email protected]:58:09> [main] loaded config from /usr/local/shoutcast/main/sc_serv.conf
          <08/13/[email protected]:58:09> [main] initializing (usermax:200 portbase:8000)...
          <08/13/[email protected]:58:09> [main] No ban file found (sc_serv.ban)
          <08/13/[email protected]:58:09> [main] No rip file found (sc_serv.rip)
          <08/13/[email protected]:58:09> [main] opening source socket
          <08/13/[email protected]:58:09> [main] source thread starting
          <08/13/[email protected]:58:09> [source] listening for connection on port 8001
          <08/13/[email protected]:58:09> [main] opening client socket
          <08/13/[email protected]:58:09> [main] Client Stream thread [0] starting
          <08/13/[email protected]:58:09> [main] client main thread starting
          <08/13/[email protected]:06:14> [dest: 94.195.218.43] server unavailable, disconnecting
          <08/13/[email protected]:08:21> [dest: 94.195.218.43] server unavailable, disconnecting
          <08/13/[email protected]:15:55> [dest: 94.195.218.43] server unavailable, disconnecting
          <08/13/[email protected]:17:33> [SHOUTcast] DNAS/Linux v1.9.8 (Feb 28 2007) starting up...
          <08/13/[email protected]:17:33> [main] pid: 11282
          <08/13/[email protected]:17:33> [main] loaded config from /usr/local/shoutcast/main/sc_serv.conf
          <08/13/[email protected]:17:33> [main] initializing (usermax:200 portbase:8000)...
          <08/13/[email protected]:17:33> [main] No ban file found (sc_serv.ban)
          <08/13/[email protected]:17:33> [main] No rip file found (sc_serv.rip)
          <08/13/[email protected]:17:33> [main] opening source socket
          <08/13/[email protected]:17:33> [main] source thread starting
          <08/13/[email protected]:17:33> [main] opening client socket
          <08/13/[email protected]:17:33> [main] Client Stream thread [0] starting
          <08/13/[email protected]:17:33> [main] client main thread starting
          <08/13/[email protected]:17:33> [source] listening for connection on port 8001
          <08/13/[email protected]:19:17> [dest: 94.195.218.43] server unavailable, disconnecting
          <08/13/[email protected]:19:41> [dest: 84.67.159.10] server unavailable, disconnecting

          Comment


          • #6
            post or pm me the server ip address as the one in your pic does not seem to be reachable.


            ** i got out of the wrong side of the bed this morning i was trying to conect to the source ip :P:
            So Long, and Thanks for All the Fish.

            Comment


            • #7
              pmed you

              Comment


              • #8
                ok there is nothing wrong as far as i can see on your end.
                Which only leaves a client side/source problem.

                Makesure the client has not altered settings on his side esspecially the password field.
                So Long, and Thanks for All the Fish.

                Comment


                • #9
                  Hmm, the thing is I can't connect to it either...?

                  Comment


                  • #10
                    I pm'ed you,other than what i have done there is no more i can do.

                    I dont have access to the dsp plugin at this time of day
                    so i cant connect and test.
                    So Long, and Thanks for All the Fish.

                    Comment


                    • #11
                      the source of the 200 error is most commonly associated with someone else broadcasting on the stream you are trying to connect to.

                      Comment

                      Working...
                      X