I'm thinking of sharing files for WebDAV connections between servers.
Both servers are Windows 2012 r2.
Both are issued by WebDAV.
There are other cloud A servers and Azure servers.
1. The folder of A server can be connected from Azure server.
2. The Azure server folder is in a state where A server cannot connect.
WebDAV settings are the same, but 2. I can't connect.
In addition to the above, there are connections in Windows SV 2008 and Windows 7/8, but
As there will be more patterns, I will write only the above first.
The connection error is System error 64.
Where should I check first?
↑This is a supplement to the above.
Connecting to Azure Server (WinSV2012R2) (https)
OK: Win7/Win8.1 to
NG: Win10/WinSV2012R2/WinSV 2008 to
Also, when WebDAV client software (CarotDAV, NetDrive) is installed and connected to an NG PC, connection and net drive setting can be performed without any problems.
If possible, I'd like to share with Windows standard network drive settings...
I see an article on the Internet saying WebDAV is unstable because it is not implemented well in Windows.
Don't you know what's not good?
OS difference? OS version?Network settings?Authentication?
Will it be improved by updating the Win standard WebClient?
If you have any advice, please let me know.
azure
Connecting to WebDav without SSL authentication is no longer available on the Windows client side.
...but it shouldn't work with Windows 7, so it's actually starting from my Windows 7 environment
Connect to a WebDAV server that is not SSL-authenticated by itself
I make registry changes and connect, or I use a WebDav client that looks like it was written in the supplementary information.
Registry changes reference URL: http://support.kagoya.jp/kir/manual/webdav/win7/
If the certificate for the WebDAV server you are asking about has not been created, or if the client has not imported the certificate, it may be the same cause.
(The OK situation is different from mine, so I think it's different...)
>Will updating the Win standard WebClient improve?
If the cause is the above, I think the Windows standard client will be even more severe because it falls on the side that tightens the restriction.
© 2024 OneMinuteCode. All rights reserved.