Windows
Media
Highest Performance: TCP Unicast is streamed using the TCP protocol
over port 1755. This is the default protocol and provides highest performance.
Fallback Option*: HTTP Unicast is streamed using the HTTP protocol over
port 80. This is the fallback protocol and is somewhat less efficient
than TCP, due to added HTTP overhead. If your firewall is providing proxy
services for HTTP port 80, you should be able to access the Webcast video.
In order to achieve higher performance, your firewall will need to proxy
port 1755, or be open to that port and provide a Network Address Translation
(NAT) to each computer viewing the Webcast.
The Media Player does
not support SOCKS protocols. You may have success viewing the Webcast
through a SOCKS proxy server by using a SOCKS application called SocksCap32.
This is not a supported implementation.
For
more information regarding Firewall Configuration for streaming through
Windows Media, Network Administrators can refer to the following source:
http://www.microsoft.com/windows/windowsmedia/serve/firewall.asp
Real
Player
The AutoConfiguration option in Real Player,
which is set by default, usually works fine. However, if there are issues
with streaming in Real Player across your network please contact your
Network Administrator. Below is information that may assist them in troubleshooting
the issue.
Network-level
firewalls, such as packet filters, use access control lists to allow traffic
destined for some ports to pass from the Internet to the organization's
internal network and to block packets for other ports. To allow any version
of RealAudio Player or RealPlayer to play correctly,
it is only necessary for the router to allow packets to pass to the inner
network that are bound for the following range of ports:
· TCP port 7070 for connecting to pre-G2 RealServers
· TCP port 554 and 7070 for connecting to G2 RealServers
· UDP ports 6970 - 7170 (inclusive) for incoming traffic only
The
TCP port is used by RealPlayer to initiate a conversation with an external
RealServer, to authenticate RealPlayer to the server, and to pass control
messages during playback (such as pausing or stopping the stream). RealSystem
G2 uses two TCP protocols for conversations between Players and Servers.
For
more information regarding Firewall Configuration for streaming through
Real Player, Network Administrators can refer to the following source:
http://service.real.com/firewall/adminfw.html
|