Windows 10 client not responding to NTML challenge.

[AkikoOrenji]

I can see the unauthorized being sent (WWW-Authenticate: NTLM) but the client never responds. I've tried a few different methods for the client accessing the wedav server and they're all the same. If use curl from your example it works as expected. If i use dir \localhost@8888\test from your examples this results in the unauthorized from the server not no hash sent from the the client. I've tried with a domain joined machine and non-domain joined Windows 10 machine.

I'm wondering whether by default something is now disabled in the latests Windows 10 builds. Any idea what that might be related to ?

Thanks