Skip to main content
Inspiring
March 2, 2007
Question

finally a solution to all your firewall problems

  • March 2, 2007
  • 15 replies
  • 6065 views
I finally have answer to all of you who are seeking this question.


When the Flash Player encounters the connect() method, it attempts to connect to your FCS following a very specific pattern. It first attmpts to connect over port 1935, then port 433, then port 80 and then it automatically attempts to tunnel through by sending rtmp data over http also called RTMPT it turns out the automatic sequence of attempts is fine for many situations however you may find some users can't make a connection (well , the NetConnection can't) because their firewall blocks data from traveling through port 1935. If those users can connect to any website surely they can use port 80 .And even if their setup blocks rtmp surely they can use RTMPT over port 80 because its really just plain http ...you might think the final attempt by flash player RTMPT on port 80 to be failsafe however the problem is that if you are running your webserver on the same machine as FMS then they can't both use port 80 at the same time....a perfectly legitimate solution is to use to computers one for the webserver and one for FMS ......two computers probably means you need to specify the domain in your rtmp (rtmp://mydomain.com/video).

To force the flash player to try to connect through a specific port other than the defaults as specified above.....write rtmp as ....my_nc.connect("rtmp::8500/mydomain.com/video);

FlashMX2004 by Phillip Kerman
    This topic has been closed for replies.

    15 replies

    Participating Frequently
    September 1, 2008
    hi there,

    i hope you can help me with my problem.

    i have an fms3 running. i configured the adaptor.xml with port 1935, 80, 433.

    but now it still have the problem that a connection over port 80 doesn´t work.

    anyone a hint?

    Participating Frequently
    May 22, 2008
    To force the flash player to try to connect through a specific port other than the defaults as specified above.....write rtmp as ....my_nc.connect("rtmp::8500/mydomain.com/video);
    Participating Frequently
    May 9, 2008
    Good topic but I still need help....
    Basically, my web client's flash player won't connect to my local fms if i use router (works without router and window vista firewall is on with port 1935 open).
    I tried to open port 1935, 80 & 433 same time in my router but still no luck....
    Do I need to modify anything in my Adaptor.xml and any others files to get it to work??
    Please help!!
    d
    Inspiring
    November 2, 2007
    *bump*
    May 1, 2008
    To be blunt...why is Macromedia/Adobe so brain dead when it comes to this issue? I work in a large enterprise and we're not going to allow direct connections from clients to Internet servers on port 80,443, or 1935 that use some proprietary protocol. If you want large enterprise users to be able to see your content, the client needs to respect the proxy and content filtering we have in place. Why even use a proprietary media format?...there are existing formats that are well established. It's hard to make exceptions when alternatives appear to already exist and Adobe has such a crappy security track record.

    Just to clarify, it is not difficult to "get through" firewalls and proxy servers. Products have been doing it for years now. I'm oversimplifying, but basically always use port 443 or 80. If the client browser is using a proxy(which any client software can easily determine), you use an HTTP CONNECT call to the proxy. Don't use port 1935 because many enterprises don't allow HTTP CONNECT calls on just any port...use 443 or 80. This will get through nearly all HTTP proxies. It's the same type of call used for HTTPS connections.
    Participant
    August 21, 2007
    Hello

    I am running the Adobe FMS locally on my home PC, I have an application running on a remote server that can connect to my applications directory and the service works fine(from home).

    If I try to access the same application from a Computer that is not in my home, it no longer connects to the FMS server.

    If I http://localhost:1935 from home, I see nothing, but the application on the remote system can still connect using RTMP://HomePC-IP/my_app.

    I configured all the .xml files to listen to port :1935.

    I also tested the wowzamedia server and had no problem connecting to port :1935 from outside of my home network, so my ISP is not blocking port :1935.

    Any ideas, seems like I missed a config inside FMS.
    Inspiring
    August 14, 2007
    *bump*
    Participating Frequently
    June 22, 2007
    We have our FMS on a seperate machine than our webserver and still get the occassional firewall blockage (very small percentage, I'm estimating).

    Given the fact that there are countless firewall configurations, I'm inclined to agree that there's not much you can do on your end to prevent ALL firewall blockage.

    Hopefully things will get better as Firewall configurations are upgraded on the user end.

    June 7, 2007
    And to add, make sure that your fms.ini ADAPTOR.HOSTPORT setting has values of :1935,80 to accept listening on those ports.
    June 7, 2007
    And to add, make sure that your fms.ini ADAPTOR.HOSTPORT setting has values of :1935,80 to accept listening on those ports.
    June 7, 2007
    And to add, make sure that your fms.ini ADAPTOR.HOSTPORT setting has values of :1935,80 to accept listening on those ports.