Skip to main content
jayesh.r.sidhwani
Known Participant
July 23, 2009
Question

Flash Media Server stopped working

  • July 23, 2009
  • 1 reply
  • 1101 views

Hello All,

I am new to FMS and have been working on Flash Media Development Server.

My Setup:

I have a FMS and HTTP server on one machine A and all my swf's were kept there. I had one more machine B in a network, from which I was testing the swf's on Machine A.

Everything was running fine, until suddenly I could not access the swfs from Machine B.

Moreover, when i checked the Admin console in machine A, there was no client (referring Machine B) was connected to the FM Development Server.

What could have happened sosuddenly. In the swf that i tried connecting from Machine B, I debugged and found out that the swf was not able to connect to the FMS. (NetConnection.Connect.Failure)

Please help me.

Thanks

    This topic has been closed for replies.

    1 reply

    July 23, 2009

    Are you addressing machine A by IP, and if so, does machine A have a static IP address on the network? Seems to me that to have both your HTTP and FMS server become unavailable like that, there must have been a change at the network level.

    jayesh.r.sidhwani
    Known Participant
    July 23, 2009

    Thanks for replying Jay.

    Yes, I am referring the Machine A with its IP and the IP is static (at times if it changes, i make the necessary changes), so that part is clear.

    And as far as the network level changes, i wonder, because till yesterday everything was working perfectly alright with the same conditions. It just suddenly started responding weird.

    I had only enabled some port forwarding in my router and had included a virtual directory in webroot.

    however, when i reverted back to my original settings, even then the same code ceases to work.

    Thanks

    jayesh.r.sidhwani
    Known Participant
    July 24, 2009

    Thanks Jay,

    I found out the error.

    Machine A had all of a sudden blocked port 1935, so all the machines could not connect to it for RTMP.

    i used this utility to start my debugging process http://bit.ly/15Q1xA

    The error might sound silly, but it took me around 12 hrs to figure out what could be the error.