Bruce,
Have you created a Broadcast publishing point or an on
demand publishing point? If it is broadcast, then is
there a specific reason why you chose broadcast instead
of on demand?
Presuming your content is yourfile.wmv, and you have it
in your root folder (which could be, for eg.,
c:\wmpub\wmroot), all you have to do to stream this is
to "Allow connections" on the default publishing point
and play content from your player as
mms://yourservername/yourfile.wmv and it should stream
content.
If you can't make this to work, please add more info
about your setup.
Thx,
Ravi
--
This posting is provided "AS IS" with no warranties, and
confers no rights.
>-----Original Message-----
>setup: Windows 2002 Standard edition, only using Windows
media server.
>Serving a single file from the windows media root folder. A basic file served up.
>
>problem: I start the media server. One person connects and then if that person or any other system connects the
media player immediately tries to connect and then
returns "stopped". The server publishing point is still
running. If I stop and start the publishing point or the
server. The the first system that logs on serves fine.
>Look for help or any one with experience with this issue.
>.
bckwheat - 27 Apr 2004 03:49 GMT
Hi Ravi
Thanks for the reply. I am not sure that I follow you. I
currently have a publishing point that when I first start
the media server and the then start the "on demand"
publishing point "currently called beavervdo", a secondary
client machine can connect and watch the video. The
problem seems to occur shortly after that. If I go back
to that publishing point 5 minutes later, the media player
tries to connect and returns "stopped". If I restart the
publishing point and or the server, it works. I can log
on 2 and 3 clients at a time when I first start up but
after I close the media player it eventually stops
buffering and thus playing. There are no errors in the
log, and the publishing point still indicates its
running. ??????
bruce
>-----Original Message-----
>Bruce,
[quoted text clipped - 39 lines]
>>
>.
Ravi Raman - 27 Apr 2004 06:58 GMT
Hi Bruce,
You should look up the difference between a "on demand"
and a "broadcast" publishing point on the WIndows Media
Help documentation. Unless I am misunderstanding you, you
seem to have broadcast publishing point (only a broadcast
publishing point can be "started" - hence my conclusion).
Can you confirm that you indeed have a broadcast
publishing point? The icons for on demand and broadcast
publishing points are different, so you can find it out
on the administrator. For example, on Windows Server 2003
default server installation, the "<Default>" publishing
point is "On demand", and the "Sample Broadcast"
publishing point is a "Broadcast" publishing point.
I am thinking that you have a file that is approx. five
minutes in length and you have a broadcast publishing
point setup instead of an on demand publishing point. So,
anybody who connects after 5 minutes sees nothing
(because the file has ended past the "broadcasting" point
and client simply receives nothing, so it stops).
You should probably recreate your publishing point as
a "on demand" publishing point (you can use the wizard to
create publishing points in which case the wizard will
ask for whether you want on demand or broadcast
publishing point) and try the same scenario.
Hope this makes sense.
Ravi
--
This posting is provided "AS IS" with no warranties, and
confers no rights.
>-----Original Message-----
>Hi Ravi
[quoted text clipped - 58 lines]
>>
>.
bckwheat - 27 Apr 2004 23:43 GMT
YOU DA MAN (oops PERSON). I duplicated the "on-demand"
publishing point and pointed the source to my file and
guess what? Works as advertised. A quick question
though, would you use the broadcast publishing point
exclusively for a live stream?
Thanks for the help
>-----Original Message-----
>Hi Bruce,
[quoted text clipped - 108 lines]
>>
>.
Ravi Raman - 28 Apr 2004 02:39 GMT
Glad I could be of help.
Yes, Broadcast is typically used for a "live" scenario -
it is a shared experience. The "Concepts" section in the
help documentation of Windows Media Server explains this
with good examples.
Ravi
---
This posting is provided "AS IS" with no warranties, and
confers no rights.
>-----Original Message-----
>YOU DA MAN (oops PERSON). I duplicated the "on-demand"
[quoted text clipped - 118 lines]
>>
>.