PDA

View Full Version : Connecting to Slimserver at Work



BigTony
2007-03-12, 09:03
Dear All,

Having just become a convert to SS, I also would like to listen to music at work. I have had a go browsing the forums, but I seem to have spent a good few hours and I'm not really any nearer what it is I need to do.

My Setup:

SS running on my PC at Home (Windows XP Media Center)
PC Connected to DSL router -> 8MB connection

SS runs fine in my home, all my local PC's run Softsqueeze.

I have tried to use winamp to play music via

http://My_Home_PC_IP/stream.mp3

but all I get a timeout on the connection.

If I try and look at SS from work via

http://My_Home_PC_IP:9000

I get an error Connection Refused

Things I 'think' in need to do :

Portforward 9000 (and the other port) to my router

Check blocked ports at work (22 is open 443 isn't)

I will try these things out, but is there anything else I need to do? I read about an SSH tunnel - but that kinda sounds scary.

All help appreciated

BT

4mula1
2007-03-12, 09:24
First off make sure there aren't any firewall settings that are interfering with the connection. If you have port forwarding set in your router (correctly) you either have a firewall problem or aren't allowing hosts other than localhost to connect. I don't know exactly where that setting is but somebody else will surely point you to you.

For listening to the stream.mp3 the only port you need open is 9000. Be sure to point your media player to http://your_ip_address:9000/stream.mp3 or it won't work.

If you want to setup an ssh tunnel it's not scary, but takes a little bit of work. Google for OpenSSH for Windows and you'll find what you need. There are some tutorials on how to configure it also. If you go that route install SoftSqueeze at work and stream that way through the SSH tunnel which SoftSqueeze can be configured for. That's how I do it from work...

Good luck

azinck3
2007-03-12, 09:25
Things I 'think' in need to do :

Portforward 9000 (and the other port) to my router


You're on the right track. Forward the two ports and also be sure that you're using the right ip address for your computer at home: you'll need to find your global IP address which is different from the local one you're using on your home network (if you're trying to use an address like 192.168.x.x to access your pc from work then that's not the right one).

fathom39
2007-03-12, 14:40
Remote streaming, SSH, firewall, etc... what a hassle! And nothing more than a solution looking for a problem.

Just get a portable player (or USB hard drive) and plug it into your PC or speakers at work. Side benefit: you can listen to your collection in your car on the way to work.

adamslim
2007-03-12, 16:04
Remote streaming, SSH, firewall, etc... what a hassle! And nothing more than a solution looking for a problem.

Just get a portable player (or USB hard drive) and plug it into your PC or speakers at work. Side benefit: you can listen to your collection in your car on the way to work.

The other advantage here is that it's a very nice off-site backup system!

Adam

BigTony
2007-03-13, 06:54
Thanks for all your helpful comments, but I'm still no closer to geting it to work.

I used port forwarding on my home system, for the required ports through my router. I also checked my external IP address to make sure I was trying to connect with the correct one, but I still get timed out errors.....

I use an IPod to bring music to work, but as my collection stands at near 2 TB of music, I get bored with transfering stuff on and off the Ipod all the time. (and before you ask I have about 2,000 CD's and nearly 3,000 live shows on my server).

BT

Mark Lanctot
2007-03-13, 07:01
It's down to two firewalls then: your own at home and your employers'.

Your own at home will not allow SlimServer to communicate out to the Internet without you specifically allowing it to.

And your employer's firewall often blocks the needed ports. This you can't change, you'll have to work around it. See http://forums.slimdevices.com/showthread.php?t=33402

shadowboxer
2007-03-13, 07:14
Dear All,

Having just become a convert to SS, I also would like to listen to music at work. I have had a go browsing the forums, but I seem to have spent a good few hours and I'm not really any nearer what it is I need to do.

My Setup:

SS running on my PC at Home (Windows XP Media Center)
PC Connected to DSL router -> 8MB connection

SS runs fine in my home, all my local PC's run Softsqueeze.

I have tried to use winamp to play music via

http://My_Home_PC_IP/stream.mp3

but all I get a timeout on the connection.

If I try and look at SS from work via

http://My_Home_PC_IP:9000

I get an error Connection Refused

Things I 'think' in need to do :

Portforward 9000 (and the other port) to my router

Check blocked ports at work (22 is open 443 isn't)

I will try these things out, but is there anything else I need to do? I read about an SSH tunnel - but that kinda sounds scary.

All help appreciated

BT


Just went through this process and got it working this week.

First off, you need to port forward 9000 and that other port to the ip address of the computer on your network running SS.

Second, you have to have a static IP address. And when you try to come in from the outside it is that IP address you use
http://Your_static_home_IP:9000.

If you are using a firewall on the computer that is running SS, you need to open it up ( zone alarms, put into your trusted zone, the ip address of your work and the ip addresses that hamachi uses) to the proper ip address ranges.

My companies firewall completely locked me out so I had to set up a free vpn connection using Hamachi. I am not very computer literate and the ssh tunnel thingy sounded like too much for me. Here is a recent thread I started re Hamachi and how to get it working:



http://forums.slimdevices.com/showthread.php?t=33407

The Hamachi website is: http://hamachi.cc/


good luck. It is a bit of trouble to get set up, but I really love being to access and listen to my home music library at work.

4mula1
2007-03-13, 07:15
A good step at this point may be to verify that your home network can be connected to from outside the walled garden. Try to access it from a computer that is a friend's or relative's just to make sure it does work as expected. This way you are outside of your employer's network and don't have the question mark of their firewall hanging over you.

BigTony
2007-03-13, 08:56
Thanks for the Hamachi link. I have tried that but still not joy, when I try and ping the network between my office and home, I get request timed out error.

Looks like my office firewall has the better of me.

Cheers

BT

Mark Lanctot
2007-03-13, 09:05
Thanks for the Hamachi link. I have tried that but still not joy, when I try and ping the network between my office and home, I get request timed out error.

Looks like my office firewall has the better of me.

Cheers

BT

I thought Hamachi works over port 80, i.e. if you can see this web page you can use Hamachi? Not 100% sure but ports don't seem to be an issue with Hamachi. Did you see shadowboxer's thread? It contains a Hamachi fix you can try.

Does your home SlimServer have full Internet access on your home PC? You avoided that question earlier.

BigTony
2007-03-13, 09:12
'Does your home SlimServer have full Internet access on your home PC? You avoided that question earlier.'

erm .. not sure what the answer is ... how do I check this?

I forwarded the ports on my router (3483 and 9000)

I can use the server from within my home network, but I've not tried to access it from outside..
Humm, do I need to use

http://My_External_IP:9000/ on a PC at home to see if I can see the server from the outside..

Will look into the hamachi thread to see if I can figure out why I can't connect my 2 PC's to the same network.


I wonder how much time is lost trying to work around stuff that work sets up to block you doing the things you would other wise get sorted out in 30 seconds and be back ready to work?

BT

Mark Lanctot
2007-03-13, 10:19
Humm, do I need to use

http://My_External_IP:9000/ on a PC at home to see if I can see the server from the outside..

That kind of "loopback" doesn't usually work.

Here's something that's easier to try: play Internet radio through SlimServer. If you can play Internet radio through SlimServer, SlimServer has incoming access, which usually means it has outgoing access on most home firewalls.

shadowboxer
2007-03-13, 10:37
Thanks for the Hamachi link. I have tried that but still not joy, when I try and ping the network between my office and home, I get request timed out error.

Looks like my office firewall has the better of me.

Cheers

BT

BigTony:

You have hamachi installed both at home on the computer running and on your work computer, right? And, when you open or "power up" your Hamchi network between the two computers, do you get a "green" dot on the hamachi interface? (this means a solid connection is established)

Are you pinging via the built-in hamachi pinger or a comman line interface? what ip are you pinging?

peter
2007-03-13, 11:50
shadowboxer wrote:
> BigTony;187328 Wrote:
>
>> Dear All,
>>
>> Having just become a convert to SS, I also would like to listen to
>> music at work. I have had a go browsing the forums, but I seem to have
>> spent a good few hours and I'm not really any nearer what it is I need
>> to do.
>>
>> My Setup:
>>
>> SS running on my PC at Home (Windows XP Media Center)
>> PC Connected to DSL router -> 8MB connection
>>
>> SS runs fine in my home, all my local PC's run Softsqueeze.
>>
>> I have tried to use winamp to play music via
>>
>> http://My_Home_PC_IP/stream.mp3
>>
>> but all I get a timeout on the connection.
>>
>> If I try and look at SS from work via
>>
>> http://My_Home_PC_IP:9000
>>
>> I get an error Connection Refused
>>
>> Things I 'think' in need to do :
>>
>> Portforward 9000 (and the other port) to my router
>>
>> Check blocked ports at work (22 is open 443 isn't)
>>
>> I will try these things out, but is there anything else I need to do? I
>> read about an SSH tunnel - but that kinda sounds scary.
>>
>> All help appreciated
>>
>> BT
>>
>
>
> Just went through this process and got it working this week.
>
> First off, you need to port forward 9000 and that other port to the ip
> address of the computer on your network running SS.
>
> Second, you have to have a static IP address. And when you try to come
> in from the outside it is that IP address you use
> http://Your_static_home_IP:9000.
>
> If you are using a firewall on the computer that is running SS, you
> need to open it up ( zone alarms, put into your trusted zone, the ip
> address of your work and the ip addresses that hamachi uses) to the
> proper ip address ranges.
>
> My companies firewall completely locked me out so I had to set up a
> free vpn connection using Hamachi. I am not very computer literate and
> the ssh tunnel thingy sounded like too much for me. Here is a recent
> thread I started re Hamachi and how to get it working:
>
>
>
> http://forums.slimdevices.com/showthread.php?t=33407
>
> The Hamachi website is: http://hamachi.cc/
>
>
> good luck. It is a bit of trouble to get set up, but I really love
> being to access and listen to my home music library at work.
>

Hamachi is cool, it they couldn't penetrate my office firewall (udp
block => yellow led). Hamachi only works over udp. I ended up using
OpenVPN in tcp mode, but you need to be well versed at networking and
stuff to install that (unlike Hamachi).

In another thread I thought of a good way to test outgoing tcp access
from inside an office LAN. Fastmail, my mail provider has a 'proxy' type
of server that listens to all ports from 0 to 65535. So to test if you
company lets you set up connections, try (from a cmd.exe prompt):

telnet pop.proxy.fastmail.fm 22
telnet pop.proxy.fastmail.fm 80
telnet pop.proxy.fastmail.fm 110
etc...

If you get a POP3 prompt the outgoing port is open and you can open that
port on your home router and see if you can get things to work. If you
don't get a POP3 prompt, don't bother with the router, it won't work anyway.

Regards,
Peter

chris.mason
2007-03-15, 06:48
This sounds like its getting increasingly complicated...

Work firewall issues aside, all you should need to do to allow audio streaming remotely (from your home slimserver to you at work) is this:

1. Configure your router firewall to forward incoming TCP port 9000 traffic to port 9000 on the PC running SlimServer.

2. Check your slimserver configuration via the SlimServer web page. Go to Home / Server Settings / Security. Check if Block Incoming Connections is set to "Block" or "Do Not Block". Set it to "Do Not Block".

3. Determine your Home internet facing IP address. You can get this information from your router.

4. Open your media player, and point it at http://<your home ip address>:9000/steam.mp3

My recommendation though is that you DO NOT do this. You are opening up yourself to a host of security issues. You could make this configuration more secure by giving SLimServer a password, and by restricted connections to SlimServer to the IP address you are coming from at work, but thats not straight forward, as your work IP address is likely to change.

What I would suggest you do, given the above, and the added complication of the firewall you will have at work, is to use SSH. I do this, and have done for a while. It works flawlessly, means you can get by the firewall issues, and means you only need to forward port 22 on your router, meaning your home network is much more secure.

Go to http://pigtail.net/LRP/printsrv/cygwin-sshd.html and follow the instructions there - don't be put off by the apparent complexity, it is in fact quite straight forward. You install cygwin, with the OpenSSH server package, and reboot. Then you need an ssh client for work (such as Putty), that is also straight forward.

You need to forward port 22 from the internet to your PC.

From work, you would then open an SSH tunnel using the following command (but you'll probably be using a Windows based client, such as Putty):

ssh username@ipaddress -L 9000:localhost:9000 -f -N

Then you can start streaming. Point your media player to this URL:

http://localhost:9000/stream.mp3

and bob's your uncle.

To get access to the SlimServer web interface, use this URL:

http://localhost:9000

One other thing, if you have a dynamically allocated internet address (as most of us do) from your ISP, that isn't a problem - use a dynamic DNS resolution service - I has www.dyndns.org. Its free. You pick a domain name (e.g. fredsmith.homeip.net), and type in the IP address you have. Its likely that your router supports services like DynDns, so you then put your DynDns details in the router, and when your IP address changes, it updates DynDNS with the new address. You then use your domain name instead of the IP address to connect to home.

Works for me...very well.

I'm happy to explain more if there are parts to this that aren't clear.

Chris.

azinck3
2007-03-15, 07:08
Good, comprehensive description, Chris. Two small things to add:



4. Open your media player, and point it at http://<your home ip address>:9000/steam.mp3

there's a typo there, it should be "stream.mp3"

Also, to use softsqueeze rather than stream.mp3 (you want to use softsqueeze, trust me, stream.mp3 is a strange and horrible beast) you'll need to follow Chris' instructions but *also* forward port 3483.

BigTony
2007-03-15, 07:20
Many thanks for all your helpful comments and suggestions.

Having now tried everything apart for SSH tunnel, it looks like a tunnel is required. I have no joy with anything so far, always getting the same 'connection timed out' problem.

I did get a hamachi connection to link my home to work pc, but was unable to get any connection to my home SS at all. (seems Hamachi was having a bad day when I tried to set it up). By this I mean using the Hamachi IP and the :9000 I couldn't conenct to anything.

I have forwared ports 9000 and 3483 on my router, and I can listen to internet radion on SS at home.

I was thinking that as I live about 500 meters from where I work that maybe I should just big some very big speakers at home and crank the volume up :-)

chris.mason
2007-03-15, 07:26
Good, comprehensive description, Chris. Two small things to add:



there's a typo there, it should be "stream.mp3"

Also, to use softsqueeze rather than stream.mp3 (you want to use softsqueeze, trust me, stream.mp3 is a strange and horrible beast) you'll need to follow Chris' instructions but *also* forward port 3483.

Thanks! You'd definitely run into problems trying to connect to 'steam.mp3'! And as you say, you'd definately want to open 3483 if you want to use SoftSqueeze. Again this is also possible via SSH.

Aha, in fact I've just remembered that SoftSqueeze has SSH built in, so you would need a separate SSH client. However, its straight forward if you did use an SSH client with softsqueeze. Your SSH client connect command which look like this:

ssh username@hostname -L 9000:localhost:9000 -L 3483:localhost:3483 -N -f

(which means forward ports 9000 and 3483 from "me" through the ssh tunnel to "hostname". (if you are interested, -N means don't open a shell terminal, and -f means fork the process to the background...)

Could you elaborate on why stream.mp3 is strange and/or horrible? I steam internet radio (typically shoutcast and lastfm stuff), and my music via mp3 to work. I usually throttle it to 160kb so as not to affect my home upload bandwidth (other people at home use the PC ya see), and it works fine for the most part. All my music is FLAC, btw.

I have used SoftSqueeze, and it is a great way to listen to your FLAC files, but thats not always a good idea when listening remotely! I've also had various lock-ups with SQ, but then I'm running it on Solaris..!

azinck3
2007-03-15, 07:44
Could you elaborate on why stream.mp3 is strange and/or horrible? I steam internet radio (typically shoutcast and lastfm stuff), and my music via mp3 to work. I usually throttle it to 160kb so as not to affect my home upload bandwidth (other people at home use the PC ya see), and it works fine for the most part. All my music is FLAC, btw.

I have used SoftSqueeze, and it is a great way to listen to your FLAC files, but thats not always a good idea when listening remotely! I've also had various lock-ups with SQ, but then I'm running it on Solaris..!

I'm surprised you haven't run into the awkwardness of stream.mp3. Perhaps some streaming clients work better than others.

This is why I don't like it:

1) Setting bitrate limiting for the first time is a little strange. You have to connect to your server, then set limiting, but depending on how long it took you to do that you may have already buffered a fair amount of silence and it seems like I always have to disconnect then reconnect to the stream to get the lower bitrate.

2) The silence stream in older versions of slimserver was always delivered at some ridiculously high bitrate like 320kbps. This was awkward as you kept stopping and rebuffering silence and it would also starve your upload bandwidth of your home connection while you were trying to use the web interface to cue up your playlist. I think this has now been fixed.

3) By far the biggest problem is how far ahead the mp3 playback software buffers! I don't know if different playback clients might work better than others but what tends to happen is that, after just a few minutes of listening, I've buffered half my playlist. So if I try to interact with slimserver to control my playback in any way the effects of the inputs aren't heard for sometimes 10 minutes or more. So, changing tracks means (1) clicking the song I want to listen to in the playlist (2) disconnecting my mp3 client from the stream (3) reconnecting my mp3 client to the stream (and in the process I've missed the beginning of the song).

Anyhow, this isn't meant to be a rant against the failures of stream.mp3 - most of these are intrinsic to the unidirectional nature of the stream and I like the fact that at least the option is there to use it. And none of this is a big deal because softsqueeze works nearly perfectly. I try to urge users towards softsqueeze as much as possible because I've seen too many new slimserver users who just casually wanted to try it out and end up disappointed merely due to the limitations of stream.mp3.

azinck3
2007-03-15, 07:49
I have forwared ports 9000 and 3483 on my router, and I can listen to internet radion on SS at home.

To be clear, port forwarding doesn't really have any bearing on your access to slimserver within your own LAN. The port forwarding you've set up is what allows devices on the WAN (the internet) to talk directly to your slimserver pc. Can you get a friend to try accessing your slimserver via port 9000 just to be sure you have the forwarding set up properly?

BigTony
2007-03-15, 08:17
I can access my PC from a wirless acess point (so not from my home network).

Anyways - just to add to the fun I have Actually Got It To Work :-)

I resorted to SSH tunnel - wasn't to tricky to setup.
However, music is choppy as hell ... do I need to flip some valves on SS on my home pc? I made the buffer as big as a house on this side, and if I pause for a few mins I can get maybe a minute of nice mucis , then the chop sets in? Get the same problem from MP3, ITunes and FLAC encoded files.

Cheers

BT

azinck3
2007-03-15, 08:30
I can access my PC from a wirless acess point (so not from my home network).

Anyways - just to add to the fun I have Actually Got It To Work :-)

I resorted to SSH tunnel - wasn't to tricky to setup.
However, music is choppy as hell ... do I need to flip some valves on SS on my home pc? I made the buffer as big as a house on this side, and if I pause for a few mins I can get maybe a minute of nice mucis , then the chop sets in? Get the same problem from MP3, ITunes and FLAC encoded files.

Cheers

BT


Great! You need to turn on bitrate limiting. If you go to your slimserver web page you should see your new player listed on the left. Click it to edit the player settings. Go to the "audio" settings. Turn bitrate limiting down to 128kbps or something like that...whatever works well for you. Note that you'll need to have lame in the slimserver bin directory on your server computer for this to work.

nicketynick
2007-03-15, 08:33
Way to go Big Tony! Which set of directions did you use to set up SSH? As much as chris.mason assures us its straightforward, I'm still intimidated - it looks like the kind of thing where I could manage to irreparably break something, and lose all functionality!

shadowboxer
2007-03-15, 08:41
Way to go Big Tony! Which set of directions did you use to set up SSH? As much as chris.mason assures us its straightforward, I'm still intimidated - it looks like the kind of thing where I could manage to irreparably break something, and lose all functionality!

I second that request! I have hamachi working most of the time. Wondering if ssh would be effective and would love to know where and which ssh program you downloaded.

thanks in advance

dale

chris.mason
2007-03-15, 08:44
I second that request! I have hamachi working most of the time. Wondering if ssh would be effective and would love to know where and which ssh program you downloaded.

thanks in advance

dale

It is straight forward, honest! Would I lie to you..? ;-) I think a laymans write-up of the process would be a great idea though.

shadowboxer
2007-03-15, 08:47
Great! You need to turn on bitrate limiting. If you go to your slimserver web page you should see your new player listed on the left. Click it to edit the player settings. Go to the "audio" settings. Turn bitrate limiting down to 128kbps or something like that...whatever works well for you. Note that you'll need to have lame in the slimserver bin directory on your server computer for this to work.

And don't forget, to bitrate limit, you have to install LAME on your system....

Got hamachi working today, my biggest problem was getting zone alarms to let hamachi through. Got that working. Bit rate limited to 128kps and streaming smoothly. Still thinking about trying the ssh tunnel method. Guess I should just give it a shot and see what happens.....

chris.mason
2007-03-15, 08:57
I'm surprised you haven't run into the awkwardness of stream.mp3. Perhaps some streaming clients work better than others.

This is why I don't like it:

1) Setting bitrate limiting for the first time is a little strange. You have to connect to your server, then set limiting, but depending on how long it took you to do that you may have already buffered a fair amount of silence and it seems like I always have to disconnect then reconnect to the stream to get the lower bitrate.

2) The silence stream in older versions of slimserver was always delivered at some ridiculously high bitrate like 320kbps. This was awkward as you kept stopping and rebuffering silence and it would also starve your upload bandwidth of your home connection while you were trying to use the web interface to cue up your playlist. I think this has now been fixed.

3) By far the biggest problem is how far ahead the mp3 playback software buffers! I don't know if different playback clients might work better than others but what tends to happen is that, after just a few minutes of listening, I've buffered half my playlist. So if I try to interact with slimserver to control my playback in any way the effects of the inputs aren't heard for sometimes 10 minutes or more. So, changing tracks means (1) clicking the song I want to listen to in the playlist (2) disconnecting my mp3 client from the stream (3) reconnecting my mp3 client to the stream (and in the process I've missed the beginning of the song).

Anyhow, this isn't meant to be a rant against the failures of stream.mp3 - most of these are intrinsic to the unidirectional nature of the stream and I like the fact that at least the option is there to use it. And none of this is a big deal because softsqueeze works nearly perfectly. I try to urge users towards softsqueeze as much as possible because I've seen too many new slimserver users who just casually wanted to try it out and end up disappointed merely due to the limitations of stream.mp3.

Ah, I can see why you don't like it....!
for 1), I've not really found that a problem. I set the bitrate limit, and reconnect my media player (I use XMMS).

I've not noticed 2) to be a problem, perhaps I've lucky (I'm running SlimServer 6.5.2)

I'm amazed about 3) - I've not come across this before. Typically XMMS buffers a few seconds, and thats it. When I make changes in the Slim UI, it therefore takes a few seconds for changes to become apparent. Not perfect but I don't mind.

My feeling about streaming is that it is an entirely sub-optimal way of listening to my music, but as my normal mode is FLAC files streamed to my SB3 at home, and normally I wouldn't get to listen to my music at work, I'm OK with putting up with the inadequacies. Beats having to load up my 256k MP3 player!

BigTony
2007-03-15, 09:46
Well I really must give a big thank you to everyone thats helped me to finally get music streaming here in my office .. now I can happily listen to Zappa all day :-)

I just hope that the IT wrecking crew don't start poking about and tell me to switch it all off.

A few points that were not clear when I started this adventure, that did cause me some confusion, so I guess I'll share them here to help others that might try this route.

1) To view your home SlimServer via your tunnel or VPN, TURN off local proxy or such like settings, that sure did waste a few hours of my time. Not sure how I can switch them on/off in IE, but when the system is set up and running you don't need to log onto SS as much.

2) Make sure you actually read the IP of you SlimServer on your home network, I assumed that it was X.X.X.1, but as it turned out it was setup on X.X.X.3 - I should have spotted that sooner, but I don't really understand the wierdness of networks or routers.

3) Load LAME.exe and LAME.DLL into
program files\slimserver\server\bin BEFORE you head back to work and trying to stream ... (I must have walked the 500 meters between my office and home 10 times trying to set this up.)

4) When adjusting you bitrate settings, I found I needed to close SoftSqueeze down to make the settings take effect. Couldn't get any headway without a shutdown.

5) If you can't get onto http://HOME_PC:9000 straight away - don't muck about - go for a SSH tunnel, it works and it was the easiest of the options I've had to setup this week (took about an hour)

All I need to do now is tag about 1,000 live shows ... and also pray that my misses has actually bought me a SB3 for my birthday (which is this weekend) as I can't tell you how many helpful hints I've dropped this last 2 weeks :-)

BT

BTW (little plug) check out www.zappateers.com - trust me!

nicketynick
2007-03-15, 09:58
5) If you can't get onto http://HOME_PC:9000 straight away - don't muck about - go for a SSH tunnel, it works and it was the easiest of the options I've had to setup this week (took about an hour)



So I take it you used the instructions chris.mason pointed to for setting up the SSH tunnel?

BigTony
2007-03-15, 10:30
Yes, that and a tutorial I was also pointed to, but it was really quite easy on windows XP.

Cheers

BT

shadowboxer
2007-03-15, 11:46
To view your home SlimServer via your tunnel or VPN, TURN off local proxy or such like settings, that sure did waste a few hours of my time. Not sure how I can switch them on/off in IE, but when the system is set up and running you don't need to log onto SS as much.

Someone on this forum helped me with that issue, same thing happens with Hamachi (which is still working for me, but I want to try the ssh tunnel thing since that way I don't have to depend on Hamachi for my connection)

It is easy to switch off in IE:
Go to Tools: Internet Options: Connections: Lan Settings: and then uncheck the "Use a Proxy Server for your LAN"

Dale

chris.mason
2007-03-15, 13:26
Very glad that you've got this working!

I feel I should stress though that you should really avoid opening your slimserver directly to the world through ports 9000 and 3483. It presents a security risk. Using SSH (or VPN) is a much safer approach.

agentsmith
2007-03-15, 19:48
Is there anyway to have a squeezebox directly accessing a remote slimserver using Hamachi?

azinck3
2007-03-15, 20:00
Is there anyway to have a squeezebox directly accessing a remote slimserver using Hamachi?

No, you have to go through a proxy of some sort because the SB can't do the encryption.

BigTony
2007-03-19, 03:03
Well now I am Mr Happy - I recieved my SB3 on Sunday (Thank You Her Indoors) so now I have to work on sorting all my tag info out, whilst listening at home and work.

Oh great Joy :-)

BT

Sike
2007-03-21, 10:24
What would be great if you could open a port on your router and ten connect a Squeezebox from work by just entering the mysqbox.dyndns.com in the squeezebox and log in using a pre defined Username/password...

Just imagane being able to set up a squeezebox connected to your music collection from anywhere with WLAN...

But dare i dream?

MrSinatra
2007-03-21, 13:22
i have mentioned this before, but i really would appreciate it if SD would create a way for me locally to control and configure SS's public face...

in that way, i could set the bitrate, give them the skin i want them to see, and simply let the person connect to the addy i give them, and either pgm SS for them or let them browse the music.

its VERY confusing the way it is now.

azinck3
2007-03-21, 13:39
i have mentioned this before, but i really would appreciate it if SD would create a way for me locally to control and configure SS's public face...

in that way, i could set the bitrate, give them the skin i want them to see, and simply let the person connect to the addy i give them, and either pgm SS for them or let them browse the music.

its VERY confusing the way it is now.

I don't really understand your request. I think that's because I don't understand the use case here...why are these random people connecting to your copy of slimserver?

MrSinatra
2007-03-21, 14:13
I don't really understand your request. I think that's because I don't understand the use case here...why are these random people connecting to your copy of slimserver?

ok, let me explain, it isn't "random" people, its friends or people i want to show it to, but it COULD be random people if i wanted it to be...

the way i understand SS to work, is that it uses "sessions" kinda like XP does.

so i could be sitting here locally listening to whatever i want, and someone else from the net could at the same time reach my SS and listen to what they wanted to. i don't know how many remote sessions it allows, but i gather its more than one, yes?

in any case, thats all fine and dandy AS LONG AS the person remoting to your SS knows how to use SS.

that of course is a qualification most people find hard to earn, esp if they don't own a SB.

so what i would like to do, is still allow those unique remote sessions, but at the same time on a different port, setup a SS "public" type access window that i have already configured locally to the right bitrate, quality, skin, etc... (in other words, i control their SS session and settings)

ideally, it would include the link to connect ones software player to, AND it would be toggle-able to remote-user music controlled, or "DJ" mode where the local SS owner could set the music programming.

does this make more sense?

MillmoorRon
2007-03-21, 14:33
Have you considered launching a pirate radio station but only telling your mates?

azinck3
2007-03-21, 15:01
ok, let me explain, it isn't "random" people, its friends or people i want to show it to, but it COULD be random people if i wanted it to be...

the way i understand SS to work, is that it uses "sessions" kinda like XP does.

so i could be sitting here locally listening to whatever i want, and someone else from the net could at the same time reach my SS and listen to what they wanted to. i don't know how many remote sessions it allows, but i gather its more than one, yes?

in any case, thats all fine and dandy AS LONG AS the person remoting to your SS knows how to use SS.

that of course is a qualification most people find hard to earn, esp if they don't own a SB.

so what i would like to do, is still allow those unique remote sessions, but at the same time on a different port, setup a SS "public" type access window that i have already configured locally to the right bitrate, quality, skin, etc... (in other words, i control their SS session and settings)

ideally, it would include the link to connect ones software player to, AND it would be toggle-able to remote-user music controlled, or "DJ" mode where the local SS owner could set the music programming.

does this make more sense?

This sort of functionality is well outside the design parameters of slimserver which is designed to serve and support slim devices' hardware (SB/transporter) so it's not terribly surprising that such functionality hasn't been built in. It seems a bit beside the point to complain that it's "VERY confusing" when it's not at all what the system was designed for.

Slimserver doesn't use "sessions" (which is specific terminology in web software) in the way you mean and the ability for stream.mp3 to support multiple players is extremely limited if not nonexistent (do some searching...there's a good deal of discussion on the issue and the last I saw was that it's essentially not possible -- the type of streaming necessary to run what is essentially a radio station from slimserver is not built in).

What you suggest fundamentally differs from the SS paradigm. In Slimserver, players (hardware, software or mp3) do not equate to viewers. That's one of many things that make SS really good at what it's designed for but not so good for what you want to do.

Indeed, there are a number of other products out there that do what you want to do much better than slimserver. Take a look at Jinzora, for one. But there are many, many others with slight differences in their capabilities.

Robin Bowes
2007-03-21, 15:02
MrSinatra wrote:

>
> does this make more sense?
>

It explains what your particular use-case is.

However, Slimserver isn't designed to do what you want it to do, which
is why you consider it confusing.

R.

MrSinatra
2007-03-21, 15:24
This sort of functionality is well outside the design parameters of slimserver which is designed to serve and support slim devices' hardware (SB/transporter)

THEY are the ones who put the ability to stream a stream to someone on the net, including supporting a software player. they advertise this ability.

this wasn't some after-thought, they wanted it in there, and all i'm asking for is this functionality be made easier to use.

its not that big a stretch...


so it's not terribly surprising that such functionality hasn't been built in. It seems a bit beside the point to complain that it's "VERY confusing" when it's not at all what the system was designed for.

simply not true. they put it [some functionality] in there. the problem is that it doesn't work well, not that it isn't supposed to be there.

and it is very confusing.


Slimserver doesn't use "sessions" (which is specific terminology in web software) in the way you mean

i can't speak to that specifically, but is it not true that in theory the way it works is that multiple people from the net can reach my SS and tell it to do things that won't impact me locally, or interfere with each other? (such as the settings or what music to play) i realize in practice its probably problematic, but thats exactly what i'm complaining about.

anyway, thats what i meant by sessions.

i don't know if stream.mp3 allows more than one player to connect to it or not, does it?

i guess i figured each session would have its own stream.mp3, but i guess thats not the case...


and the ability for stream.mp3 to support multiple players is extremely limited if not nonexistent (do some searching...there's a good deal of discussion on the issue and the last I saw was that it's essentially not possible -- the type of streaming necessary to run what is essentially a radio station from slimserver is not built in).

ok, i understand what you are saying, but actually what i was thinking, (and as i just said, i guess its not like this) is that each session connecting to SS would have its own 'stream.mp3' unique to it. i think it could be done, the Q is how would you IP address it?


What you suggest fundamentally differs from the SS paradigm. In Slimserver, players (hardware, software or mp3) do not equate to viewers. That's one of many things that make SS really good at what it's designed for but not so good for what you want to do.

i understand that listening via the net to SS is secondary, but it is something they put in there.

allow me to restate my request entriely, and tell me if this is something not "too far" from SS now:

i would like the ability to control locally the skin and the settings (like bitrate limiting) for any single remote user who happens to listen to my SS.

as it is now, i can't do that. only the remote user can do it, and its hard for a novice to configure.

thats a much more limited request, and not too far from current SS implementation, is it?

azinck3
2007-03-21, 15:39
I didn't really explain one of the things I said very well:

Slimserver does not associate a particular viewer with a particular player. All viewers (and yes, there can be an unlimited number of viewers -- all you're doing is making page requests) are "peers" who have full access to all of slimserver and slimserver has no knowledge of them corresponding to any particular players. All players are peers and can be equally controlled by any viewer.

Viewer settings are mostly global and they reside in "server settings" (the ability to specify skins and default players through the URL are pretty much the only non-global "settings" available to viewers).

Global player settings are maintained in "server settings" while individual player settings are maintained in the "player settings" for a particular player.

There is no settings "overlap"...that is, none that correspond to both a particular viewer AND a particular player, which is basically what you're trying to do. There are so many differences between what you want to do and the way SS behaves that it would take quite a while to outline them all, but suffice it to say that it's not a trivial change.

azinck3
2007-03-21, 15:45
allow me to restate my request entriely, and tell me if this is something not "too far" from SS now:

i would like the ability to control locally the skin and the settings (like bitrate limiting) for any single remote user who happens to listen to my SS.

as it is now, i can't do that. only the remote user can do it, and its hard for a novice to configure.


You can actually do both these things. If you want them to use a specific skin then just give them a url with the name of the skin appended like so: http://yourserverip:9000/fishbone/

If you want to limit the bitrate then you can adjust bitrate limiting via slimserver just as well as they can. You just adjust it in the player settings for their player (it will be listed with an IP address)--you have the same control over everything as they do. Alternatively (and more simply), just have them connect to a url that specifies the bitrate: ttp://yourserverip:9000/stream.mp3?bitrate=128

Robin Bowes
2007-03-21, 15:45
MrSinatra wrote:

> i would like the ability to control locally the skin and the settings
> (like bitrate limiting) for any single remote user who happens to
> listen to my SS.

That's a reasonable request - others have asked for similar things. Try
searching enhancement requests or raising a new one.

R.

nicketynick
2007-03-22, 05:36
Wouldn't it just be easier to use SoftSqueeze? Once the player is connected to SS, you could adjust whatever settings for that player/ip, and they could browse/listen to your music as though they were sitting in your living room. Why should they even use the SS Web UI?

azinck3
2007-03-22, 05:44
Wouldn't it just be easier to use SoftSqueeze? Once the player is connected to SS, you could adjust whatever settings for that player/ip, and they could browse/listen to your music as though they were sitting in your living room. Why should they even use the SS Web UI?

That's mostly true, but I assumed that with MrSinatra's emphasis on "simple" that he wouldn't want to force people to install a new piece of software or learn how to use softsqueeze (after all, if Slimserver's too complex for these users then who's to say softsqueeze isn't too complex). Also, there are many player settings (including bitrate limiting) that cannot be modified via the squeezebox/softsqueeze and must be changed via the web interface.

nicketynick
2007-03-22, 05:52
That's mostly true, but I assumed that with MrSinatra's emphasis on "simple" that he wouldn't want to force people to install a new piece of software or learn how to use softsqueeze (after all, if Slimserver's too complex for these users then who's to say softsqueeze isn't too complex).
SS Web UI has way too many menus and esoteric settings for a non-user, but I would think anybody who can open a browser can get softsqueeze working easily.

Also, there are many player settings (including bitrate limiting) that cannot be modified via the squeezebox/softsqueeze and must be changed via the web interface.
That's the point - all the nit-picky stuff can be set by whoever is 'controlling' the server!

azinck3
2007-03-22, 05:58
That's the point - all the nit-picky stuff can be set by whoever is 'controlling' the server!

This is no less true with mp3 streaming.

But I'm not trying to argue with you. I agree than softsqueeze is far better than mp3 streaming. I was just entertaining MrSinatra's idea and trying to play by what I imagined his restrictions were...sorry this got into what seems like a debate. Your suggestion that he use softsqueeze is certainly a good one and I agree, it shouldn't be too hard for him to help his friends download it.

nicketynick
2007-03-22, 06:24
No, no, it was probably me with an antagonistic tone! Sorry. I was imagining differently, and it seemed to me Softsqueeze was the easier way. I think the problem with stream.mp3 is that the user has to use the webUI for playlist generation, etc. which is to be avoided - no telling what else they'll do once they're into it!

4mula1
2007-03-22, 06:44
To a degree the whole idea of using Softsqueeze brings up a point that some people have wanted: an easy way to duplicate player settings. As it stands now, when I change SlimServer to a different version I have to change all of the menu, display, and audio settings for 2 SB3s and 2 Softsqueeze installs. That sucks. Along the lines of being able to copy settings from one player to another, why not entertain the idea of a new player template. One template for hardware players (which tend to be local) and one for software clients. In the template for the software clients I could set bitrate limiting to 128k and all new software clients would inherit that, and could only be changed by deliberately changing it in SlimServer.

That would make "mass" Softsqueeze deployment easier, in that the users wouldn't have to set it themselves.

azinck3
2007-03-22, 07:06
To a degree the whole idea of using Softsqueeze brings up a point that some people have wanted: an easy way to duplicate player settings. As it stands now, when I change SlimServer to a different version I have to change all of the menu, display, and audio settings for 2 SB3s and 2 Softsqueeze installs. That sucks. Along the lines of being able to copy settings from one player to another, why not entertain the idea of a new player template. One template for hardware players (which tend to be local) and one for software clients. In the template for the software clients I could set bitrate limiting to 128k and all new software clients would inherit that, and could only be changed by deliberately changing it in SlimServer.

I agree--I think that's an excellent idea.