Windows 10: Endless WebDAV requests caused by WqlEventQuery for Win32_LogicalDisk

Hi, I'm facing problems when mapping a drive via WebDAV and simultaneously using WqlEventQuery to monitor creation of logical disks. 1. WebDAV: The network drive is mapped to a folder e.g. http://192.168.178.10/folder. Here it is important that the network device does not allow access to http://192.168.178.10/ and will respond with a 403 status code if that "root" folder is accessed via e.g. PROPFIND. Unfortunately I cannot change the network device's behavior since it's from 3rd party vendor. I have also set up a WebDAV server on localhost for troubleshooting which is configured to behave

:)

 

WebDAV redirector makes strange requests in Windows 10

I noticed that when I access a WebDAV resource through the file manager, I get horrible performance, and looking at the Apache logs I see some oddities come through.

1) Requests from my authenticated user (the server requires Negotiate) are interspersed with requests from my machine credentials. ?!?! Why should the system be asking for the same file properties as the user, at the same time?

2) Sometimes it capitalizes the first part of the WebDAV path in the request. The Apache server, of course, responds that the method is not allowed because the uppercase path is not the same as the lowercase path. Why would it suddenly start uppercasing the path?

 

What is "Jackrabbit Webdav Server"? Why is it wanting my password?

• What is Jackrabbit?

Sounds scary to me, do you use Java?

• What's with the unsecure connection?

As you put it "my destination", is not secure. What I've seen is, this crops up when somehow a microsoft office 07, 10, and 13 application tries to use an unsecure connection.

• How do I stop this?

There may be a way but you will need to work in the registry, first go over this KB article: https://Office application opens blank from Sharepoint,WebDAV or site when it is HTTP | support.microsoft.com/en-us/help

The area you want to concentrate on is: Step 1: Configure WebDAV Redirector on the client. Skip the Windows XP and Windows Server 2003 part and go to the Windows Vista, Windows 7, and Windows 8 To enable Basic authentication on the client computer, and study the steps. You may be adding a key. BasicAuthLevel [some systems already have the key but it's set to 0 ]. Before you start create a restore point: System Restore Point - Create in Windows 10 Then complete the steps from the beginning of the Vista, 7, 8 section.

• Here's a heads up:

1.) I've seen that the BasicAuthLevel can exist in your registry but it's set to ( 0 ) which causes the problem you're experiencing. Then all you have to do is change the value by right clicking on it and left click on Modify then enter a 1 or 2 in the value data box.

2.) It says to use a value of 2 for the BasicAuthLevel value but this is for secure and non secure SSL connections, I haven't found anything as to what is meant by non-secure SSL .

I did take a look at my registry and found it's set to (1) 1 - Basic authentication enabled for SSL connections only: One (1) is what I'd go with.

 

WebDAV access from File Manager gone from Belle

You are not alone. The request for Remote Drive is also in the Mike_Myers_N8 to-do list:



I don't know why Nokia had to remove WebDAV in Belle. There is very little information available about the
under the hood changes from Anna to Belle regarding memory and storage management. A growing list of apps no longer working is all we have ...



--

Hans