QuickTime 4.1 provides new streaming capabilities for users. In addition to streaming using RTSP/RTP standards-based transport, it can now also use HTTP as a transport for streaming. While HTTP doesn’t always provide the best streaming performance, it does allow most users behind firewalls to receive QuickTime streams.

Firewalls are designed to protect corporate information, but they can also prevent you from viewing QuickTime streams. This is because firewalls are frequently configured to block data protocols that QuickTime uses for streaming. Use the information on this page to set your QuickTime settings. Server administrators can also use the information provided on this page to safely set up servers to block unwanted traffic but allow QuickTime streams in.

1. Open the QuickTime Settings control panel.
   
   
2. Choose Streaming Transport from the pop-up.
   
   


 

3. Click Auto Configure. If QuickTime is able to establish a connection you will see a dialog:
   
   




NOTE: The above is not the only ‘success’ dialog that you can see. For example, there is a dialog that will tell you that HTTP is being used because it couldn’t get UDP through.



If QuickTime is unable to establish a connection you will see a dialog:







If QuickTime successfully configured your connection, you’re done. You can skip the rest of this. If QuickTime could not configure your connection, then continue to step 4.



4. If your firewall is blocking direct network access, then you will need to use a proxy server. You can tell QuickTime about your proxy servers by opening the Streaming Proxy dialog from the QuickTime Settings control panel.
   
   



 


5. Check the Use System Settings check box to use the system settings you have already established with your web browser. If you uncheck this box, you may enter the name and port ID of any of your proxy servers. You will need to get this information from your system administrator.
   
   
6. After selecting a proxy server, you will need to manually set the correct transport in the Streaming Transport panel.
   
   
• If you are using a SOCKS proxy server, you should first try setting "Use UDP, RTSP port 554." If that doesn’t work, try setting "Use HTTP, port 80."
• If you are using an RTSP proxy server, you should set the Streaming Transport to "Use UDP, RTSP port 554."
• If you are using an HTTP proxy server, you need to set the Streaming Transport to "Use HTTP, port 80."

For Network Address Translation (NAT) Server Users
If you have a home or small business network in which several computers are connected to the Internet through an ISDN, ADSL, cable modem, or other high speed connection, you may run into problems accessing QuickTime movies streamed with the RTP/RTSP protocol. If your access device performs network address translation, allowing multiple computers at your site to share a single IP address, then you will either need that router to understand RTSP or you will have to use HTTP as a transport mechanism.

Recommendations for Firewall Administrators
QuickTime follows the conventions of the RTP and RTSP Internet standards to stream media over the web. To enable QuickTime 4 to work properly inside your firewall, please follow the following IETF recommendation:

• Open port 554 for RTSP/TCP data.
• Open ports 6970 through 6999 (inclusive) for RTP/UDP data.

For more information on the RTP and RTSP Internet standards:

• RTSP: http://info.internet.isi.edu:80/in-notes/rfc/files/rfc2326.txt
• RTP: http://info.internet.isi.edu:80/in-notes/rfc/files/rfc1889.txt

Recommendations for SOCKS Administrators
If your organization uses SOCKS to pass data through the firewall, you will need a SOCKS Version 5 server to pass RTP/RTSP streaming traffic. We have confirmed operation with the Aventail SOCKS server, though others should also work. NEC has a web site containing information about SOCKS Version 5 at http://www.socks5.nec.com/.

Recommendations for Proxy Administrators
If your organization uses application-specific proxies (e.g., HTTP or FTP proxies) to pass data through your firewall, for best performance you should use an RTSP proxy for the streaming traffic. Apple has created such a proxy and made it available in source code form. You may also choose to use HTTP for streaming traffic. However, users may experience reduced streaming performance.