Skip to main content
L
LLuckham
Participant
March 13, 2009
Question

Can FMS coexist on a Windows IIS webserver?

  • March 13, 2009
  • 2 replies
  • 1804 views
I'm new to video streaming and to FMS. I have a client that has been streaming VOD on a MS Server 2003 box but is not satisfied with the performance, in particular the substantial delay in the delivery while Windows Media Services buffers to the end user. This delay is apparent even with Advanced Fast Start. More particularly although enabling AFS does shorten the lag, it seems to do so by serving up a smaller image.

Looking around for a way to improve their delivery I encountered FMS. Without giving it too much thought (always a bad thing) I downloaded and installed FMS to give it a try. Surprise. Apache stopped all of their websites! Very dumb of me! Promptly diagnosed. Stopped Apache & restarted the websites. Now the question.

Is it possible to have FMS running concurrently on a Windows IIS server, or would I need to install a completely separate box for them to do this? And, if it is possible, what's the best practice to accomplish the task?

Thanks for reading.

Larry
    This topic has been closed for replies.

    2 replies

    A
    Anonymous
    March 16, 2009
    By default FMS 3.5 listens at port 80 (check variable ADAPTOR.HOSTPORT in conf file fms.ini), While listening at port 80; it as configurable property to forward unknown(non rtmp ) HTTP requests to a local webserver running at a port mentioned in fms.ini variable HTTPPROXY.HOST.


    To make IIS & FMS work together you might try IIS listen on a different port and ask FMS to proxy the request to the port your IIS is listening.


    If there is no dependency; you might consider switching to default apache that comes with FMS :)

    Please let me know if it helps.
    J
    jonpor
    Inspiring
    March 16, 2009
    Thanks you fmslove.

    I went into fms.ini and changed the line:
    ADAPTOR.HOSTPORT = :1935,80

    to
    ADAPTOR.HOSTPORT = :1935

    Since I am developing, I don't need FMS listening on port 80. That fixed my problem. Just a little curious why I never had this issue with previous versions of FMS.
    A
    Anonymous
    March 13, 2009
    The problem is that both FMS and IIS want to bind to port 80... but only one device can bind to a given port on a given IP.

    The solution... add another IP address to your NIC, and bind FMS to the new IP instead of the IP you're using for IIS.

    If you're using IIS6 or later, you'll need to use httpcfg to disable IIS socket pooling, otherwise IIS will just bind to all IP's
    J
    jonpor
    Inspiring
    March 16, 2009
    >>The problem is that both FMS and IIS want to bind to port 80.

    I am hitting a similar problem as well using a FMS and IIS on XP pro during development. But until FMS 3.5 I have never had a conflict between IIS and FMS with both on the localhost. I've used 2.0 and 3.0 without problems. (And since it is localhost, FMS should be connecting on port 1935 instead of 80 ).

    But as of FMS 3.5 I am seeing there is a conflict for port 80. I need to shut down FMS to start IIS, and *up until now* I could then start FMS without killing IIS (up until I rebooted). I was passing through the forums when I saw this thread. I'm thinking this is being introduced by Apache, although *supposedly* it is turned off by the default install. Or could this be FMS listening on 80? It seems odd to me that previous versions worked without this snag. Anyone else hit this problem?

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