Setup of our first Simple Broadcast White Rock 27.06.2007 05:56:02 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 -- Developing Peopleware Solutions with Microsoft Framework

Re: Setup of our first Simple Broadcast "Mike Lowery" <selfspam[ at ]mouse-potato.com> 27.06.2007 14:17:31 "White Rock" <daveh[ at ]ergometrek.net> wrote in message news:BB4C247C-B915-407E-A8F8-6295ACCBF359[ at ]microsoft.com... [Quoted Text] > 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 What is your server's DNS name on the Internet?

Re: Setup of our first Simple Broadcast White Rock 27.06.2007 15:36:05 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? -- Developing Peopleware Solutions with Microsoft Framework "Mike Lowery" wrote: [Quoted Text] > > "White Rock" <daveh[ at ]ergometrek.net> wrote in message > news:BB4C247C-B915-407E-A8F8-6295ACCBF359[ at ]microsoft.com... > > 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 > > What is your server's DNS name on the Internet? > > >

Re: Setup of our first Simple Broadcast "Mike Lowery" <selfspam[ at ]mouse-potato.com> 27.06.2007 21:48:38 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. "White Rock" <daveh[ at ]ergometrek.net> wrote in message news:24FAAB23-7888-4E0F-AE45-8CC61A5934B8[ at ]microsoft.com... [Quoted Text] > 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? > -- > Developing Peopleware Solutions with Microsoft Framework > > > "Mike Lowery" wrote: > >> >> "White Rock" <daveh[ at ]ergometrek.net> wrote in message >> news:BB4C247C-B915-407E-A8F8-6295ACCBF359[ at ]microsoft.com... >> > 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 >> >> What is your server's DNS name on the Internet? >> >> >>

Re: Setup of our first Simple Broadcast White Rock 28.06.2007 06:06:00 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 "Mike Lowery" wrote: [Quoted Text] > 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. > > "White Rock" <daveh[ at ]ergometrek.net> wrote in message > news:24FAAB23-7888-4E0F-AE45-8CC61A5934B8[ at ]microsoft.com... > > 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? > > -- > > Developing Peopleware Solutions with Microsoft Framework > > > > > > "Mike Lowery" wrote: > > > >> > >> "White Rock" <daveh[ at ]ergometrek.net> wrote in message > >> news:BB4C247C-B915-407E-A8F8-6295ACCBF359[ at ]microsoft.com... > >> > 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 > >> > >> What is your server's DNS name on the Internet? > >> > >> > >> > > >

Re: Setup of our first Simple Broadcast "Mike Lowery" <selfspam[ at ]mouse-potato.com> 28.06.2007 15:21:25 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 "White Rock" <daveh[ at ]ergometrek.net> wrote in message news:BD55ECF6-DE90-4C31-89E0-2D54CF7ADE10[ at ]microsoft.com... [Quoted Text] > 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 > > > "Mike Lowery" wrote: > >> 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. >> >> "White Rock" <daveh[ at ]ergometrek.net> wrote in message >> news:24FAAB23-7888-4E0F-AE45-8CC61A5934B8[ at ]microsoft.com... >> > 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? >> > -- >> > Developing Peopleware Solutions with Microsoft Framework >> > >> > >> > "Mike Lowery" wrote: >> > >> >> >> >> "White Rock" <daveh[ at ]ergometrek.net> wrote in message >> >> news:BB4C247C-B915-407E-A8F8-6295ACCBF359[ at ]microsoft.com... >> >> > 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 >> >> >> >> What is your server's DNS name on the Internet? >> >> >> >> >> >> >> >> >>

Re: Setup of our first Simple Broadcast White Rock 29.06.2007 18:32:00 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 -- Developing Peopleware Solutions with Microsoft Framework "Mike Lowery" wrote: [Quoted Text] > 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 > > "White Rock" <daveh[ at ]ergometrek.net> wrote in message > news:BD55ECF6-DE90-4C31-89E0-2D54CF7ADE10[ at ]microsoft.com... > > 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 > > > > > > "Mike Lowery" wrote: > > > >> 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. > >> > >> "White Rock" <daveh[ at ]ergometrek.net> wrote in message > >> news:24FAAB23-7888-4E0F-AE45-8CC61A5934B8[ at ]microsoft.com... > >> > 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? > >> > -- > >> > Developing Peopleware Solutions with Microsoft Framework > >> > > >> > > >> > "Mike Lowery" wrote: > >> > > >> >> > >> >> "White Rock" <daveh[ at ]ergometrek.net> wrote in message > >> >> news:BB4C247C-B915-407E-A8F8-6295ACCBF359[ at ]microsoft.com... > >> >> > 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 > >> >> > >> >> What is your server's DNS name on the Internet? > >> >> > >> >> > >> >> > >> > >> > >> > > >