Streaming HTTP via WMS & log question.

On Tue, 11 May 2010 13:52:10 -0700 (PDT), The ants are driving me
crazy wrote:

I have a WMV file on a wms 9 box that I can access thru a url in
either of these forms: mms://server/directory/video.wmv or
rtsp://server/directory/video.wmv. I can't play the video via http
though (http://server/directory/video.wmv). Is this because the WMS
HTTP Server Control Protocol plug-in is not enabled?

It could be that, although I think it's enabled by default in windows
server 2003 R2 release (I'd need to check with a fresh install as it's
something I enable immediately when I install WMS so it's hard to be
sure)

More often, people are also running a web server on the same machine
as the media server, on port 80. That cannot be shared on the same IP
address - if the web server starts first, then the media server can't
allocate port 80 and the HTTP protocol is disabled.

In that case you either need to have the web server on a different
port such as 8080, or bind another IP address for it or the media
server - either dual homed network cards, or bind 2 IP addresses to
the single public NIC and allocate one to the media server, the other
to the web server.

Instructions for doing that are here :
http://support.microsoft.com/kb/328728

My other quesion has to do with the log file. The cs-user-name field
in the log file is blank. How can I get wms to fill in this field?

The WMS authentication plugin woud need to be enabled for WMS to fill
in this value - however that only works with windows clients (WMP /
Silverlight) which can ask the user to provide authentication
credentials.

You'd need (I think) negotiate and/or digest authentication as
anonymous probably wouldn't get you this data.

Final question. Can either of the above items be set per publishing
point? We are sharing the server.

The protocol binding is per-server not per-publishing point, although
it's recommended to use HTTP if possible as this gets the media past
restrictive corporate firewalls which don't permit RTSP streaming
content. I don't know of a specific downside to enabling this for the
server for anybody's stream, though you'd have to check the contract.

Authentication / authorisation can be enabled per-publishing point so
yes that should be fine.

HTH
Cheers - Neil

Digital Media MVP : 2004-2010
http://mvp.support.microsoft.com/mvpfaqs