• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 3167
  • Last Modified:

Microsoft-WebDAV-MiniRedir

I would like to know about these WebDAV entries in my IIS log.

2002-05-23 18:02:21 10.1.19.211 - 10.1.19.225 80 OPTIONS / - 200 393 141 0 HTTP/1.1 Microsoft-WebDAV-MiniRedir/5.1.2600
2002-05-23 18:02:21 10.1.19.211 - 10.1.19.225 80 PROPFIND /C$ - 404 0 156 16 HTTP/1.1 Microsoft-WebDAV-MiniRedir/5.1.2600
2002-05-23 18:02:21 10.1.19.211 - 10.1.19.225 80 PROPFIND /C$ - 404 0 156 16 HTTP/1.1 Microsoft-WebDAV-MiniRedir/5.1.2600
2002-05-23 18:02:21 10.1.19.211 - 10.1.19.225 80 PROPFIND /C$ - 404 0 156 16 HTTP/1.1 Microsoft-WebDAV-MiniRedir/5.1.2600

I'm not aware of that we're using Microsoft-WebDAV-MiniRedir.

Is it something that we could/should disable on the webserver?
0
ola
Asked:
ola
1 Solution
 
TwodogsCommented:
Without more context, (e.g., What is on the client and server and from whose log is this error stream taken from.)here is my best guess.

It looks like an application on a Windows XP client is sending a WebDAV propfind method (e.g. extended HTTP1.1. method to get resource information) to your web server using the WebDav file system redirector which is incorporated directly into Windows XP. More than likely, the client is not using a web browser but some other Windows application, like Web Folders, to access a resource on your web server.  
 
Here is some background on file system redirectors. I apologize ahead of time if I am giving you information you already know. I don't mean to sound patronizing.

Generally speaking, the client redirector is Windows OS object that handles the presentation of remote file system resources on the network. This module handles user account security, resource availability, the actual "connection" to a remote server's resource, and other network operating system-specific functions. Essentially, once two computers are able to communicate with each other, the redirector provides the local operating system with the ability to access the network resources through local file system. The internal Windows architectural layers go something like this:

App using I/O call with UNC name
             |
Multiple UNC Provider (MUP)
             |
WebDAV Redirector (or some other Redirector like CIFS)
             |
Transport Driver Interface (TDI)
             |
Network Protocol - Driver - NIC, etc..


For example, the File Manager has never understood network concepts explicitly, but has always relied on a redirector to handle requests for it.

Windows XP integrates a redirector for WebDav directly into its file system. It looks like this component is generating the WebDav request that is returning these log entries.
0
 
olaAuthor Commented:
Thank you Twodogs for clearing this out.
0

Featured Post

Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now