locked
Cannot connect to webdav service RRS feed

  • Question

  • I can connect (most times!) to my webdav server (nextcloud) from Windows 10 by going to "My PC" then using the "Add Network Location" button. I enter the URL to my webdav server which is of the format:

        https://example.com/remote.php/webdav

    Then the credentials manager asks for username and password and whether I want that remembered. I enter that and tick the remember box. After a long pause the window opens and I can access my files.

    **But when I reboot I cannot connect and have to go through the whole process again.**

    I have tried adding `AuthForwardServerList` as multi value string under `Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WebClient\Parameters` and add example.com (obviously, my own domain) to it - a suggestion I found at (not allowed to post links yet...) but that has not helped.

    The error I get is

    > System error 53 has occurred.  
    > The network path was not found


    Running the troubleshooter gives a DNS error. DNS is working fine (e.g. on the same machine I can access the same site at https://example.com with a browser), but the error looks odd: it says

    > "windows can't find the host name "example.com@SSL" using DNS.

    It looks like it's including `@SSL` in the domain lookup?

    I have also tried connecting like

    net use N: \\mynextcloud.com@SSL\remote.php\webdav mypassword /USER:myuser /PERSISTENT:YES

    which gives the same errors above.

    Tuesday, January 29, 2019 12:21 PM

All replies

  • Hi,

    Please check whether this user could access WebDAV using other computers.

    Meanwhile, you can actually map network drives to webdav locations. To do so use this:

    1. Open Windows Explorer

    2. Rightclick on 'Computer'

    3. Go to 'map network drive'

    4. Choose station/drive letter

    5. Use this link to your WebDAV location:\\your_webdav_server_domain@SLL\rootwebdavfolder\path\to\folder

    6. Press OK and your set.

    The nice part of mapping your network drive is that you can use it for synchronisation (online/offline files).



    Best Regards,

    Eric


    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.





    Wednesday, January 30, 2019 8:52 AM
  • Hi,

    Just checking in to see if the information provided was helpful.

    Please let us know if you would like further assistance.

    Best Regards,

    Eric


    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Thursday, January 31, 2019 9:09 AM
  • Hi Eric,

    Thanks, but mapping a network drive via the UI does not solve it either. (Note that mapping a network drive is what the "net use" command in original post should do.)

    The exact same problem occurs: after a restart I'm prompted to login again when I first access the drive.

    There is nothing wrong with this user's webdav account. There is nothing wrong with this machine's DNS - e.g. the user can use a web browser on their machine to access the web UI of the webdav service without problem (proving that their machine is able to lookup the host from the DNS and that their account is valid)

    Thanks for your time.

    Thursday, January 31, 2019 9:23 AM
  • Hi,

    Thanks for your reply.

    Have you try to use IP address?

    Here is an article as a reference for you to troubleshoot Webdav.

    https://docs.microsoft.com/en-us/iis/publish/using-webdav/using-the-webdav-redirector#003

    More about this issue, it's recommend you ask in IIS forum for more professional help.

    https://forums.iis.net/

    Best Regards,

    Eric


    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Friday, February 1, 2019 7:25 AM
  • Have you resolved this problem? I come across the exactly same issue as yours.
    Thursday, September 5, 2019 8:49 AM
  • No, I have to explain to my users:

    "Ah, I'm afraid you're on a Windows machine. This means that - because their software is buggy, despite Windows creating the webdav technology - you have to jump through these hoops every day when you start work. For a more productive day, please use one of our Ubuntu machines".

    :-/

    Thursday, September 5, 2019 9:56 AM
  • I have the exact problem. Adding network location works and I can access files but after reboot, I can no longer access them until I delete and re-add the location.

    As a workaround I found that adding the network location, and when it asks you how to name it, you can click cancel without adding it and can access your files from your existing entry.

    Thursday, April 30, 2020 10:30 AM