Can't Listen to My Own Radio!

[ZuluTiger]

So, I am running Shoutcast 2 on a server in my office. On the same network, I try to listen to from my personal laptop and I just get connection errors. I also can't look at the administrator settings from my personal laptop, but can do that on the server computer. So, my question is what I need to do to hear my radio on my network, which is the same connection as the server network. Listening on the phone app isn't the ideal way I was going for. :P

Thanks!

Server Computer Info:
Windows 7 32-Bit
Sam 4 Broadcasting Software
Shoutcast 2.0.11 Server

PS: What is the best way to stream directly on my website? I am not a pro coder and I just want a basic player that gives volume controls and shows current song.

Here is the station: www.FHSSTUCO.com
Click "FHS Radio"

[DrO]

if you're trying to play via the 'listen' link from the DNAS then you (or your host) have setup the 'streampath' to be the same is the listen link itself i.e. you're accessing <server>/listen.pls and the link in the pls file is <server>/listen.pls. so you need to drop the streampath entry or change it to something else.

-daz

[jaromanda]

it could also be as simple as windows firewall

[DrO]

true (or some loopback issue on the router), though i was able to hit the DNAS directly (and it plays on the site in IE) so from any external view point it seems to be fine (other than the self-looping tune-in link - probably need to add some filters to the DNAS to prevent that).

-daz

[ZuluTiger]

Thanks for the reply. So I changed the streampath and I still am just getting the page to load, favicon of shoutcast comes in, but timesout. I feel it is a loop in the router. Now I need help on that because I search google and this forum but I haven't had any luck.

Also, how or where can I find information to filter the DNS to prevent that tune in loop?

THANKS SO MUCHO!

[DrO]

Also, how or where can I find information to filter the DNS to prevent that tune in loop?

sorry, that was a comment more to myself to make sure that how you'd managed to setup the DNAS isn't able to happen again - not something you can really do anything about.

as for the page loading failure, i'm not sure as i remember one other person seeing such things but no fix ever came out from trying to resolve that (especially as i could never replicate it).

-daz