IIS7.x: Webdav Troubleshooting


When you're troubleshooting webdav problems in IIS 7.0 and think that everything should be working (but its not), consider uninstalling webdav completely, rebooting, downloading the most current installer package from http://www.iis.net/download/webdav (even if you think you already have the latest bits), and reinstalling webdav.  This isn't the answer to every webdav problem but it seems to me to allow good progress for the stranger webdav cases.

Additional keywords:   PROPFIND PROPPATCH MKCOL Web-based Distributed Authoring and Versioning IIS 7.0 IIS 7.5 IIS7 IIS7.5 500 0 405 sccm

 

Comments (4)
  1. Melinda D says:

    Isn't there also an update for webdav that you must download as well?  

  2. Help with WebDav configuration! says:

    I have WebDav running on WIndows 2008 Server R2 with IIS 7.5. I have three sub-sites running on the IIS Server. I finally got it working with Expression Web 4, but not Visual Studio 2010 ( I can deal with that, for now). The problem comes when I enable either basic or Windows authentication in the "Authorization" section of IIS. Either one of these is required for me to connect via WebDav with Expression Web 4. WebDav works fine… But then when I go to the site as a regular user for testing, I get a login screen. This is unacceptable for a public website! Am I configuring the IIS wrong? What can I do?

  3. I have WebDav running on WIndows 2008 Server R2 with IIS 7.5. I have three sub-sites running on the IIS Server. I finally got it working with Expression Web 4, but not Visual Studio 2010 ( I can deal with that, for now). The problem comes when I enable either basic or Windows authentication in the "Authorization" section of IIS. Either one of these is required for me to connect via WebDav with Expression Web 4. WebDav works fine… But then when I go to the site as a regular user for testing, I get a login screen. This is unacceptable for a public website! Am I configuring the IIS wrong? What can I do?

  4. Chris says:

    What happens when you click CANCEL on the login screen?   401.1?  401.2?  or just 401?

    Usually public websites use anonymous authentication so the general public can reach them and not have to supply any credentials.  You'd only want to use basic or Windows auth if the people hitting your site actually have a user account on the domain that your web server is part of (or has trust relationships with).  

Comments are closed.

Skip to main content