windows media server questions

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Luke - 19 May 2004 14:49 GMT

Hi
I have a pc (called A) with a webcam and windows media encoder, and another
pc (called B) with win2003 server where i have also windows media service.
I configured pc A this way:
Source: webcam
Push to server ---> ip server (pc B)
publishing point: test

when i start encoding in pc B i can see the publishing point just created.
How can i set permissions in order to let only some users to publish to my
server? I would like to create an account on pc B and let only some users
use that account to push to my server. Is it possible? Otherwise everyone
can connect to my server, isn'it?

Another question:
If i create a publishing point directly on pc B then i must to have a file
as source or i can set also the webcam on the pc A as a source?
I ask this because every time i create a publishing point on pc B it asks me
for a file or a directory

thanks

Luke

Reply to this Message

Ravi Raman - 19 May 2004 19:29 GMT

I presume you have not reset any of the authorization or
authentication plug-ins in the server.

If so, you were able to successfully push from PC A to PC
B only because you were logged in on PC A as some user
belonging to administrators group on machine B. You can
try testing by logging yourself off on PC A, and logging
in as an user on PC A who doesn't have Administrator
access on PC B and try pushing to PC B - you will get an
authentication prompt.

The permission settings are on the Server->Properties-

>Authorization->"WMS Publishing Points ACL Authorization".

You can see that Administrators have Read/Write/Create
access. The write and create access controls who can push.
You can add or remove users to as per your needs.

As for your second question:
You can set a publishing point to source from the encoder.
Your encoder should run in "Pull" mode on a valid port on
the PC A (let us say the encoder runs as
encoder.yourdomain.com on port 80). You need to create
a "Broadcast publishing point" (since a webcam is
typically a broadcast) and in the source path you mention
http://encoder.yourdomain.com:80 and start it.

Hope this helps.
Ravi
--
This posting is provided "AS IS" with no warranties, and
confers no rights.

>-----Original Message-----
>Hi
[quoted text clipped - 22 lines]
>
>.

Reply to this Message

Luke - 20 May 2004 08:52 GMT

Hi Ravi and thanks
The problem is that i didn't log on the PC A as a user belonging to
administrators group on machine B. In fact the pc A is my pc at work and i
log in the domain, the pc B is my home PC. I understand the user permission
on the server (B), but i don't know how a client that want to push to my
server can log as a user defined on it.
If i have a pc in a LAN and i want to log on a server, i can insert username
and password of the server and so i can login. but how can i do that from
The media Encoder of a client? Is there the possibility to push also a
username and a password to the server?
This is what i don't understand.

thanks

> I presume you have not reset any of the authorization or
> authentication plug-ins in the server.
[quoted text clipped - 63 lines]
> >
> >.

Reply to this Message

Ravi Raman - 20 May 2004 19:06 GMT

I am not sure what exactly is happening in your case but
here is what generally happens with push distribution:

1. One the server, the server level "WMS Publishing Points
ACL Authorization" should be enabled - this is very
important. If it is disabled, nothing gets checked and
anyone can push.
2. When the encoder pushes, first Anonymous authentication
plug-in is used. Since Anonymous user is denied access in
the Publishing Points ACL (Write and Create access is only
there for Administrators - not Anonymous users), the next
authentication will be tried. By default, WMS Negotiate
authentication is enabled.
3. So, the encoder will get challenged with WMS Negotiate
Authentication. Since your Encoder PC is not in a domain,
it will use NTLM - the encoder will provide your NTLM
Logged on credentials (if your IE settings allows it to).
If the credentials has valid write/create access on
server, you will be able to push.
4. If the user does not write/create access, then the
encoder will be challenged again and the encoder will
prompt you with a dialog box asking for username and
password. Here you get a chance to enter the credentials
in the dialog box. Again, if you provide a valid
username/password with write access it will work - if not
it will fail again.

Hope this makes sense. I am not sure what part is breaking
for you as I do not have more info on your complete server
setup etc.

Ravi
--
This posting is provided "AS IS" with no warranties, and
confers no rights.

>-----Original Message-----
>Hi Ravi and thanks
[quoted text clipped - 80 lines]
>
>.

Reply to this Message