Shoutcast through VPN?

[Clifford27]

I find this rather wierd! I am able to log into other SHoutcast stations when I am logged onto my VPN for work but when I try to connect to my own Station it will not connect.

If I dissconnect my VPN I am able to log onto my station no problem.
I figured if I could get other SHoutcast stations while in VPN I would have access to my own also?
Any Ideas?

Cliffy.

[Clifford27]

This is what happens when I log into my VPN:


<01/12/03@23:42:25> [yp_tch] yp.shoutcast.com touched!
<01/12/03@23:43:26> [yp_tch] yp.shoutcast.com touched!
<01/12/03@23:44:27> [yp_tch] error connecting to yp.shoutcast.com
<01/12/03@23:45:28> [yp_tch] error connecting to yp.shoutcast.com
<01/12/03@23:46:29> [yp_tch] error connecting to yp.shoutcast.com
<01/12/03@23:47:30> [yp_tch] error connecting to yp.shoutcast.com
<01/12/03@23:48:31> [yp_tch] error connecting to yp.shoutcast.com

As you can see I am logged in fine before and then it drops the connection. Any idea? This is what happens when I log on to VPN on the Host computer.

I am guessing that is the same reason I have problems listening to my own station on other computers when logged into VPN. Still don;t understand why I can listen to other peoples staions?

Please help... Need my Music at work! hahaha

[argonaut]

It would help to know where your client is in relation to your radio station. I asume your VPN client and WinAMP stream source are *not* on the same network client (same computer), since you said you connect to your radio station. It sounds like your VPN client does not support an IPSEC feature called "split tunneling"

See this page for an example.

In other words, when you connect to your work (VPN) network, the VPN connection (VPN server) is directing all traffic on your computer through the VPN gateway then out to the internet, instead of only those networks that are inaccessable via the internet except through your VPN client. I am guessing that becuase you are sending all IP traffic through the VPN client there is some type of firewall or ACL between the VPN server and your VPN client/WinAMP client. Thus causing the shoutcast directory to not be able to connect back to your stream source, because it does not know how to get back to your client. This is all sort of confusing, I know ... Perhaps answering a few question will help me to understand your situation better. We need to know where your (1) client, (2) shoutcast server and (3) WinAMP source are, in relation to one another.

Is your Shoutcast station within your work network (the VPN network) or is it outside of you work network? In other words

Is the "host computer" the radio station? If so, is it also where you are listening from ? (I wouldn't think so). If not, is the WinAMP stream source

Can you listen to other radio stations when logged into your VPN server?

[Clifford27]

Okay from what I see it is the Port 8000 that is the problem. All of the stations that I am able to listen to when I am logged into VPN are running on Port 80.
I have changed my port to 80 iun my config and forwarded 80 and 81 in my router but I am unable to get my DNS to connect? It only likes port 8000. Any ideas on how to get it to connect using port 80 instead of port 8000?

[argonaut]

Well we now know that it is definitely a firewall/ACL issue. That is a good start.

From your latest post I can infer a few things. Please correct me if I am wrong. Your streaming server is behind a firewall and router. It is trying to connect to yp.shoutcast.com and failing because of the firewall in between your streaming server and yp.shoutcast.com. However, the aforementioned firewall allows http traffic on port 80. Which is why you can connect to streaming servers on port 80. So it sounds like we have figured out some of the picture.

Since the hostname and domain are the same for the computer regardless of which port you are running on. (host.domain.com:8000 is the same in DNS as host.domain.com:80, the port is irelevant)

I am confused when you say:

I am unable to get my DNS to connect

So my questions this time are:

• What can't connect to what?
• Are you port forwarding on your router in order to send the winamp stream via DNAS to the streaming server?
• Also, is there another webserver such as Apache, running on port 80? If so it will interfere with your streaming server. Both cannot use the same port at the same time.

[Clifford27]

Well I am just trying to run a Server off my home machine. Now my question is how do I make it run off of PORT 80?

I am not running any firewall software and have disabled the Windows XP Firewall.

The only firewall that would be present would be when I do log into my Work VPN on this home computer. But my concern is running on the Home computer and logging into VPN say from my laptop at another location. I know that stations on PORT 80 work fine. So how do I make this happen on my home computer?

[argonaut]

So, it sounds like we just need to configure your DNAS to stream on port 80 through your router?

It sounds like you are NAT'ing on your home LAN.

My only experience with streaming is with Linux and Unix, I have never done it on windows. Here goes ... in your sc_serv.conf (I think it is called sc_serv.ini on Windows), set PortBase=80 . Restart the DNAS.

Then in your router you need to configure Port Address Translation (PAT). It might be referred to as Port Forwarding, overloading, port mapping, port-level multiplexed NAT or single address NAT by your manufacturer. Configure the router to forward TCP ports 80 and 81 to your server's IP address on your home LAN. You don't need to worry about UDP.

Then when you or a listener connect to your server they will actually be connecting to your router on port 80 which will then forward that "connection" to the streaming server.

So if your router IP address 66.218.71.85 then you will connect to the stream by going to

code:
http://66.218.71.85:80 <- notice the port

or use the DNS entry if there is one.

Then try and connect. If you are on your home LAN you can use the address of the server to connect to your server real address.