I wouldn't be surprised if most people here forgot to specify the port.
My port is 8080 so it should look like this http://myaddress.org:8080/WebDAV without the port it will try to map somewhere on your server.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Hey on there!
Got trouble with mounting drive through WebDav on Windows 11 desktop clients. On Windows 10 or 7 was no problems yet for 30+ different users and respectively OS assemblies .
System configuration: Serveside - WebDav cloud server OwnCloud 10.9.1-rc1 running on Ubuntu 20.04.3 LTS, SSL secured via LetsEncrypt (Traefik used). ClientSide - Windows 11 clients on Oracle VirtualBox (fresh install from MS official) and newly installed W11 on few client PCs
Expected behaviour: Mounting network drives using any in-box features, as it was on W7 or W10
Actual behaviour:
or
net use X: "\\mydomain.com@SSL\remote.php\webdav\" /persistent:no /savecred
Both with error:
> System Error 59. Unexpected error
> The mapped network drive could not be created because the following error has occurred A device attached to the system is not functioning
Error occured:
> New-PSDrive : A device attached to the system is not functioning
For sure, next features are set correctly on client Windows 11 to use WebDAV:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\WebClient\Parameters set:
No any events in OwnCloud log on server side when mapping commands trying to run! Seems like client even not trying to talk with server. Issue also posted on OC forum - https://central.owncloud.org/t/webdav-mapping-error-on-windows-11/34602
Duct tape solution: For few month stuck, find out same issue in past, with Windows 10 1903 update: https://social.technet.microsoft.com/Forums/ie/en-US/d01099e0-9e09-4382-8a09-cf6eba1b2d64/webdav-broken-in-update-1903?forum=win10itpronetworking
In the last reply find out something, that works fine. I replaced two DLLs WebCient service using with same DLLs from original Windows 10:
%WINDIR%/System32/winhttp.dll
%WINDIR%/System32/winhttpcom.dll
Backuped original W11 files before, then made administrator as owner and granted full permissions to the files. Otherway i was not allowed to change them. Then restarted WebClient service and everything goes fine.
Conclusion: I bet its an MS side bug, that should be fixed.
Best regards and thanks in advance for any other info about this issue (easier way to fix, maybe?) or Microsoft reaction.
P.S. Newbie here - help me with tags pls )
I wouldn't be surprised if most people here forgot to specify the port.
My port is 8080 so it should look like this http://myaddress.org:8080/WebDAV without the port it will try to map somewhere on your server.
Anyone have a fix for this yet? Works fine on all Windows 10 PC's just not on windows 11.
Was hoping Microsoft would have a fix by now.