I've just set up the following scenario:
4 IIS 7.5 sites; (1) an anonymous ftp site; (2) an anonymous WebDAV site (pointing to the same disk location as the anonymous ftp); (3) a secure ftp (FPTES) site (port 22) and (4) a secure WebDAV site (pointing to the same disk location as the FTPES site). The secure sites all use a self-signed certificate (obviously we won't run with this in production, just for testing).
The first 3 work absolutely fine; anonymous ftp works like a dream, WebDAV (Windows 7) can access the equivalent http site easily, and FileZilla can link up perfectly to the FTPES site. Site 4 however only partly works; I can access it over https through a browser (even- as tested yesterday- runnning on port 666) but WebDAV connections just don't work from my Windows 7 box (in fact- WebDAV doesn't even work from the server itself and by default our endpoint firewalls are switched off on the domain, so it's not a firewall issue).
The sequence of events is:
<<
net use u: https://x.x.x.x:666 /user:<mydomainuser> <mypassword>
System error 1244 has occurred.
The operation being requested was not performed because the user has not been au
thenticated.
>>
Any ideas? I've tried various registry modifications, I've even downloaded BitKinex but have had no joy. As soon as I take off SSL then the site works any which way I want- it just doesn't seem to be accepting SSL encrypted WebDAV sessions. I've even had WireShark on the case but it's not provided any real help.
<UPDATE>: I've just tried this from an XP machine (without a proxy) and it works like a dream (barring NTFS permissions, which are the least of my worries at the minute). So it's probably a Vista/ 7 "feature".
<UPDATE 03/03/11@17:16> Okay, this is definitely a Vista/ 7 "feature"; I've just managed to connect to the HTTPS Webdav folder from my Nokia N8. It complained about the certificate (as you'd expect with a self-signed) but mapped the drive no problem.