On the Virtual Directory tab verify that Read, Write, Directory browsing, and Log visits are checked. After finishing the wizard, right-click the new virtual folder and choose properties 10.Allow the Read, Write, and Browse permissions.Leave the box checked for “Always use the authenticated user’s credentials when validating access to the network directory.”.Choose an Alias of “RemoteFileAccess” and a Path of “fileServershare”.Right-click on the chosen site -> New -> Virtual Directory…, this starts a wizard.Select the “Default Web Site” or create a new site.Expand SERVERNAME (local computer) -> Web Sites.Click on the Web Service Extensions folder and enable the WebDAV extension.
Start -> Control Panel -> Administrative Tools -> Internet Information Services (IIS) Manager.Assuming that you have IIS installed, here are the steps for making fileServershare accessible from You don’t have to run IIS on your existing file server(s), and probably shouldn’t.
First, of course, we need to install Internet Information Services (IIS) somewhere. Let’s take a closer look at the dials and levers we need to adjust for IIS to provide WebDAV functionality. This means that you won’t run into trouble with most firewall configurations, and can breathe a sigh of relief after paying an exorbitant fee to VeriSign for guaranteeing your identity. The great thing about WebDAV is that you can (and should) set it up to run on port 443 using industry standard SSL. WebDAV on Windows Server 2003 allows you to funnel data from users, through a WebDAV enabled Web server, and onto existing file servers. It makes the Web a two-way street by allowing remote users to PUT files on a Web server instead of just GETting them.
Web-based Distributed Authoring and Versioning (WebDAV) is a set of extensions to the HTTP protocol. If you don’t have the time or expertise to setup a virtual private network (VPN) then WebDAV is a quick and easy alternative to enable remote file access for your users.