Select the product you need help with
- Internet Explorer
- Windows Phone
- More products
How to configure firewalls and Network Address Translation (NAT) for Windows Media Services 9 Series
Article ID: 827562 - View products that this article applies to.
This article discusses the firewall ports that you must open to stream content from a media server that is located behind a firewall.
You can use control protocol plug-ins such as Microsoft Media Server (MMS), Real Time Streaming Protocol (RTSP), or Hypertext Transfer Protocol (HTTP) when you configure a firewall. To make the process of configuring firewalls easier, you can configure each control protocol plug-in on the server to use a specific port. Therefore, if your network administrator has already opened a series of ports for use by your Windows Media servers, you can allocate those ports to the control protocols. If the ports are not yet available, you can request that the default ports for each protocol be opened.
If ports on your firewall cannot be opened, Windows Media Services can stream content by using the HTTP protocol over port 80. For more information about how to configure the control protocol plug-ins, see the server help documentation.
The "More Information" section describes how to configure firewalls for the following list of situations:
Open the portsTo enable Windows Media Player and other clients to use the HTTP protocol, the RTSP protocol, or the MMS protocol to connect to a Windows Media server that is behind a firewall, open the following ports.
Collapse this tableExpand this table
If you cannot open all the UDP Out portsIf you cannot open all the UDP Out ports on a firewall, UDP packets that are sent by a Windows Media server may be blocked by the firewall and may not be able to reach the clients on the other side of the firewall. If this condition occurs, clients may still be able to receive a stream if the clients automatically roll over to a TCP-based protocol, such as HTTP, MMST, or RTSPT. However, the rollover causes a delay for the client that is receiving the stream. If you know that you will not be able to support UDP streaming through a firewall, you can decrease the rollover delay by clearing the UDP check box in the Unicast Data Writer plug-in Properties dialog box. For more information, see the server help documentation.
Distribution servers cannot use a URL that has an mms:// prefix to request a connection to the origin server.
Collapse this tableExpand this table
The following firewall configuration enables multicast streaming packets to traverse your firewall:
IP multicast address range: 22.214.171.124 through 126.96.36.199To enable IP multicast streaming, you must allow packets that are sent to the standard IP multicast address range to come through your firewall. This IP multicast address range must be enabled on both the player and server sides, and on every router in between the player and the server. IP multicast streaming typically will not work over the Internet because multicast-forwarding is not enabled on routers on the Internet.
The following example firewall configuration allows a computer that is running Windows Media Encoder outside a firewall to access a Windows Media server that is behind a firewall by using HTTP. The In port is the port where the server accepts connections. The Out port is the port where the server sends data to clients:
In/Out: TCP on port 8080
For more information about firewalls and ports for Windows Media Services 4.0 and 4.1, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/189416/ )Firewalls and ports used by Windows Media Services