This article was previously published under Q262382
This article has been archived. It is offered "as is" and will no longer be updated.
Third-party applications cannot play back Advanced Stream Redirector (ASX) files that are generated by Active Server Pages (ASP) on Netscape if the files come from servers where the header is set to no cache.
By default, the Windows Media Player plug-in is loaded to handle the MIME type. The Windows Media Player plug-in then finds the owner of the ASX extension to determine whether Windows Media Player is really the owner of the file type. Because a third-party application owns the extension, the plug-in waits for Netscape Navigator to download the ASX file. When the plug-in is notified by Netscape Navigator that the download is complete, the plug-in passes the file to the third-party player. However, because the server is set to no cache, the file is deleted, and therefore, no file is actually there to pass to the third-party player.
A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem.
To resolve this problem, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone 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.
The English version of this fix should have the following file attributes or later:
Date Time Version Size File name Platform ---------------------------------------------------------------- 05/02/2000 14:36 4.72.2106.1 257,760 Wmp-nplug.exe x86
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
This fix is intended for all platforms: Windows NT, Windows 2000, Windows 95 and Window 98.