This article has been archived. It is offered "as is" and will no longer be updated.
Important This article contains information about how to modify the registry. Make sure to back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986 Description of the Microsoft Windows registry
When Microsoft Internet Explorer and Microsoft Windows Media Player are set to use different HTTP proxy servers, certain requests may go through the proxy server that is specified by Internet Explorer instead of going through the proxy server that is specified by Windows Media Player.
These requests include but are not limited to the following types of scenarios:
Progressive download content
Requests for HTTP content in the range of ports 8000 through 9000
Multicast announcements (.nsc files)
ASF Stream Redirector (ASX) files
This behavior is different from the behavior of the earlier Windows Media Player version 6.4. This behavior may cause problems if you upgrade to Windows Media Player 9 Series.
For example scenarios, see the "More Information" section.
Windows Media Player uses Internet Explorer and its underlying WinINET or WinHTTP infrastructure for certain tasks during playback of content. If the destination server does exist outside the Windows Media Player proxy server but the destination server does not exist outside the Internet Explorer proxy server, the player cannot connect to the content.
To maximize startup times, the player also assumes certain things based on the request. Because some Web servers and some proxy servers use a port in the 8000 through 9000 range, the player tries to do a progressive download of the requested content. When the player tries to do this, the player uses the Internet Explorer proxy server settings.
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next update that contains this hotfix.
To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:
Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
For more information about how to download Microsoft Support files, click the following article number to view the article in the Microsoft Knowledge Base:
119591 How to obtain Microsoft support files from online services
Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Date Time Version Size File name -------------------------------------------------------------- 17-Mar-2004 15:26 18.104.22.16847 4,685,824 Wmp.dll 17-Mar-2004 15:35 22.214.171.12447 2,070,640 Wmvcore.dll
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For example, the player tries to use progressive download, and the URL request is in the range of ports 8000 through 9000. If you apply this hotfix in this situation, the player automatically uses the Windows Media Player proxy server if the player cannot serve the request by means of the Internet Explorer proxy server. This behavior is known as rollover.
For the other scenarios that are listed in the "Symptoms" section, Microsoft recommends that you do not change the default behavior of Windows Media Player. Sometimes, a third-party application that embedded the Windows Media Player ActiveX control relies on this behavior from earlier versions. This hotfix also permits these applications to enable compatibility with the behavior from earlier versions. You can enable the compatibility either programmatically or by means of the registry.
Registry controlled behavior
When you enable these registry values, the player behaves as specified by the appropriate flag.
Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.
Behavior that is specific to Windows Media Player
To control the behavior that is specific to Windows Media Player, follow these steps:
Create the following registry key (where AppName.exe is the name of the host application):
Add a REG_DWORD under this registry key that has a value of OptionFlags1.
You can OR the value for this registry key for a combination of behaviors in this hotfix and in other fixes to the same component:
0x0 - No behavior from earlier versions.
0x1 - The .nsc files will be downloaded by means of the proxy server that is specified by the player settings.
0x2 - The player will use the proxy server that is specified by the player settings for HTTP requests in the range of ports 8000 through 9000. The player will not do automatic rollover.
Atom controlled behavior
The settings that are mentioned earlier can also be set programmatically by means of an atom. Following are the atom values:
UseStreamingProxyForASXFileDownload - ASX files will be downloaded by means of the proxy server that is specified by the player settings.
UseStreamingProxyForNSCFileDownload - The .nsc files will be downloaded by means of the proxy server that is specified by the player settings.
ExcludeProxyCheckForProgressiveDownload - The player will use the proxy server that is specified by the player settings for HTTP requests in the range of ports 8000 through 9000. The player will not do automatic rollover.
These calls must be made before the Windows Media Player ActiveX control is loaded.
For more information about using atoms, visit the following MSDN Web site: