I hope that some of you have more experience with Webdav servers than me.
Please only answer when you know this very problem and have solved it.
Windows 10 users of domain A want to access a webdav server of domain B. In the browser this works, but of course they can only read the files in the browser. Thus, for write access, they want to use Webdav in Windows Explorer and create a desktop shortcut for this purpose with the target
\\webdavserver.domain\Folder or \\webdavserver.domain@SSL\Folder - that makes no difference and everything works so far.
After a reboot, Windows asks for authentication when using that shortcut , which fails despite correct input!
But if he uses a browser for this, it asks for authentication as well, which succeeds AND THEN the desktop shortcut is also usable!
This is reproducible at any time.
If I test the whole thing with a user from domain B (the domain of the Webdav server), this phenomenon does not occur!
What needs to be done to avoid using the browser?
Hm, "AuthForwardServerList" rings a bell here, so I am afraid this was already tried before, but in the afternoon we'll have time to retry this.