WMS connection problem (only works when IIS6 is started)

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

Server
-----------

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

IIS6
- 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
streams)


Client-side
-------------------

- Win Mobile 5 PDA's accessing the media stream through IPAddr1 using MMS
protocol
- 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
machine/server.


Symptoms
-------------------
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
newsgroup.

Ken

RE: WMS connection problem (only works when IIS6 is started)

Hi Ken,

Basically this should be a WMS issue instead of an IIS one.

I will help forward your question to our WMS group for consultation. If
there is any update from there, I will post here to let you know.

Have a good day.

Sincerely,

WenJun Zhang

Microsoft Online Community Support

==================================================

Get notification to my posts through email? Please refer to:
http://msdn.microsoft.com/subscriptions/managednewsgroups/de fault.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at:

http://msdn.microsoft.com/subscriptions/support/default.aspx .

==================================================

This posting is provided "AS IS" with no warranties, and confers no rights.

RE: WMS connection problem (only works when IIS6 is started)

Hi Ken,

I've confirmed with our Media Server group. This is not typical behavior.
Below are some suggestions from them to start the troubleshooting:

1) Check under
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WMServe r for the
settings of DependOnService and make sure that only RPCSS is listed.

2) Can you make port connections to any of the WMS ports (80, 554,
1755) when IIS is stopped? Try using the following command line and just
look for a connection:
telnet 1.1.1.1 554
Where 1.1.1.1 is the IP address of the WMS server.

3) Instead of using httpcfg or wmshttpsyscfg to set the IP addresses,
I prefer installing the fix KB 892847 (included in Winsows 2003 SP2) to
allow you to disable endpoint sharing via the registry. This makes it much
easier to configure WMS and IIS. Whatever you set in the UI, is what is
actually honored by HTTP.sys.

I look forward to your update.

Thanks and have a great day.

Sincerely,

WenJun Zhang

Microsoft Online Community Support

==================================================

Get notification to my posts through email? Please refer to:
http://msdn.microsoft.com/subscriptions/managednewsgroups/de fault.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at:

http://msdn.microsoft.com/subscriptions/support/default.aspx .

==================================================

This posting is provided "AS IS" with no warranties, and confers no rights.