storing and accessing file

[Gerhard]

I have an application that needs to be able to upload documents that can
latter be accessed and opened by a hyperlink. I can do this easliy if I
store the files in a subdirectory in the application, but we will be using
multiple web servers, so the files need to be stored on a common file server.
Saving them is easy enough, but how do I point a hyperlink at a file on a
file server that is different from the web server?

Could you please give me an example of how to do this, and how to set up the
correct permissions on a Windows 2003 server?

Thanks.

[Paul Henderson]

> I have an application that needs to be able to upload documents that can

latter be accessed and opened by a hyperlink. I can do this easliy if I
store the files in a subdirectory in the application, but we will be using
multiple web servers, so the files need to be stored on a common file server.
Saving them is easy enough, but how do I point a hyperlink at a file on a
file server that is different from the web server?

You probably need to make a page in the application which just
retrieves the content of a specified file, and writes it to the
Response stream [using BinaryWrite or similar]. Then, you would make
your hyperlinks point to this page and pass the name of the required
file in the request string.

For permissions, it depends on your accounts setup. If the files will
be saved/retrieved when the page is accessed anonymously, then you'd
need to give the account under which ASP.NET is running (probably the
IIS default anonymous user account, IUSR_<something >) read/write
permissions on the relevant folders; if they are on a different
machine, then you'd either need to make the ASP service run under a
domain account (so the file servers have access to the credentials) or
explicitly allow the local account on the web server access to the
files on the other servers (which might or might not be possible). If
you pages use an authentication scheme whereby they are running under
the context of the domain account of the user accessing the site, then
if those users have permissions to access the file server anyway, it
should 'just work'. If they do not, you could either grant them
permission, or make the relevant section of code run under an
impersonation context for a domain account that is permission to view
the files.

HTH

-- ph

[Kevin Spencer]

Hi Gerhard,

You can create a virtual directory in IIS that points to the network path of
the directory on the file server containing the images.

--
HTH,

Kevin Spencer
Microsoft MVP
Professional Numbskull

Hard work is a medication for which
there is no placebo.

"Gerhard" <ac***@communit y.nospam> wrote in message
news:9C******** *************** ***********@mic rosoft.com...

I have an application that needs to be able to upload documents that can
latter be accessed and opened by a hyperlink. I can do this easliy if I
store the files in a subdirectory in the application, but we will be using
multiple web servers, so the files need to be stored on a common file
server.
Saving them is easy enough, but how do I point a hyperlink at a file on a
file server that is different from the web server?

Could you please give me an example of how to do this, and how to set up
the
correct permissions on a Windows 2003 server?

Thanks.

[Steven Cheng[MSFT]]

Hi Gerhard,

For your scenario, I think you can consider to System.IO class to read the
file stream from the remote file share in the page's code behind file and
then write the stream into the ASP.NET page's ResponseStream to populate
the file download page.

#How To Write Binary Files to the Browser Using ASP.NET and Visual C# .NET
http://support.microsoft.com/kb/306654/en-us

#Downloading Files - Forcing the File Download Dialog
http://aspalliance.com/259

Also, make sure your ASP.NET application can correctly access the remote
server's file share in code.

Hope this helps.

Regards,

Steven Cheng
Microsoft Online Community Support
=============== =============== =============== =====

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

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