IIS 6 and webdav problem?

TheMSsForum.com: The Microsoft Software Forum

server 2003 sp1
IE 6.0.3790 from same server
IE 6.0.2900 (xp sp2 machine behind an ISA 2000 proxy/firewall)

both IE clients have same problem. Can not open web folder. WebClient
service is running on both. Here is the error:
'internet explorer could not open http://server.domain.com/virtualfolder as
a web folder. would you like to see its default view instead?'
this error occurs immediately, never even prompted for credentials.

WebDav is installed and enabled on server. NTFS permission are good (user is
able to otherwise browse the site - just no webdav functionality)
- basic auth is the only method enabled (clients can authenticate to see
regular http site)
- anonymous access is disabled
- directory browsing is enabled on the virtual directory (as well as read
and write)

IIS log reveals:
2006-08-24 20:05:55 W3SVCxxxx computername ipaddress GET /foldername - 80 -
ipaddress HTTP/1.1 Microsoft-WebDAV-MiniRedir/5.2.3790 - - server.domain.com
404 0 2 258 186 0
2006-08-24 20:05:55 W3SVCxxxx computername ipaddress GET /foldername - 80 -
ipaddress HTTP/1.1 Microsoft-WebDAV-MiniRedir/5.2.3790 - - server.domain.com
404 0 2 258 186 0
2006-08-24 20:05:55 W3SVCxxxx computername ipaddress GET / - 80 - ipaddress
HTTP/1.1 Microsoft-WebDAV-MiniRedir/5.2.3790 - - server.domain.com 404 0 2
258 152 0

notice the 404 0 2? 404 is file or folder not found? but its found just fine
when http browsing the site? 0 is the sub status code and not used I presume
and I don't know what the win32code of 2 is? I also see some win32codes of
64?

404 0 64 and 404 0 2 are common in my log when trying to access via webdav?

I don't know whats wrong? anyone else?
Top

Re: IIS 6 and webdav problem? by djc

djc
Fri Aug 25 10:10:27 CDT 2006

to anyone interested:

404 0 2 - using server as client (IE on the actuall IIS server)
404 0 64 - xp xp2 IE 6 client from remote network

these are the sc-status, sc-substatus, and sc-win32-code (going by memory so
might not be exact column names) IIS logs when a webdav connection has been
rejected by URLScan.

That was my problem, I didn't realize URLScan was installed on the server I
was working with! duh. That should have been one of the first things I
checked. URLScan was doing its job and blocking the required HTTP verbs and
such that webdav requires. Modified urlscan.ini and it works fine now.

to anyone having the same problem the urlscan.ini file has comments in it
refering to webdav so you will know what you need to enable just looking at
that.

"djc" <noone@nowhere.com> wrote in message
news:OBYppv7xGHA.4972@TK2MSFTNGP03.phx.gbl...
> server 2003 sp1
> IE 6.0.3790 from same server
> IE 6.0.2900 (xp sp2 machine behind an ISA 2000 proxy/firewall)
>
> both IE clients have same problem. Can not open web folder. WebClient
> service is running on both. Here is the error:
> 'internet explorer could not open http://server.domain.com/virtualfolder
> as a web folder. would you like to see its default view instead?'
> this error occurs immediately, never even prompted for credentials.
>
> WebDav is installed and enabled on server. NTFS permission are good (user
> is able to otherwise browse the site - just no webdav functionality)
> - basic auth is the only method enabled (clients can authenticate to see
> regular http site)
> - anonymous access is disabled
> - directory browsing is enabled on the virtual directory (as well as read
> and write)
>
> IIS log reveals:
> 2006-08-24 20:05:55 W3SVCxxxx computername ipaddress GET /foldername -
> 80 - ipaddress HTTP/1.1 Microsoft-WebDAV-MiniRedir/5.2.3790 - -
> server.domain.com 404 0 2 258 186 0
> 2006-08-24 20:05:55 W3SVCxxxx computername ipaddress GET /foldername -
> 80 - ipaddress HTTP/1.1 Microsoft-WebDAV-MiniRedir/5.2.3790 - -
> server.domain.com 404 0 2 258 186 0
> 2006-08-24 20:05:55 W3SVCxxxx computername ipaddress GET / - 80 -
> ipaddress HTTP/1.1 Microsoft-WebDAV-MiniRedir/5.2.3790 - -
> server.domain.com 404 0 2 258 152 0
>
> notice the 404 0 2? 404 is file or folder not found? but its found just
> fine when http browsing the site? 0 is the sub status code and not used I
> presume and I don't know what the win32code of 2 is? I also see some
> win32codes of 64?
>
> 404 0 64 and 404 0 2 are common in my log when trying to access via
> webdav?
>
> I don't know whats wrong? anyone else?
>


Top