>So - What happens when you shut down IIS on that box - does it work
>now ? I can't see why the encoder direct connection would ever cause
>an error, but since you didn't say what that "error" was ...
This W2k server plays a .WMV file just fine over windows media
server on port 1754, so I haven't tried to shut down IIS. Also, one
thing that is logged on the Windows Media server is the client
connection event but nothring else. The Windows Media player client
error follows - about as helpful as 'error'!! :-)
----------------------------------------------------------------------
Windows Media Player cannot play the file. If the file is on another
computer, verify that you are connected to the network. If you typed a
path, verify that it is correct. If the problem persists, the server
might not be available
C00D1197: Cannot play the file
Windows Media Player cannot play the file. You might encounter this
error message for one of the following reasons:
Your computer is not connected to the local area network (LAN) or to
the Internet. Connect to the network or Internet, and then try again.
The path to the file is not valid. If you typed a Uniform Resource
Locator (URL) in the Open URL dialog box, verify that the file name is
spelled correctly and that the path to the file is correct, and then
try again. If you clicked a link on a Web page, the link might not be
valid.
The server is not available (for example, the server is busy or not
online). Try again later.
Some network protocols in the Player are not enabled. Enable all
network protocols, and then try again.
The proxy server settings for the Player are not configured properly.
Verify that your proxy settings are correct, and then try again.
To enable all network protocols
On the Tools menu, click Options, and then click the Network tab.
In the Streaming protocols area, select all the protocol check boxes.
To verify your proxy server settings
On the Tools menu, click Options, and then click the Network tab.
Verify your settings in the Streaming proxy settings area.
Note
If you do not know what your proxy server settings should be, on the
Network tab, select a protocol, click Configure, and then select
Autodetect proxy settings or Use proxy settings of the Web browser
(available for HTTP protocol only).
Error ID = 0xC00D1197, Condition ID = 0x00000000
Web Help
Neil Smith [MVP Digital Media] - 01 Jan 2007 14:50 GMT
>>So - What happens when you shut down IIS on that box - does it work
>>now ? I can't see why the encoder direct connection would ever cause
>>an error, but since you didn't say what that "error" was ...
>
> This W2k server plays a .WMV file just fine over windows media
>server on port 1754, so I haven't tried to shut down IIS. Also, one
OK so we've confirmed that IIS is "intercepting" the port 80 request
to begin the Push stream to the server.
The options now are - go to the media server and configure http server
control protocol to listen on another port than port 80, or you can
set the server to listen on another IP bound to the network card - or
just use a second NIC for incoming encoder connections, making sure
IIS is configured *not* to listen to that IP.
>thing that is logged on the Windows Media server is the client
>connection event but nothring else. The Windows Media player client
[quoted text clipped - 37 lines]
>Error ID = 0xC00D1197, Condition ID = 0x00000000
>Web Help
------------------------------------------------
Digital Media MVP : 2004-2006
http://mvp.support.microsoft.com/mvpfaqs
Jeffery Jones - 01 Jan 2007 17:09 GMT
>OK so we've confirmed that IIS is "intercepting" the port 80 request
>to begin the Push stream to the server.
[quoted text clipped - 4 lines]
>just use a second NIC for incoming encoder connections, making sure
>IIS is configured *not* to listen to that IP.
This server is serving some web sites on port 80, so that cannot be
changed.
I did however find a way to tell Windows Media Encoder to push to
port 1755. This produced a message -
----------------
The network connection has failed (0xC00D0029)
---------
There was nothing relevant in any logs. A network packet trace showed
a connection to port 1755, this POST, followed by an immediate server
disconnect.
POST /abcstream HTTP/1.1
Content-Type: application/x-wms-pushsetup
X-Accept-Authentication: Negotiate, NTLM, Digest
User-Agent: WMEncoder/10.0.0.3708
Host: 192.168.47.221:1755
Content-Length: 0
Connection: Keep-Alive
Cache-Control: no-cache
Cookie: push-id=0
-----------------------------------------
I couldn't find a way to specify a 'push' type of connection to
Windows Media Server version 4.1 when setting up the broadcast
publishing point.
I'm guessing that Windows Media Encoder 9 is not compatible with
Windows Media Server 4.1/ Windows 2000? I can't find anything in the
docs either way or cannot find an old version of Windows Media Encoder
to try.
Jeffery Jones - 01 Jan 2007 21:59 GMT
> I did however find a way to tell Windows Media Encoder to push to
>port 1755. This produced a message -
I found that WMS 4.1 also opens port 7007, so I tried pushing to
that port with the same results.