|Subject:||WMS connection problem (only works when IIS6 is started)|
|Posted by:||Ken L (email@example.com)|
|Date:||Fri, 27 Jul 2007|
I have a problem connecting to WMS that only seems manifest itself when I
shut down the IIS server running on the same machine . . .
Here is the configuration
Win2003 Server R2 Standard w/SP2
- Machine runs multiple services and has multiple IP addresses on it's
"public" facing NIC, lets call them IPAddr1 (WMS) and IPAddr2 (IIS)
Win Media Server 9.0
- Several remote media encoders are sending live video streams via HTTP
protocol to the server via IPAddr1. This is working just fine.
- Media Player clients connect to this server to play these live streams
- HTTPCFG was used to disable socket pooling and set up http.sys listener
on IPAddr2 for the web transactions (which are for a separate
applications and are not related in any way to the Media Stream server
- Win Mobile 5 PDA's accessing the media stream through IPAddr1 using MMS
- Win Media Players (Win XP, Win 2000, variety of releases) using MMS and
RTSP protocols through the same IPAddr1 assigned to WMS.
- Connection to the WMS is driven by URL's (with MMS service moniker)
embedded in web pages running on a web site on a completely different
We see slow startup connections or no connections from the desktop OS,
and no connections at all from the PDAs when we have
stopped the IIS web server on the machine (although the HTTP.SYS
and IIS admin services are still running).
If I start a web server instance, all the connection problems go away.
I am confused by this. Other than both utilizing port 80, I did not think
there was any interaction between IIS and the Media server.
Can anyone tell me whats going on here and what is causing the connections
to fail unless I have an IIS server instance started?
I've checked the port and address assignments and IPAddr1 and IPAddr2 are
segregated from each other and only assigned to WMS and IIS, respectively.
Thanks in advance for any assistance. Please post responses to the