This document (10024723) is provided subject to the disclaimer at the end of this document.

Windows Media Player and HTTP Proxy 

Novell BorderManager 3.0

Novell BorderManager 3.5

BorderManager 3.0 doesn't proxy Windows Media player. It will, however proxy Real Audio and Real Player. BorderManager 3.5 can PROXY the Windows Media Player through an HTTP stream. Configure the Media Player to specifically use the PROXY service at the address of the PROXY server. Do NOT rely on any auto-detect options in either the browser or the media player. If problems still occur under this configuration try the suggestions in the next paragraph.

Additionally, testing has shown that if the PROXY server port is changed to 80 rather than the default of 8080 Windows Media Player version 7 works just fine using an HTTP stream. It has not been determined if this is a Microsoft issue but incidents have been opened with Microsoft to address the issue. If the default port is changed to 80 make sure that Transparent Proxy is disabled and that no Web Server is loading on port 80 that will conflict with that address and port. If a Web Server is required then add a secondary IP address on the PRIVATE card and define that address as either the Web Server's address or Proxy's address.

Running NAT on the server is another option. Filter exceptions must be created to use NAT for TCP and UDP ports to destination port 1755 outbound (the port is actually configurable. It is 1755 by default and it is specified by the client.)

The Origin of this information may be internal or external to Novell. Novell makes all reasonable efforts to verify this information. However, the information provided in this document is for your information only. Novell makes no explicit or implied claims to the validity of this information.