How do connect 2 WM Servers (ver. 9) for purposes of rollover (i..e if one
is unavailable or has hit its max bandwidth connect to the other).  Is this
possible?  If not, what are some of the things I can take advantages of by
having 2 separate WM Servers?

I have opened ports 1755, 554, 5005 with both TCP and UDP protocols
and still I can only stream within the network and not to external
clients. Any advice out there?

I can stream within the network using windows media server, however
external clients are getting the " cannot connect to server error". I
opened port 1755 recomended for windows media player and still cannot
serve video or audio to external clients. Please help,

Howdy again gang,
Does anyone know if there is a setting or reghack that I could use to limit
the number of player connections allowed per IP address in WMS9? I know how
to block addresses entirely, but I've not found anything that would let me

I believe I have everything set up Ok.  I run the wizzard in media server
pick the directory, pick the asf file, etc.  At the end, it gives you a
chance to test the asx file and the htm file.  They both work fine and the
windows media player comes up and plays my asf file.  I go to ...

My streaming server runs a webcam (see signature for URI). I want to
have a backlog of 2 or 3 days of video. At my current bitrate, this will
take up about 20 Gb of space per day. Since I have apr. 100 Gb free,
this should not be a problem.

I recently installed Windows Server 2003.  I have WMS and
IIS both installed.  I have two different IPs running on
this machine.  IIS is on one IP on a different port
number other than 80.  Windows Media still wants to try

Hello
i'm looking for a sollution to start publishing points
remotely.
I have found a script that remotely start the media

I enabled logging in the Server tab of the Windows Media Administrator, but
after a broadcast with many listeners, there are no values for the total
clients field, in fact no data other than a time and date stamp. I tried
setting it up to log monthly and daily, with the same results ...

It appears that you cannot set up an encoder push and a multicast using WM9 Encoder and WMS 9 Enterprise Edition.
It's too bad. The scenario for this was from behind a corporate firewall, I would push the encoder to a Internet based server, which could take advantage of Multicast ...

Under wms 4.1 I could turn the connection to the encoder
on and even get an error message when the encoder was not
streaming live content.  But when the encoder started
broadcasting, the server automatically noticed and went

I am running a WMS9 on W2K3/Enterprise server. Works great, I use it
for streaming live content, and was thinking of archiving the
material.
I set up the WMS Archive Data Writer for the live publishingpoint, and

We are thinking of using Windows Media to encode a live stream onto disk for
a slight delay.
For example, a 30 minute program starts at 11:00 AM.
In another venue, they are starting at 11:15 AM.

When I brought up the steaming video issue, his initial reaction was it
would kill the network from mission critical tasks and it would cost a lot
for the storage. What I don't understand is: if it's for intranet, it's
50KB/sec and it can only be 250KB/sec if we have 5 concurrent ...

Hai,
For the following setup
Win2000 using wmesdk ,two encoding sessions to the win2003 server
WM9Server