More questions though I think I'm getting closer.
I have WMS HTTP Server Portocal enabled and restricted to
one IP. Now I'm still a bit lost with three things...
1) Does the publishing point name in WME(9) need to match
the publishing point name on the WMS server? (i think it
does)
2) I get a network error when trying to publish using port
7007. (DSL + Router)
3) In WMS the push would look like push:stones
4) In WMS do I need to setup my anoucement. Currently it
looks like this. mms://CLH-1/stones (is this right?)
Thank you,
Jon C.
Ravi Raman - 26 May 2004 16:06 GMT
What version of the WM Server are you using?
Thx,
Ravi
>-----Original Message-----
>More questions though I think I'm getting closer.
[quoted text clipped - 18 lines]
>
>.
anonymous@discussions.microsoft.com - 27 May 2004 07:47 GMT
Thank you for responding again Ravi.
Runing 2k Pro for the Encoder 9 (push)
Server 2003 with WMS 9 + patch
I have a couple more questions.
If I try and change WMS port to 80 I get and error saying
IIS is already using it.
I used the HTTPsys confirgure tool and only add the IP for
WMS. I have IIS running websites and have some using (*all
unasigned) as virtual sites.
Can I disable IIS using a specific IP?
I think this is my major problem.
jc
>-----Original Message-----
>What version of the WM Server are you using?
[quoted text clipped - 26 lines]
>>
>.
Jon Chambers - 27 May 2004 09:33 GMT
I got it, I got it! Finally!!!
Thank you for your help.
I was using the HTTPsys config backwards. D-oh!
I'm sure I will have more questions in the future.
Thanks again Ravi.
jc
>-----Original Message-----
>What version of the WM Server are you using?
[quoted text clipped - 26 lines]
>>
>.
Ravi Raman - 26 May 2004 16:21 GMT
I presume all your questions involve push and not pull
distribution.
The authorization on who can push and who cannot is
controlled by the "WMS Publishing Points ACL
Authorization". By default,Administrators can push and
create new publishing point as they have the write and
create access.
1. The answer is not necessarily. Like I said above, it is
possible for the encoder to create a new publishing point
on the fly - so if you specify a new publishing point and
you have the access to create new publishing point, then a
new publishing point will be created.
2. Port 7007 is not used anymore as the MSBD protocol is
being deprecated. Only HTTP push is allowed, so you should
push to port 80 (if your server is running on port 80).
3. I believe the source of your publishing point should
always be push:*
4. Announcement is so that you generate an ASX metafile
that the player would use to connect. If your publishing
point is called stones and CLH-1 is your server, then your
announcement looks good - but only for intranet. If you
will publish this URL on the internet, then your
announcement should have the fully qualified domain name
of your CLH-1 server.
Hope this helps.
Ravi
--
This posting is provided "AS IS" with no warranties, and
confers no rights.
>-----Original Message-----
>More questions though I think I'm getting closer.
[quoted text clipped - 18 lines]
>
>.