>I am trying to setup a multicast live broadcast using pull from the encoder -
>and I get this error code on the Windows Media Server. I am using the
>http://IP:port in the encoder - other desktops can connect to it, but the WMS
>can't.
>I can stream archived files as live with no problems, just not from an
>encoder.
It seems fair to imagine then that there's a routing problem between
the server and the encoder. Can you ping the encoder PC box using it's
IP address, from the server ?
You should be able to ping it, which would indicate a valid router
path form the server end, it's quite possible the server is on a
subnet or external network which can't "reach" your encoder - whereas
these "desktops" are probably on the same subnet as the encoder PC
HTH
Cheers - Neil
------------------------------------------------
Digital Media MVP : 2004-2007
http://mvp.support.microsoft.com/mvpfaqs
whfropera - 29 May 2007 01:19 GMT
Hi neil -
Thanks for the reply! :)
It turns out that I can't ping the server from the encoder?
Suggestions?
I used this document to open the ports?
http://www.microsoft.com/windows/windowsmedia/forpros/serve/firewall.aspx#Encoder
Thanks, wod
> >I am trying to setup a multicast live broadcast using pull from the encoder -
> >and I get this error code on the Windows Media Server. I am using the
[quoted text clipped - 17 lines]
> Digital Media MVP : 2004-2007
> http://mvp.support.microsoft.com/mvpfaqs
whfropera - 29 May 2007 14:57 GMT
Now I can ping, but still can't connect - get same connection error.
> Hi neil -
>
[quoted text clipped - 28 lines]
> > Digital Media MVP : 2004-2007
> > http://mvp.support.microsoft.com/mvpfaqs
Neil Smith [MVP Digital Media] - 30 May 2007 19:47 GMT
OK 2 more network tests to try :
(1) Do tracert from the server box to the encoder - it uses different
packet types to ping (ICMP)
(2) Do telnet from the server to the encoder : The encoder must be
running for this test. To achieve this from a command window
telnet ip_address_of_encoder_pc encoder_port
(eg telnet 192.168.10.102 8080)
Then when the window goes blank, type or cut/paste the text
GET / HTTP/1.0
Press enter twice (you'll probably not be able to see the text, but
it's sent to the encoder's http service when you press enter)
If you see a response like "Bad Request ... Rex Server" then you know
for sure you've connected to the encoder service, so the problem must
lie elsewhere.
HTH
Cheers - Neil
>Now I can ping, but still can't connect - get same connection error.
>
[quoted text clipped - 30 lines]
>> > Digital Media MVP : 2004-2007
>> > http://mvp.support.microsoft.com/mvpfaqs
------------------------------------------------
Digital Media MVP : 2004-2007
http://mvp.support.microsoft.com/mvpfaqs