Member Avatar for Aestivalis

I installed a new Windows Server 2003 SP1 box, and added Media Streaming and IIS (as well as Darwin, but I'll leave that out for now). I can't seem to get Windows Media Streaming to work with IIS installed, even if the service is stopped. Once I uninstall IIS, it works again. I can't even stream to the server itself through the testing part of the MMC, so it's not a firewall issue. Has anyone else gotten them to work together? MS says that they should interoperate just fine, and I've even gone through the trouble of binding the site to a different IP address on the NIC, though I'm not trying to stream on port 80.

-Ray

  • 3 Contributors
  • 3 Replies
  • 258 Views
  • 1 Week Discussion Span
  • Latest Post Latest Post by Aestivalis

Dani AI

Generated

Short expert summary and concrete steps to try next (references below).

When IIS is present on the same Windows Server 2003 box as Windows Media Services (WMS) the usual culprits are (a) an HTTP-port / listener conflict (WMS can accept HTTP on port 80 while IIS owns port 80) or (b) IIS handling HTTP push/requests (an ISAPI/log component can intercept HTTP requests intended for WMS). Windows Media Services uses MMS (1755), RTSP (554) and HTTP (80) as control protocols, so a service that grabs those ports or the HTTP listener can prevent remote clients from reaching WMS even if local loopback appears to work. (learn.microsoft.com)

Quick diagnosis checklist (run as Administrator):

  • Confirm WMS service state and which process owns the streaming ports:

    netstat -anob | findstr /R "(:80|:1755|:554)"
tasklist /svc | findstr /I "wmserver"

    If inetinfo.exe / w3wp.exe or System owns port 80, IIS is intercepting HTTP traffic. Check Application and System event logs for WMS errors (look for NSE* codes); NS_E_INCOMPATIBLE_PUSH_SERVER explicitly means an HTTP push was received by IIS instead of WMS. (learn.microsoft.com)

Common, practical fixes

  • Give IIS and WMS separate IP: bind IIS sites to a dedicated IP (IIS Manager → Web Sites → Properties → Advanced → select IP) and configure WMS HTTP control protocol to allow only the other IP(s). Alternately, leave IIS on its IP and change WMS HTTP port to an alternate port if HTTP streaming is required. The WMS MMC lets the HTTP Server Control Protocol be enabled/disabled and set to a different port or bound IPs. (flylib.com)
  • If HTTP streaming/push is not needed, disable the WMS HTTP Server Control Protocol plug‑in so IIS and WMS won’t collide. If WMS logging/ISAPI (nsiislog.dll) is present in IIS, ensure WMS hotfixes/patches are applied (MS security bulletins cover nsiislog.dll). (learn.microsoft.com)

Recommended sequence: capture netstat output, check WMS control‑protocol settings in the WMS MMC (bound IPs/port), then either isolate IIS to a different IP or change the WMS HTTP port / disable the HTTP plug‑in. Back up WMS/IIS config before making changes and watch WMS/IIS and System event logs for immediate errors. This approach addresses the scenario described by and follows the typical resolution paths other responders hinted at (separate IPs or changing ports). (daniweb.com)

Recommended Answers

All 3 Replies

Member Avatar for goldeagle2005

can you provide more details as to what exactly youre doing and what you've done to rectify the problem? I may be able to help you out then

Member Avatar for techniner

So standlone they work together they do not?

Member Avatar for Aestivalis

If only Windows Media Services is installed, it works. If I install IIS, IIS works fine, but any reference to mms://servername/filename fails. From the server itself, it appears that mms://127.0.0.1/filename works, but that doesn't help.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.