I have an IIS server that I've configured WebDAV on so a certain directory can be drive mapped on remote clients. Almost of the client computers that will need to use this are Windows Servers versions from 2008 R2 through to 2016.
On my Windows 10 PC, I can drive map the WebDAV URL without issue. I'm on the LAN. I can also map it on my home PC fine - it is also Windows 10, but on an entirely different network. Also connects OK on Windows 7 systems on the LAN and elsewhere on the internet.
The command I'm using is
net use p: http://pe-distribution.corporatedomain.com.au /User:pe.user P@ssw0rd /Persist:YES and the P: drive appears straight away and I can read/write without issue.
But if I try to run the same on any of the client servers (Windows Server Std 2008 R2/2012/2012 R2/2016) that will need to use it, I receive the very unhelpful
System error 67 has occurred. The network name cannot be found.
I've even tested other Windows Servers on the same LAN as the ISS server and they fail.
Is there any security policy or registry settings in the Windows Server OS that need to be modified for NET USE to work with http/https? Or something else I've missed in the IIS config?