Friday, November 16, 2012 4:08 AM
Im trying to setup a webdav server. This is the only function on the server currently. I am setting up a virtual directory (https://webdav.domain.com/(virtual directory)
The main website has nothing on it and is not being used. The virtual directory points to my dfs path back to the file servers. I have tried every way I can think of to get this to work but all I ever get is either http 500.19 error or an endless loop of login box. I currently have asp.net impersonation set with windows login enabled. I do not have any https settings set at this time. Can someone give me a good walk through for 2012 to get this working with domain credentials. We currently have a 2003r2 box that is about to be retired running webdav. It works perfectly. It is using basic auth with https website cert but I understand 2008 and 2012 dont like to operate that way.
In the end i need 2 virtual directories under the website to be assessable via webdav. I hope someone can help me out.
Monday, November 19, 2012 6:00 AM
Not sure about Windows 2012. WebDAV in Server 2008 is different from Server 2003:
Configuring WebDAV on Windows Server 2008 for Configuration Manager 2007
Monday, November 19, 2012 3:24 PM
I think I have this working now. My authentication error was fixed by me setting up a service account and using that account in the app pool. I gave that account the security groups that would allow it to see the folders in the virtual directory. After setting the user up in the app pool I switched to basic authentication on the website and virtual directory and made sure my 443 stuff was set up. Everything appears to be working now.
- Marked As Answer by K_evin ZhuMicrosoft Contingent Staff, Moderator Tuesday, November 20, 2012 2:27 AM
Tuesday, November 20, 2012 2:27 AMModeratorThanks for sharing your experience and solution.