QuickTime Streaming Behind the FirewallIn addition to streaming using RTSP/RTP standards-based transport, QuickTime can now also use HTTP as a transport for streaming. While HTTP doesnt 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. How to set up QuickTime for streamingQuickTime is designed to automatically configure your streaming connection the first time you try to play a streaming movie. If you are having trouble with streaming or have moved your machine from one network to another then you may want to manually configure your QuickTime streaming network settings to establish the best streaming connection possible.
If QuickTime successfully configured your connection, youre done. You can skip the rest of this. If QuickTime could not configure your connection, then continue to step 4. 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 to work properly inside your firewall, please follow the following IETF recommendation:
|
|
|
|