Article ID: 932756 - View products that this article applies to.
After you install Windows Media Player 11, you receive the following error message when you try to play content that is located on a Windows Media Services 4.1 server:
0xC00D11B3: Windows Media Player cannot play the file because a network error occurred. The server might not be available. Verify that you are connected to the network and that your proxy settings are correct.
Windows Media Services 4.1 supports only the Microsoft Media Server (MMS) protocol and the Hypertext Transfer Protocol (HTTP) protocol. Windows Media Player 9 adds support for the Real Time Streaming Protocol (RTSP) protocol. However, support for the MMS protocol began to be deprecated in Windows Media Player 9. Windows Media Player 11 does not support the MMS protocol. Therefore, if the HTTP protocol is not enabled on the Windows Media Services 4.1 server, Windows Media Player 11 cannot connect to the server.
To resolve this problem, upgrade to Windows Media Services 9 Series. Windows Media Services 9 Series is available as part of Microsoft Windows Server 2003. To select the correct version for your business needs, see the product documentation.
Windows Media Services 9 Series has support for RTSP-enabled clients. Windows Media Services 9 Series allows for legacy clients to connect by using the MMS protocol.
If you cannot upgrade, you must enable the HTTP protocol for Windows Media Services 4.1. To do this, follow these steps:
When you enable HTTP, a port conflict with IIS may cause an error if Microsoft Internet Information Services (IIS) is installed on the same server as Windows Media Services. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/268585/ )How to run IIS 5.0 and Windows Media Services with HTTP streaming enabled
MMS is used to represent both a protocol and a URL moniker. The MMS URL moniker (mms://) is still typically used by Web content authors to connect the client to the server. When the moniker is used in this form, the moniker allows for the client to automatically select among the supported protocols. When MMS is explicitly referenced as a protocol, the transport is specified as part of the URL moniker (for example, mmsu:// or mmst://). For more information about protocols and protocol rollover, see the product documentation.