Could not locate the WebDAV share on your system.
Could not locate the WebDAV share on your system.
I'm facing issues connecting to my WebDAV share via HTTPS on Windows 10 1709 and the newest version. I encounter numerous errors no matter the method—whether using the GUI in Explorer or the command line. It's strange since it functions perfectly on all other non-Windows devices. What alternatives should I consider? I've tried: net use w: https://{ddns address}:{port}/{share name} /user:{username} in Command Prompt, adding Network location in Explorer, changing settings in Internet options for IE, and editing the registry.
I recently attempted to gather relevant details for you, but I wasn't able to replicate the results on 1803. Most online resources discussing comparable problems focus on TLS 1.1/1/2 functionality, which was resolved in all public Windows 10 releases and later versions. Did this solution function in earlier Windows iterations or any other operating system?
It's actually my first attempt to connect a WebDAV share on Windows. It offers a minor advantage compared to my current setup, which involves using a VPN and mapping drives manually. From what I've learned, it performed well on Windows 7. I've noticed many issues with Windows 8.1 and 10, so I enabled WebClient Services and set it to automatic.
For fun, your initial comment about using a DDNS address is identical to what would happen if you switched to an IP address. Also, it’s a bit of a joke point—your note about VPN working but WebDAV not is relevant. Have you confirmed your server settings to allow direct WebDAV access instead of via the VPN? Are your firewall rules properly configured? I’m guessing everything looks okay for non-Windows clients accessing the share directly, though you were checking the VPN setup.
Edit: July 26, 2018 – Tabs
I haven't used it with my IP address directly. I'll try again later. If I keep getting the same errors, it might mean something is off. Everything seems set and working fine. Interestingly, Windows 10 lets me access the WebDAV share through HTTP. When testing locally without a VPN, I confirmed it via my phone's file browser. Connecting remotely also worked smoothly over HTTPS. I’m curious why Windows 10 seems to struggle with HTTPS specifically.
I was just trying to eliminate external factors when thinking about the issue. My assumption was it might be Windows disliking the dynamic DNS provider. I've faced problems with DDNS before. If it relies on IP, it's a partial solution; otherwise, we should dig deeper. You said it works over HTTP, so checking the protocol used when connecting via HTTPS on your phone or other devices is important. Windows no longer supports SSL2 by default—it's insecure—and most setups also block SSL3. If your WebDAV server doesn’t support TLS1.1 (1.0 might revert to SSL3, making connections risky), it won’t connect securely through a safe channel. You’d need to adjust this on your host platform. Unless I suggest other approaches, you may need to perform detailed network analysis with tools like Wireshark to see if the server or client is rejecting the connection and why. This could point to mismatched cipher suites, which can usually be fixed by reordering them. Otherwise, it might reveal sensitive authentication data about your server.
Using an IP to map the WebDAV share isn't recommended. The same issues appear as before: authentication failure. My long-term concern is that my IP might become unreliable since I have a dynamic one. I checked the NAS support page, which indicates SSL (HTTPS) isn't supported on Windows 10 and suggests using an older WebDAV client. Now I'm questioning whether it's worth persisting with this approach or switching to HTTP, even though it's less secure. Testing SFTP could be a better alternative.
The chance is increasing that it relies on SSL3 or maybe SSL2, which is significantly less safe. The issue here is that SSL2 is so flawed it offers no advantage over HTTP. If you're forced to stick with it, alternatives like SFTP might be your only option, or you could keep using a VPN—though it adds complexity and still protects traffic. I regret there wasn’t a better response; you can definitely configure Windows to use older SSL versions, but this exposes your system to many man-in-the-middle risks, which is why it was turned off by default originally. The key takeaway is that the HTTPS version of your WebDAV server remains insecure due to its outdated protocol.
Thank you for your assistance and for spending the time to assist me.