But, cannot your hosting server be changed to receive in one of those ports they support? If not, the only other solution I can think of is to install Shoutcast in your own VPS and use port 8000. That is what I do and so far haven't had any problem using Shoutcast 2. Humberto
-----Original Message----- From: Pc-audio [mailto:pc-audio-boun...@pc-audio.org] On Behalf Of Robert Doc Wright Sent: Saturday, August 02, 2014 11:46 PM To: PC Audio Discussion List Subject: Re: shoutcast I paid for a hosting service which alotted me a port on their server. Ever since the new shoutcast came out my shoutcast plugin only states that it is reconnecting. This is the same results I get with the new shoutcast plugin I dounloaded from shoutcast.com. **** If we can't look at ourselves, and ask, why? then where does the learning start? ----- Original Message ----- From: "Humberto Rodriguez" <s...@hrfinancial.com> To: "'PC Audio Discussion List'" <pc-audio@pc-audio.org> Sent: Friday, August 01, 2014 3:43 PM Subject: RE: shoutcast Is this with your own installation of Shoutcast? I mean, have you installed Shoutcast in your server, or do you use their streaming service? Is there a problem with using the ports they want? Humberto -----Original Message----- From: Pc-audio [mailto:pc-audio-boun...@pc-audio.org] On Behalf Of Robert Doc Wright Sent: Friday, August 01, 2014 5:04 PM To: PC audio discussion list. Subject: shoutcast It seems the new shoutcast owners have made changes that keeps me from being able to stream. I can no longer input the port I had been using. It now forces port 8000 or 65350. **** If we can't look at ourselves, and ask, why? then where does the learning start?
