Skip to main content
B
booming09
Participant
August 23, 2012
Question

Preparing ports on my network for FMS?

  • August 23, 2012
  • 1 reply
  • 2087 views

Hey,

I've finally got my server installed with Windows OS. I was reading the FAQs for FMS and came across:

What do I need to do in my network to prepare for Flash Media Server? 

    Flash Media Server can use multiple protocols over both TCP and UDP. All protocols can be configured and enabled or disabled. Ports and protocols must be enabled on your network for Flash Media Server to operate normally.

    The RTMP protocol (used for video streaming and communication) default TCP port is 1935, but it can also operate over port 443 (for SSL) and port 80 using a tunneling version of the protocol. Flash Player has a built-in port priority that may choose to communicate over these protocols.

    The HTTP protocol default is TCP port 80, shared with RTMP tunneled (RTMPT). The internal HTTP server will communicate to Flash Media Server internally using port 8134.

    RTMFP (used for P2P introductions or multicast) uses UDP with a configurable port range.

    Multicast-enabled network hardware is required to take advantage of native IP multicast. This approach is best for internal, enterprise, VPN, or LAN networks.

    Flash Media Server administration operates over default TCP port 1111.

I just wanted some help here. If I intend to run RTMP, then do I need to 'open' these ports?

Thanks,

This topic has been closed for replies.

1 reply

A
Anonymous
August 23, 2012

If you're only using RTMP/T/E/S (and not RTMFP), then you'll only need ports 1935 and 80 (for RTMP clients), and 1111 (if you intend to use the admin console or admin HTTP interface)

B
booming09Author
Participant
August 23, 2012

Do I have to open these ports or anything or just keep them free from other applications?

A
Anonymous
August 23, 2012

Both. Ports will need to be open on your firewall  so clients can connect to the server. If your server is behind NAT, you may also need to forward those ports at your router.

The ports on the IP you're binding FMS to can't be occupied by other server applications (only one server can occupy any given port on any give IP at once).  If you have other server applications that need those ports (an HTTP server on port 80 for example), add another IP address to the server, and use the new IP address for FMS.

Incidentally, if you can be sure that all of your clients will be able to connect using RTMP over port 1935, you can skip port 80. Port 80 is used for tunneled RTMP, and for HTTP (if you're serving any HTTP protocols)

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