I recently spent far too much time getting Webdav enabled user folders to be accessible over SSL outside our LAN (using IIS 7 on Windows Server 2008). As a separate project I was later required to change the DNS suffix of our Active Directory integrated zone from <domain>.local to <domain>.csd
This caused a few problems on our network, most of which has been resolved however my webdav setup is completely broken and I can find no indication of why. The error logs in IIS are returning error 500 with no description. Attempting to map a webdav drive from the command line returns a system error 67 (network name cannot be found) even though nslookup proves that DNS resolution is working properly and that the host is responding.
The initial attempt to connect using a web browser will ask for authentication, which seems to indicate there may have been something broken with the authentication process.
Any help to understand where to look would be greatly appreciated.