DynDNS + Slim

If there's one thing I'm bad at, it's networking. Parts for my NAS are coming in tomorrow, and I was looking for a nice and simple way of setting it up just to stream my music on a remote location, not even having to tunnel NFS over SSH or anything more complicated. I ran across this: http://forum.ecoustics.com/bbs/messages/34579/138845.html It basically explains how to set up a static IP with DynDNS, have the program that auto-updates your IP, and how to install your SlimMP3 server thing.

So I did all of that. ****.homeunix.net, forwarded my router's port 9000 (apparently you have no need to open any ports on the desktop if it uses Linux), had the auto-update program running, installed and ran Squeezeslim or Slmserver or whatever the name is, and basically had everything set up as the site told me to. When I tried to connect to my ****.homeunix.net:9000 it gave me a "page not available" from a remote connection, and a seemingly infinite loading time from a local computer. Without the port at the end, it redirects me to my router from a local computer and gives me an infinite loading time from a remote location.

I'm not sure what I'm doing wrong. The thing that I've noticed that is odd is that there was no configuration for the streaming software - I just ran it in the terminal, and it said "Done". Second thing that I found odd is that it redirects me to my router (192.168.1.1) if I enter my address in a local machine. I suppose this is to be expected, but I'm not sure if my assumption is correct.

I'm using Ubuntu 8.04 64-bit, have a Linksys WRT310N, and three computers on the router. My computer's router IP address (would that be the gateway IP?) is 192.168.102, and that's the IP I have port 9000 forwarded for.

If there's any extra information needed, I'd be glad to give it. Any help is appreciated.

Thanks in advance,
Romanian

 

The port forwarding setting should be 192.168.1.102:9000. This is the way you should set it up on the router.

 

Then from the outside world you use your dyndns name:9000 to hit your server. Most routers support DynDNS, so you can have the router perform this function instead of your PC, no software required.

 

Wirelessman: That's what I've got it set as; port 9000 for both TCP and the other one, at 102.

blue68f100: I'm not sure what you mean by "have the router perform this". When I input ****.homeunix.net:9000 it cancels connection from local and has infinite loading from remote networks.

 

is the slimp3 server daemon running? run pgrep -l slim* to see if it is running.

if you are using iptables you may need to add an entry to allow port 9000 to listen. you can run netstat -paunt to see what applications are listening and on what ports.

going to address:9000 opens the music controller for slimserver. to play the music you have to add http://address:9000/stream.mp3 to an audio player.

i would test to see if your music is streaming from the pc at all by going to another pc within the network and attempting to access the control page and stream music. if that works, then move on to the port mapping.

 

Sorry, infinite loading from local and cancels from remote**.

celsdogg: That's just the thing; I don't know how to access it from another local computer. As I said, it just redirects to my router via hostname, and doesn't load via hostname:9000

As soon as I get home I'll try to see if the server daemon is running. I use IPtables, and haven't thought of opening the 9000 (I think I had it closed, though).

Thanks.

 

You said 192.168.102, I said 192.168.1.102.

 

What I was saying is to have the router preform the DynDNS function. Then do a port forward for 9000 to the IP address of the server. Then access by using mydomain:9000 from any where.