Skip to main content
Participant
January 8, 2010
Question

Authentication issue accessing remote share

  • January 8, 2010
  • 1 reply
  • 813 views

I'm testing out Adobe Flash Media Server and Wowza Flash Server and am trying to accomplish the following... Web server and Flash server are on different computers... Flash server is configured to stream vod files (.flv) from a remote file share (UNC path) on a separate Windows domain server.

I was able to get both servers configured and working.  The final piece is to move both Flash servers to the DMZ segment of our firewall and test from outside our network.  On the DMZ, the Wowza Server is able to connect to the remote file share and stream video as it's apparently leveraging the credentials I entered when I mapped a network drive to the file share and supplied valid domain credentials.  The Adobe Flash Server is not able to connect to the remote file share and stream video because it seems that the connection method that the Adobe Flash Server uses is reliant upon the Adobe Flash Server Windows service account being a domain account... and when the server is on the DMZ it cannot access our domain controllers to authenticate.

Does anybody have any experience with this type of situation.?  Or know if there's a way for Adobe Flash Server to leverage drive mapping credentials as opposed to the credentials that it starts the Windows service with?

Thanks!

-Dave

    This topic has been closed for replies.

    1 reply

    January 12, 2010

    Dave,

    I assume your FMS box is Windows? How are you supplying the credentials for the remote share? Are you mapping a drive and then specifying the drive letter/path within your FMS configuration? What account are you having the FMS services start as? Have you tried using a fully-qualified path, such as \\SERVERNAME\SHARE\FOLDER?

    Best,

    RMT.

    dvwool wrote:

    I'm testing out Adobe Flash Media Server and Wowza Flash Server and am trying to accomplish the following... Web server and Flash server are on different computers... Flash server is configured to stream vod files (.flv) from a remote file share (UNC path) on a separate Windows domain server.

    I was able to get both servers configured and working.  The final piece is to move both Flash servers to the DMZ segment of our firewall and test from outside our network.  On the DMZ, the Wowza Server is able to connect to the remote file share and stream video as it's apparently leveraging the credentials I entered when I mapped a network drive to the file share and supplied valid domain credentials.  The Adobe Flash Server is not able to connect to the remote file share and stream video because it seems that the connection method that the Adobe Flash Server uses is reliant upon the Adobe Flash Server Windows service account being a domain account... and when the server is on the DMZ it cannot access our domain controllers to authenticate.

    Does anybody have any experience with this type of situation.?  Or know if there's a way for Adobe Flash Server to leverage drive mapping credentials as opposed to the credentials that it starts the Windows service with?

    Thanks!

    -Dave

    dvwoolAuthor
    Participant
    January 13, 2010

    Hi Rick,

    Thanks for posting a reply.  Yes, FMS is a Windows server.

    When I initially tried getting it to work, I configured the FMS server as a stand-alone server (not part of our Windows domain) and placed it on my LAN (no firewall in the mix)... I successfully mapped a network drive via Windows with the appropriate domain credentials... then in the FMS config I tried both drive letter and UNC path \\content-server-ip-address\share but neither worked.  I DID restart the FMS service each time I made a change.

    In troubleshooting, I found a thread where someone relayed to try configuring the FMS windows service account to start up using the domain credentials... I had to join the domain to do that... once I joined the domain and started the FMS windows service with the appropriate credentials my streaming video started working using \\content-server-ip-address\share.  So... now it works fine on my LAN but when I move it to our DMZ the service won't start with the domain credentials because it can't reach the domain to authenticate.  I'm not sure why FMS can't utilize the mapped drive like the Wowza server does.  Any additional thoughts/advice?

    Thanks again!

    -Dave