Multiple server instances - configuration for Windows 2008

[JohnSmither]

Hi

I'm running Windows 2008 server and I note from these forums that I can run multiple server instances on this server. However I would like some more in depth knowledge on both the server security aspects and the shoutcast configurations. I was wondering if the more experienced could assist with this. Specifically:

(a) Can anyone link me to a good sites that explain how to restrict user access on servers to just one folder containing the shoutcast server instance? Is it just simply locking the server down for one user to one folder? Would it be correct for the user to access through remote desktop?

(b) The key forum posts on this website to explain the configurations of multiple server instances? Can I use different folders for different server instances?

Once again many thanks in advance?

[JohnSmither]

Do I need to set up a VPS for each?

[dotme]

Depends on your goals. If this is your server, for your use, then just fire off instances and you're all set. If this is something you plan to resell instances, it gets more complicated. First, Windows isn't the best streaming platform. It works, but tends to lack good burst-on-connect when serving up higher bitrate (128k+) streams.

The simplest route when reselling is just to perform the setup and adjustments yourself, and give customers a web form to send you their requests. You can automate, of course, but plan to invest time and money if that's the goal.

[DrO]

i won't properly answer a) as that's not really my area, though if you are looking to host things for other people (as seems to be the way from the tone of your post), there are config options in the v2 DNAS which allows for restricting access to just one stream via the stream specific passwords, etc if you are happy running things that way.

for b) you can multiple instances of the DNAS (be it v1 or v2) on the same machine / host - you just have to run different config files set to use different ports (via the portbase option).

so you can just have one copy of the sc_serv file and just run it with different config files set to use a common file and then have specific child config files for where to save the logs, etc in separate folders or even the same one and use the 'unique' option to do it (is what is used for our relay hosts so you have one sc_serv, one common.conf and x many station specific config files which is what is passed to the DNAS on loading).

[edit]
dotme's post wasn't there when i started.

-daz

[JohnSmither]

Thanks to both of you for the reply. Yes, reselling is something I am now contemplating. I take the point on the Windows 2008.....I'm committed to this at present and it is the solution I know, unfortunately.

My immediate sticking point on this is allowing a user access to upload their music to a secure folder which only they access and then applying auto DJ for them; hence why I was asking about the server security.

Can anyone therefore provide me with an optimum solution for user access to the server to upload files and run auto-dj?

[dotme]

This will probably require Daz to offer sc_trans tips since I'll confess I haven't worked with it. I do know Windows Server pretty well though. For uploading, you have a couple of options. Under no circumstances would I grant RDP access though.

Through IIS, you can set up FTP in such a way that users are contained within their own folder, and can't walk "up the tree" to see the root or other folders.

If your end users are not tech-savvy and you think FTP is too much for them, then you'd want to either write your own web app, and get a COM component that allows anonymous uploading via HTTP, OR search for 3rd party control panels/systems.

Or... you can make the DJ/customer responsible for using a 3rd party AutoDJ service, and simply host their streams. The possibilities are many here.