Skip to main content
V
VejOut
Known Participant
April 23, 2009
Question

FMS3 - videos start immediately in domain, 20+ sec delay outside domain

  • April 23, 2009
  • 4 replies
  • 3065 views

We are running FMS3 on Windows 2003 Server. Videos stream and play fine when inside our domain, but outside the domain the videos take anywhere from 20 or more seconds before playing.

After analizing the connections it was determined that the player is randomly trying to access ports until it gets to the one that works, but this is ONLY happening from people trying to view videos from outside our domain.

The server is not behind a firewall.

Any ideas?

    This topic has been closed for replies.

    4 replies

    V
    VejOutAuthor
    Known Participant
    May 22, 2009

    SOLVED!

    After reformatting the server, reinstalling the OS, reinstalling FMS3, and putting all the videos in the default locations, the server now works from all locations (finally!).

    I'm not sure which of these did it, or if it was a combination of things, but that fixed it.

    V
    VejOutAuthor
    Known Participant
    May 15, 2009

    Okay, we've completely rebuilt this Windows 2003 server and the only non-default thing we've installed on it is FMS3.0.4. It will NOT work outside the college domain.

    Does anyone have some detailed settings for this type of setup that I can compare with?

    T
    techeye
    Participating Frequently
    May 15, 2009

    Do you still get this message?

    Failed to create listener for adaptor _defaultRoot_, IP 443, port 1935:

    That "IP 443" doesn't look like a valid IP address to me.

    V
    VejOutAuthor
    Known Participant
    May 15, 2009

    Yes, was still getting that error, so I edited the fms.ini line from this:
    ADAPTOR.HOSTPORT = :1935

    to this:
    ADAPTOR.HOSTPORT = 66.194.105.214:1935

    Then restarted FMS3 and took a look at the Event Viewer --> Application and found these:

    information - Server starting...

    information - Server started (C:\Program Files\Adobe\Flash Media Server 3\conf\server.xml).

    Error - Failed to create listener for adaptor _defaultRoot_, IP 66.194.105.214, port 1935: .

    information - Listener started ( _defaultRoot__edge1 ) : localhost:19350/v4

    Error  - Failed to start listeners for adaptor _defaultRoot__edge1.

    Error  - Failed to start edge : _defaultRoot__edge1

    T
    techeye
    Participating Frequently
    April 24, 2009

    Just because _your server_ isn't firewalled doesnt mean that your network isn't firewalled.  We know your not a network person (at least you stated as much), so ask your network team for help.  Tell them you want to verify that the fms ports are open externally.  Or if you feel so inclined, there are some great port scanners readily available such as nmap:

    Your golden ticket looks like this:

    nmap -O yourHost.yourDomain.com

    PORT     STATE SERVICE

    1935/tcp open  rtmp

    V
    VejOutAuthor
    Known Participant
    April 24, 2009

    Well, we are also running a FMS2 server (separate box) that is behind the firewall, and it works just fine. So, system wide, those ports must be open as they use the same ports to communicate.

    Since there is no firewall running on the FMS3 box, where else could I possibly look on it for something that would mess up the ports?

    In the Application Event Log I'm seeing an error:

    Source: FMS (Edge)

    Category (263)

    Event 1013

    with the detail of:

    Failed to create listener for adaptor _defaultRoot_, IP 443, port 1935:

    If that helps at all.

    V
    VejOutAuthor
    Known Participant
    April 28, 2009

    On a side note, the player we are using was originally created to work with a FMS2 server. Not sure if that makes any difference, but it might be relevant. When it works with the FMS2 server, there is no delay like there is with the FMS3 server.

    I've been looking and looking for a decent example of how to make an RMTP call to a FMS3 server using ActionScript 3 and NOT useing the video component, but have not found one yet.

    T
    techeye
    Participating Frequently
    April 23, 2009

    So what port is being negoitated?   Even though the server isn't behind a firewall, there may be some other network device or proxy that isn't handling the connection correctly.

    V
    VejOutAuthor
    Known Participant
    April 24, 2009

    Port 1935 and 443 are being used for FMS3. If the port was being blocked by something it wouldn't work at all, correct? What makes no sense is that it works immediately when accessed from the same domain it's hosted on (inside our network), but has the 20-30 second delay when accessed from anywhere outside our network. So, the port problem is only happening from external hits even though both internal and external hits are calling the exact same URL and RTMP. I'm not a network person, but that makes no sense to me at all that there would be a difference.

    The Windows 2003 server has the firewall turned off. There is no proxy server running on it. The only other thing running on this server is IIS, and it's using port 80.

    A
    Anonymous
    April 24, 2009

    The default port Flash Player uses to connect to FMS is 1935; if a port is not specified in the NetConnection.connect() call, Flash Player attempts to connect to ports in the following order: 1935, 443, 80 (RTMP), 80 (RTMPT).

    Go to this technote from the external clients to see which ports Flash Player is able to use to connect to FMS:

    http://kb.adobe.com/selfservice/viewContent.do?externalId=tn_16466&sliceId=1

    For more information about ports and how to specify which ones Flash Player uses to connect to FMS, see this technote:

    http://kb.adobe.com/selfservice/viewContent.do?externalId=tn_16499&sliceId=2

    HTH,

    Jody

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