Announcement

Collapse
No announcement yet.

Salvation for the [Error syncing to stream] while tunneling

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

  • Salvation for the [Error syncing to stream] while tunneling

    Hi, I got frustrated searching for a solution for this problem here, I didn't see anything useful other than "why you wanna do that huh" and "I think the proxy is blocking winamp", well DUH I already knew that, so I solved it myself instead and figured I'd share the fun because I LOVE the Winamp community, it's that simple.

    Problem 1:
    THE corporation, with an anal content filter on their proxy, killing both music and surf for me, the busy bee employee.

    Solution:
    Port forwarding via an encrypted proxy tunnel. I'm not going to write all the details for that here, since this is Winamp.com, so I'll stay on topic for the forum. I'm assuming you have an SSH server at home, and that your're using Tunnelier or Putty to "phone home". Your tunnel works already for surfing, and I assume you're using Firefox to disable DNS leakage via about:config, but you keep getting the [Error syncing to stream] in Winamp.

    Problem 2:
    Trying to listen to aacPlus or any shoutcast streams in general from .pls files in Winamp will render an [Error syncing to stream] in Winamp, despite you having entered the correct proxy settings, as in pointing to your Tunnelier or Putty forwarding port.

    Solution:
    Since the actual problem is, that Winamp is expecting a HTTP proxy, and the ones mentioned above use SOCKS, the solution is to set up another proxy on your work computer, for example the simple, brilliant and "free for up to three users" Youngzsoft CCproxy. I use one install at home and one at work now for this to work, btw.

    So, with a working tunnel already in place, add CCproxy on work comp, with a cascading proxy setup, so it forwards to the SOCKS forwarding Tunnelier or Putty, via the CCproxy HTTP proxy port. Make sure to avoid port collisions, and to disable the HTTP forwarding in Tunnelier, just use the C2S port forward. Also make sure to use the built-in IP-masking in CCProxy so it only allows localhost IP.

    You then tell Winamp to use the CCProxy, which forwards to Tunnelier or Putty, which forwards encrypted stuff to the corporate proxy, which forwards home, which in turn hooks me up to where the fun is at.

    Yupp yupp.

    Having set up the above correctly, I now have any .pls webradio anhywhere in the world available at work. I'm also smart enough to use the aacPlus ones, for like 24-36 Kbit bandwidth, so I generate low amounts of traffic to stay under the radar.

    Oh, this also works for the dreaded WMP .asx ones, but that crappy program keeps opening the "Now playing" for the .asx files, so even though I get the stream playing, I also generate a "content denied" page from my corporation, which is conspicuous if it happends alot. If you solve that, please reply to this thread with the solution since WMP defaults to the IE settings for the "Now playing", and I need IE untouched for the internal corp stuff.

    If this helped you, I'm glad, and the beer is on me. Cheers from Sweden.

  • #2


    sounds good.

    Comment


    • #3
      Hi coderWinAmper, looks good, I'll have a go. I'm just wondering, which port do you forward to your SSH server (does it matter)?

      Cheers,
      Ken.

      Comment


      • #4
        Actually no, I'm a little more confused that I thought.

        We have a linux service here (that isn't firewalled). I can use putty to connect to that, but what do I tunnel to? Would I need another proxy running there?

        e.g.
        Winamp -> CCProxy -> putty -> Linux Proxy -> Shoutcast Servers

        Cheers,
        Ken.

        Comment


        • #5
          Basically this is what you need, if you're behind a filtering corp/uni proxy that you need to cascade through:

          Winamp -> CCProxy -> Putty -> Corp/Uni Proxy -> SSH Server at home -> Proxy at home -> Shoutcast Servers

          You can choose any ports in your own machines to forward between. The problem occurs at the corp/uni firewall, if they block certain ports (or all apart from a few). Then you'll probably neede to use specific ports like 80, 22, 23, 443 or something like that. Try any port first and then cycle through if you get dropped in Putty.

          Comment


          • #6
            There's no issue of Uni Proxy once I tunnel to linux, it connects directly to the Internet. So I think if I run a proxy there I can avoid a few steps.

            I'll have a play around.

            Cheers,
            Ken.

            Comment


            • #7
              Re: Salvation for the [Error syncing to stream] while tunneling

              Originally posted by coderWinAmper
              So, with a working tunnel already in place, add CCproxy on work comp, with a cascading proxy setup, so it forwards to the SOCKS forwarding Tunnelier or Putty, via the CCproxy HTTP proxy port. Make sure to avoid port collisions, and to disable the HTTP forwarding in Tunnelier, just use the C2S port forward. Also make sure to use the built-in IP-masking in CCProxy so it only allows localhost IP.

              You then tell Winamp to use the CCProxy, which forwards to Tunnelier or Putty, which forwards encrypted stuff to the corporate proxy, which forwards home, which in turn hooks me up to where the fun is at.
              This is exactly what I want to do. I'm just not sure I completely understand how this works. I have tunnelier working and can connect via firefox using the socks proxy 127.0.0.1:1080. I'm just not clear on how to use CCProxy. I see the cascading config and assume that I can set that to use 127.0.0.1:1080, however I'm not sure how to setup the C2S fwd. If I switch off the HTTP forward in tunnelier my browser is no longer able to connect. And, what then will be the IP:PORT (HTTP) setting for Winamp. It appears that CCProxy will forward to port 808, but is the IP still 127.0.0.1 (my head is starting to hurt).

              I apologize if this is a noob question.

              Thanks,

              Jim

              Comment


              • #8
                Hi jimwat, sorry for me not checking in here sooner to answer your question. Setting stuff like this up, is in now way intuitive, so no need to apologize for being a "noob".

                If the tunnel stops working when you disable the HTTP proxy in Tunnelier, that means that your C2S isn't properly configured as you already seem to have guessed, since the HTTP is supposed to be off (I never got the HTTP proxy to work for Winamp, it's "non-standard" or something).

                For CCProxy, under "Cascading Proxy" advanced menu tab, choose to Enable, enter 127.0.0.1 as address, protocol SOCKS5, port XYZ (XYZ is the port you set up for Tunnelier C2S, covered below) and then set Winamp to use the CCProxy HTTP port, (I think 808 is default but not sure, it proxies from that port, not to it). Ok?

                Then for Tunnelier, under "C2S Fwding", enabled, 127.0.0.1, List. Port is the same as XYZ above, preferrably something way above 1024. Destination host is "localhost" (this is what your HOME machine will proxy to, in my case another CCProxy) and Dest. Port is then the SOCKS port of your home proxy.

                If it works, cheers and you're welcome, if not, questions?

                (And again, for your safety, enable the IP filtering on your uni/work AND on your home CCProxy to only allow localhost, otherwise you open up a tunnel for anyone doing stuff through your comps, and THAT is a noob move.)

                Comment

                Working...
                X