Skip to main content
B
bank555
Participant
July 22, 2009
Answered

Best way to set up FMS?

  • July 22, 2009
  • 1 reply
  • 1169 views

I'm new to FMS and a bit confused on how I should set things up.

Right now, I have a web server running IIS and a database server. I originally install FMS 3.5 on the web server and set the port 1935.  However, many of my users have that port blocked so that's not the best option.

Should I install it on the database server so I can set the port to 80?

Also, does FMS work as a standalone server?  For example could you have two servers - one with IIS and the other with FMS.  When someone goes to the IIS web page can it pull in videos from the FMS server?  I'm guessing it can but I haven't found any information about this so any help is greatly appreciated.

    This topic has been closed for replies.
    Correct answer

    FMS is a standalone server, so yes, your .swf and html can be served from one server, and your FMS can be on another server (or another network for that matter).

    That said, if you have system resources and bandwidth to spare on the machine your HTTP server is running on, you can install FMS on the same machine. You just need to add a second IP address to your network interface. Bind IIS to one IP, and FMS to the other. If you're running IIS 6 or newer, you'll need to disable socket pooling (http://www.netfxharmonics.com/2007/07/Disabling-IIS6-Socket-Pooling). If you don't, IIS will continue to bind to all IP's.

    1 reply

    A
    Anonymous
    Correct answer
    July 22, 2009

    FMS is a standalone server, so yes, your .swf and html can be served from one server, and your FMS can be on another server (or another network for that matter).

    That said, if you have system resources and bandwidth to spare on the machine your HTTP server is running on, you can install FMS on the same machine. You just need to add a second IP address to your network interface. Bind IIS to one IP, and FMS to the other. If you're running IIS 6 or newer, you'll need to disable socket pooling (http://www.netfxharmonics.com/2007/07/Disabling-IIS6-Socket-Pooling). If you don't, IIS will continue to bind to all IP's.

    B
    bank555Author
    Participant
    July 23, 2009

    Thank you JayCharles.  That's good to know.  I found this tutorial - http://www.flashcomguru.com/tutorials/fcs_iis.cfm which walks you through each step.  Seems easy enough.

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices