Network share as a Publishing Point source
From: Ravi Raman (ravira_at_Online.microsoft.com)
Date: 09/23/04
- Next message: Steve Adams: "Network share as a Publishing Point source"
- Previous message: Steve Adams: "Network share as a Publishing Point source"
- In reply to: Steve Adams: "Network share as a Publishing Point source"
- Next in thread: Steve Adams: "Network share as a Publishing Point source"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 23 Sep 2004 11:26:26 -0700
If the service won't start, then very likely that you
missed setting one of these things that is mentioned in
the article:
Give the common user appropriate permissions on folders,
services, registry keys, and processes that Windows Media
Services logs on to, including the following:
1. Read permission on the sources of all on-demand
publishing points, including the default folder WMPub.
2. Read permission on the following registry key, in order
for anonymous username, distribution, and proxy
credentials to be read:
HKLM\Software\Microsoft\Windows
Media\Server\Namespace\Storage
3. Write and modify permissions on the folder and
subfolders of: %windir%\system32\windows media\server.
4. If logging is enabled, write and modify permissions on
the folder: %windir%\system32\LogFiles\WMS.
5. If archiving is enabled, write and modify permissions
on the folder: %systemdrive%\wmpub\WMArchive.
Just to confirm: Using a "mapped" drive letter is a no go
with WMS. You HAVE to use the full drive names (like \\d3
\c that you mention). I am not sure how the wizard looks
into it. Let me know if you can't get it to work, I can
suggest a few more things and make it work.
Thx,
Ravi
-- This posting is provided "AS IS" with no warranties, and confers no rights. >-----Original Message----- >Ravi, > >When I posted I had not changed the account the service >logged under since it didn't seem that leaving the >original account would keep me from mapping a publishing >point to the remote share in the Wizard. I finally was >able to map the publishing point to the share (still using >the original login account) by not using the wizard. The >wizard appears unable to display shares as options for a >publishing point source, or to even take the full UNC name >of the share. > >But I still could not reach the share from a client player >so I then proceeded to follow the instructions in the >section you mentioned and changed the service logon >account to a new account - WMServer - I set up with a >password. Now the service won't start! > >Steve > > >>-----Original Message----- >>Have you actually checked this section where both the >>machines are in a workgroup: >>http://www.microsoft.com/windows/windowsmedia/howto/artic l >e >>s/SourcingRemoteContent.aspx#serverremotedeviceorbothinwo r >k >>groups >> >>So, what account is your service currently running under? >>Did you create a new wmserver account? >> >>Thx, >>Ravi >>-- >>This posting is provided "AS IS" with no warranties, and >>confers no rights. >>>-----Original Message----- >>>I tried setting up a remote share for WM9 Services, >>following the >>>article below that David Chen gave to Blake Crosby on >>9/16/2004, but >>>had trouble from the start. I mapped a directory on a >>remote computer >>>to the drive letter "Z:" at the WM9 Server. The remote >>computer and >>>the WM9 Server are in the same Workgroup. But when I >try >>to create a >>>publishing point referencing this remote directory, the >>mapped letter, >>>Z, does not show up in the pull down menu that drops >from >>the browse >>>window. If I type Z:\ into the source field anyway, I >get >>the message, >>> "The URL you specified is not valid." If instead of >>using "Z:\" I >>>enter the \\D3\c, which Z maps to, I get the same >>message. I've tried >>>rebooting. I know the share is working because on the >WM9 >>Server I can >>>see the share when I open My Computer, and I can rename >>files on the >>>share from a command window at the WM9 Server using just >>the drive >>>letter Z:\. >>> >>>This problem seems a long way before any issues about >>clients having >>>correct rights to access the remote share - the thrust >of >>the article >>>- since there are no clients in the picture yet. At any >>rate, I have >>>disabled the WMS NTFS Authorization for the WM9 Server, >>as per the >>>article, and enabled it for the publishing points not >>using the >>>remote share. At the remote computer I have allowed >>Everyone all >>>permissions on the share, just to get the share working >>for now. >>> >>>Thanks for any help on this, >>>Steve Adams >>>. >>> >>. >> >. >
- Next message: Steve Adams: "Network share as a Publishing Point source"
- Previous message: Steve Adams: "Network share as a Publishing Point source"
- In reply to: Steve Adams: "Network share as a Publishing Point source"
- Next in thread: Steve Adams: "Network share as a Publishing Point source"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
