Hello,
I have following issue: I have a WebDAV Windows Server 2012 with IIS and SSL signed by StartCom (so it is trusted by default). On Windows 8, I have no problem to map WebDAV over HTTP, however with HTTPS, I am unable to map it. I keep getting prompted for credentials all the time. I have tested this both on Windows 8 and Windows 8.1 RTM.
Now the issue is that when I tried it on Windows 7, it mapped on both HTTP and HTTPS. I really have no idea what I am doing wrong, but I believe this could be client related rather than related to Windows Server and the WebDAV setup.
Thank you.
Edit: When running net use * https://files.domain.com in cmd under Windows 8, I get directly error 1790, on Windows 7, I am prompted for username and password.
Edit 2: When running net use * "\\files.domain.com@SSL\" /User:username password, on Windows 8, I get directly 1244 error.
Edit 3: As such as it seems, this issue seems to be related to: http://social.technet.microsoft.com/Forums/windows/en-US/1a3c29ab-d038-4132-af99-b85bce51b5c2/sslv2-being-used-with-webdav, since the symptoms seem to be the same, however there is no solution provided on that thread.
Edit 4: After running Microsoft Network Monitor, I can confidently say that the issue is indeed with the SSLv2 being used for WebDAV communications. See attached image.
Edit 5: I just used Network Monitor on Windows 7, where the drive maps correctly over SSL, see the difference in a picture below.
- Edited by Jan Hajek Thursday, September 26, 2013 6:47 AM Added Windows 7 picture