Event ID 309 — Data Transfer Protocols

Applies To: Windows Server 2008

In Windows Media Services, data transfer protocols are used to stream Windows Media-based content to clients. You can configure Control Protocol plug-ins in Windows Media Services to manage these protocols that control communication between the Windows Media server and clients. You can use these plug-ins to configure Real Time Streaming Protocol (RTSP) and Hypertext Transfer Protocol (HTTP), protocols that handle the high-level exchange of data. You can also use these plug-ins to configure User Datagram Protocol (UDP) and Transmission Control Protocol (TCP), protocols that manage more fundamental tasks such as network connectivity and packet error correction. For more information, see About data transfer protocols.

Event Details

Product: Windows Media Services
ID: 309
Source: WMServer
Version: 9.5
Message: Windows Media Services cannot bind to TCP port %1. The port is being used by another service.


Eliminate the port conflict

Assign Windows Media Services to a different port or create additional Internet Protocol (IP) addresses so that the Windows Media Services service and the Web service can use port 80 on separate IP addresses. For more information, see the Using HTTP streaming and other services on the same computer.


To verify that the selected control protocols can be used to deliver content to clients, test the stream by using Windows Media Player:

  1. If you want to test the stream by using Windows Media Player on the computer that is running Windows Media Services, you must install Desktop Experience. For more information, see Installing Desktop Experience.
  2. On the Windows Media server, open Windows Media Services. To open Windows Media Services, click Start, point to Administrative Tools, and then click Windows Media Services.
  3. In the console tree, click the publishing point that hosts the stream you want to test.
  4. In the details pane, click the Announce tab, and then, in Connect to a unicast stream, note the value of the URL that a client can use to access the content.
  5. Start Windows Media Player on a computer that can access the stream, and enter the URL that you noted in the previous step.
  6. Using the Player controls, test the control functionality of the content stream. Broadcast streams can use the Start and Stop commands. On-demand streams can use the Start, Stop, and Pause commands, and the Seek bar.
  7. Test all the available streaming protocols. A unicast stream will try to connect by using the MMS protocol, but will switch to the RTSP protocol if network conditions or the Player version requires it. The HTTP protocol is not active unless the WMS HTTP Server Control Protocol plug-in is enabled. For more information, see About data transfer protocols.

Note: If some members of your expected audience will access the stream from outside your network firewall, your testing scenario should include that condition. For more information about the firewall configuration for Windows Media Services, see Firewall Information for Windows Media Services.

Data Transfer Protocols

Streaming Media Services