Network share as a Publishing Point source

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Steve Adams (stvadams_at_baydelna.com)
Date: 09/23/04

  • Next message: Ravi Raman: "Network share as a Publishing Point source" 
    Date: Thu, 23 Sep 2004 10:34:01 -0700

    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/articl
    e
    >s/SourcingRemoteContent.aspx#serverremotedeviceorbothinwor
    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: Ravi Raman: "Network share as a Publishing Point source"

    Relevant Pages

    • Re: How to remote access Windows XP Pro computer?
      ... you happen to use Norton Internet Security please read the following link. ... link for the remote person to access their system. ... "Is LogMeIn secure and what is SSL? ... separate passwords to access both your LogMeIn account and your Target ...
      (microsoft.public.windowsxp.work_remotely)
    • Re: RWW and Remote desktop stopped working on all clients
      ... After diggin through ALL the group policies, I found Remote ... Desktop DISABLED under the Account Lockout policy - I don't think I've even ... adminsitrator or another account with Domain Admin role; also the server ...
      (microsoft.public.windows.server.sbs)
    • Re: DomainLocalServer$ is not a valid user
      ... I have traced by SQL-profiler on remote computer. ... it's always traced the user account. ... Its Security is ... to use the current user credential to logon to the remote server. ...
      (microsoft.public.sqlserver.security)
    • Network share as a Publishing Point source
      ... what account is your service currently running under? ... >I tried setting up a remote share for WM9 Services, ... >to the drive letter "Z:" at the WM9 Server. ... At the remote computer I have allowed ...
      (microsoft.public.windowsmedia.server)
    • Network share as a Publishing Point source
      ... Give the common user appropriate permissions on folders, ... publishing points, ... >original account would keep me from mapping a publishing ... >>>I tried setting up a remote share for WM9 Services, ...
      (microsoft.public.windowsmedia.server)