Using HTTP for Streaming and Downloading from the Same Computer

dmnelson — Fri, 26 Sep 2008 20:08:00 GMT

By default, the HTTP Listener (HTTP.sys) for the default Web site in IIS 7.0 listens to all requests coming in on port 80 for all static IP addresses bound to the network adapter (site binding = http:*:80:). Thus, when you install Windows Media Services on the same computer, you can't stream by using HTTP. If you try to configure HTTP streaming by enabling the WMS HTTP Server Control Protocol plug-in in Windows Media Services, you'll get an error that looks something like this:

Error Code: 0xC00D158B
Error Text: One usage of each socket address (protocol/network address/port) is permitted. Verify that other services (such as IIS) or applications are not attempting to use the same port and then try to enable the plug-in again.

There are two approaches to resolving this issue. One is to change the port that Windows Media Services uses for HTTP streaming. But if you must use port 80 for your Web traffic, another approach is to obtain another static IP address for use with your network adapter, and then configure Windows Media Services to use that IP address with port 80. Earlier versions of Windows Media Services contained the HTTP Sys Configuration tool for assigning additional IP addresses to your services, but in Windows Media Services 2008, that tool is not available and you must configure the HTTP.sys IP inclusion list by using enhanced netsh commands instead. This article describes both of these approaches in detail.

Windows Media Server or Web Server?

dmnelson — Thu, 15 May 2008 20:57:00 GMT

As promised in Chris Knowlton's Blog, we have an updated document that compares digital media content delivery from Windows Media servers (running Windows Media Services 2008) and Web servers (running IIS 7.0). You can find it here.

Dave Nelson's Blog

Using HTTP for Streaming and Downloading from the Same Computer

Windows Media Server or Web Server?