Setup of our first Simple Broadcast

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

White Rock - 27 Jun 2007 06:56 GMT

We've followed the guides and have attempted our first publishing point with
WM Server on W2K3R2 Standard x64. Thou I think we started off with the wrong
Domain name. We called the server Alpha. We want the server to publish
content to Internet Client. When I look at the Direct connection using the
MMS protocol`` it reads mms://Alpha/Sample_Broadcast. How would a WMplayer
client resolve that address Do we need to change the server name...

Any assistance would be appreciated

Signature

Developing Peopleware Solutions with Microsoft Framework

Reply to this Message

Mike Lowery - 27 Jun 2007 15:17 GMT

> We've followed the guides and have attempted our first publishing point with
> WM Server on W2K3R2 Standard x64. Thou I think we started off with the wrong
[quoted text clipped - 4 lines]
>
> Any assistance would be appreciated

What is your server's DNS name on the Internet?

Reply to this Message

White Rock - 27 Jun 2007 16:36 GMT

Thanks for the reply. The server's DNS name is eigo-go.com We cannot edit
the direct connection string in the GUI 'Announce' Tab. which reads
mms://Alpha/Sample_Broadcast Is there something wrong with permissions or
the setup?

Signature

Developing Peopleware Solutions with Microsoft Framework

> > We've followed the guides and have attempted our first publishing point with
> > WM Server on W2K3R2 Standard x64. Thou I think we started off with the wrong
[quoted text clipped - 6 lines]
>
> What is your server's DNS name on the Internet?

Reply to this Message

Mike Lowery - 27 Jun 2007 22:48 GMT

It doesn't matter what the GUI says. Your server is listening on a port, not a
URL. You could specify an IP address and have it work--DNS isn't even
necessary. In your case you would want to specify your external DNS name (or
IP), not the internal server name.

> Thanks for the reply. The server's DNS name is eigo-go.com We cannot edit
> the direct connection string in the GUI 'Announce' Tab. which reads
[quoted text clipped - 13 lines]
>>
>> What is your server's DNS name on the Internet?

Reply to this Message

White Rock - 28 Jun 2007 07:06 GMT

Thanks for the reply. I have used the advise about outside dns. Todaye, I
have attempted to 'Announce' this publishing point using the 'Unicast
Announcement Wizard' with limited success. The wizard has a cool step for
editing the DNS within the announcement. After completing the announcement
with webpage I then navigated the server's browser to the Announcement page
- the media player renders and the publishing point works. When I attempted
to access from a client desktop outside the network. - The page renders with
the embedded player but the media connection fails. I have viewed the source
on the htm page and the reference is mms://eigo-go.com/Sample_Broadcast; I
looked at our setup with stopping anything wierd; Asked Our hoster and they
have openned port 1755.We have checked from the server using a port utility
to verify 1755. Do know why it not working. Any suggestion would be
appreciated

Developing Peopleware Solutions with Microsoft Framework

> It doesn't matter what the GUI says. Your server is listening on a port, not a
> URL. You could specify an IP address and have it work--DNS isn't even
[quoted text clipped - 18 lines]
> >>
> >> What is your server's DNS name on the Internet?

Reply to this Message

Mike Lowery - 28 Jun 2007 16:21 GMT

MMS is a deprecated protocol:
http://www.microsoft.com/windows/windowsmedia/licensing/netprokit.aspx

You should be allowing HTTP and/or RTSP as well:
http://www.microsoft.com/windows/windowsmedia/forpros/serve/firewall.aspx

> Thanks for the reply. I have used the advise about outside dns. Todaye, I
> have attempted to 'Announce' this publishing point using the 'Unicast
[quoted text clipped - 38 lines]
>> >>
>> >> What is your server's DNS name on the Internet?

Reply to this Message

White Rock - 29 Jun 2007 19:32 GMT

Thanks for the reply. We have setup the rtsp and http protocol. Is that
enough to create the rollover for WMP? Do we create another unicast
announcement or is the old one reuseable? The http is not on port 80<does
that matter>?
Any suggestion would be appreciated

Signature

Developing Peopleware Solutions with Microsoft Framework

> MMS is a deprecated protocol:
> http://www.microsoft.com/windows/windowsmedia/licensing/netprokit.aspx
[quoted text clipped - 44 lines]
> >> >>
> >> >> What is your server's DNS name on the Internet?

Reply to this Message