Re: WME Error 0xC00D2F0B

Tech-Archive recommends: Fix windows errors by optimizing your registry

On Tue, 06 Jun 2006 21:13:08 GMT, "Neil Smith [MVP Digital Media]"
<neil@xxxxxxxxxx> wrote:

On Tue, 06 Jun 2006 10:37:38 -0400, Drew <drew.winter@xxxxxxxxx>
wrote:

I am running WMS on 2003 server without any troubles. i have other
customers connected OK, but I have a new customer connecting and then
they get disconnected with the error:

Unable to establish a connection to the server. Ensure Windows Media
Services is started and the HTTP Server control protocol is properly
enabled. (0xC00D2F0B)

Can anyone point me in the right direction to a solution?


Yes, you are probably running IIS on port 80 on that server.

I'm assuming that all your other live publishing points to date have
been Pull rather than Push from encoder.

You should check first, by opening the administration pages for WMS,
go to the top level server section and look at the Properties tab.

The first item on there, "WMS HTTP Server control protocol" may have a
red X next to it, which usually indicates a port conflict and is
usually cause by conflicting port 80 usage (so the service is not
started).

If you're unable to Start that service, right click the HTTP control
protocol and choose Properties, change the port selection to (other
than port 80) : 8080 is also popular as it can often traverse
firewalls at the encoder end.

You'll also probably have top open that port in the windows firewall
if you haven't added WMS to the applications list of the firewall (you
should anyway ;-)


The customer is using WME to push the stream to the server when they
get this error on their end.

The next step would be to inform the client of the new setting -
they'd then choose in WME's output tab for Server Name *both* server
name *and* port, so say your server is at 141.200.50.100, they'd
specify to push to 141.200.50.100:8080 (because the default port 80
doesn't usually need to be specified)

When I view ther stream throough IE it buffers often which makes the
stream choppy as well.

You can't view the stream "through" IE, it must be viewed through WMP
or similar - is that what you meant ?

How's their outgoing bandwidth supplied by their ISP compared to the
stream rate they're trying to source ? Are you sure their encoder PC
can keep up with the data source and compression they're trying to
achieve ?

HTH
Cheers - Neil

Thanks for all the feedback Neil. All of my streams are push from
encoder, and the port is already on an alternate setting. I did find
out that the encoded stream is coming from south america, so I have no
idea what type of internet connection they are uploading with, my
guess is that its not the best.

The streaming server is a 2.0 Ghz Celeron with 1 Gb of RAM. Is there a
formula to calculate the total amount of streams it can handle at the
same time? The streams all vary in their length and quality, but there
are rarely more than 20-30 simultaneous people viewing the streams.

Any other suggestions?

Thanks again for the input!


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

Relevant Pages

  • RE: Streaming to firewall users.
    ... comes with Windows Server 2003). ... mechanism where it tries RTSP on port 554 and if that fails, ... I've set up a streaming server to stream mp3s to myself and few of my ... > Windows Media streams just fine. ...
    (microsoft.public.windowsmedia.server)
  • RE: Streaming to firewall users.
    ... Server A is running WS2003 and WME9 and is on a cable ... broadcasting via http. ... I need to run http on another port than 80 because I have IIS ... She was able to connect to the stream. ...
    (microsoft.public.windowsmedia.server)
  • Re: WMP 11 Problem in playing MMS
    ... streaming server is also under my control and it's a Win2K server running ... Windows Media Services. ... The HTTP port has been used by the IIS. ... You'd have to contact the provider of the stream. ...
    (microsoft.public.windowsmedia)
  • Re: WME Error 0xC00D2F0B
    ... but I have a new customer connecting and then ... Unable to establish a connection to the server. ... you are probably running IIS on port 80 on that server. ... You can't view the stream "through" IE, it must be viewed through WMP ...
    (microsoft.public.windowsmedia.server)
  • WME Error 0xC00D2F0B
    ... I am running WMS on 2003 server without any troubles. ... but I have a new customer connecting and then ... The customer is using WME to push the stream to the server when they ...
    (microsoft.public.multimedia.windows.mediaplayer)