Cable Modem Troubleshooting Tips


 

Streaming media

This page applies to applications for playing streaming media, such as Real Player, Windows Media Player, QuickTime Player.


Performance issues

Players for streaming media, such as Real Player, Windows Media Player, QuickTime Player have options in their preferences settings for telling them the bandwidth of your network connection. By default, they usually assume a slow dial-up modem connection. You should set this preference option to the available value equal to (or next less than) your downstream bandwidth. For instance, if your nominal downstream bandwidth is 512 kbps, and the nearest options available are T1 (too high) and Dual-ISDN (too low), then select Dual-ISDN, as being the highest option less than 512 kbps. The exception is the Windows version of Microsoft Media Player 7, where you should check Detect my connection speed (not available in Mac version).

For instance, on a 512 kbps or better download broadband connection, configure RealOne Player as follows:


Streaming protocols and Firewalls or NAT routers

Some streaming protocols do not work if you have a firewall, or if your PC is behind a NAT router (either a physical router or ICS). In the preferences for the above streaming players, you can usually specify which protocol options to allow or deny:

If you are behind a firewall or a NAT router, you might have to:

For example, to prevent RealOne Player for Windows from attempting to use the UDP protocol:

Now the player will attempt to use only TCP and HTTP protocols, which should work through firewalls and NAT routers without special configuration. These preferences will apply also to the Real Player plug-in for web browsers.

Real Player 8 for Macintosh is able to recover from non-working UDP and fall back to TCP without special configuration.


Streaming protocols and Inktomi Traffic Servers

Some ISPs use Inktomi Traffic Servers to cache streaming protocol data in a similar way to how they use them as a transparent web proxy cache. The interception of streaming protocol data is meant to be transparent, but for some reasons (not understood) Real Player does not work correctly for some sources (it appears to work for RTSP, but not for PNA protocols), and Windows Media Player does not work correctly for some sources (MMS protocol). Consult the following work-arounds for possible fixes:


Real Player on Windows - work-around

On Windows, the symptom of this problem is:

either an error dialogue from the RealPlayer web browser plug-in saying:

A General Error has occurred.

or an error dialogue from the RealOne Player application saying:

Connection to server has been lost. You may be experiencing network problems.

Configure Real Player for Windows to work around this Inktomi problem as follows:

Now the player will explicitly send all requests via the selected Traffic Server. These preferences will apply also to the RealPlayer plug-in for web browsers.

If your PC is firewalled or behind a NAT router then you might also have to disable the UDP protocol under PNA Transport Settings as described in the previous section.

If after making this configuration, you receive an error dialogue from the RealOne Player saying:

Requested file not found. The link you followed may be outdated or inaccurate.

then the chosen Traffic Server does not support PNA proxy, or it is temporarily broken. You should try the above configuration again, specifying a different Traffic Server within your ISP's network, preferably one at your regional centre, otherwise one at a different regional centre.

[Technical note: the use of port 1090 for PNA proxy replaces the normal Real Player usage of port 7070 for PNA].

For more information about Real Player and firewalls, see http://service.real.com/firewall/.


Real Player on Macintosh - work-around

On Macintosh, the symptom of this problem is:

either an error dialogue from the RealPlayerG2 web browser plug-in saying:

Unable to connect to server. Check network transport settings or run auto-configure.

or an error dialogue from the RealPlayer application saying:

Connection to server could not be established. You may be experiencing network problems.

Configure Real Player 8 for Macintosh to work around this Inktomi problem as follows:

These preferences will apply also to the RealPlayerG2 plug-in for web browsers.


Windows Media Player - work-around

Configure Windows Media Player as follows to work around a failure to play media over the MMS protocol via Inktomi traffic servers:


Windows Media Player for Macintosh - no work-around

There is no method of setting an MMS proxy in Windows Media Player for Macintosh 7.1.


Finding the Streaming Media Proxy

The default streaming media proxy might not be the same server as the transparent web proxy cache (see Which is my web cache?). Nevertheless, sometimes the transparent web proxy can act also as a streaming media proxy. In cases where it can, use it. But sometimes it cannot, and you need to discover an alternative local streaming media proxy.

To discover the default streaming media proxy under Windows, launch a web browser, launch RealOne Player, and launch a command window. In the web browser, navigate to a site which contains links to Real Player clips that use the RTSP protocol (for instance, at the site http://news.bbc.co.uk/, the links to BBC News 24 and BBC One TV news use RTSP). While the RTSP clip is playing in RealOne Player, enter the command netstat -a in the command window, and look for an ESTABLISHED TCP connection to a host using a remote port other than 80 or 554: a port often seen used is 9231. This host will be the default streaming media proxy.

If the above procedure does not yield a working streaming media proxy, NTL users can experiment to find one as follows. First find the default transparent web proxy (see Which is my web cache?). It will have a name of the form

inktomiN-XXX.server.ntl.com

where N is a number, and XXX is a code for the local data centre. Try various values for N until you find one that works as a streaming media proxy.


Return to Index.