IIS 5 & IIS 6
IIS 6.2 not responding to WebDAV client
Last post Aug 03, 2017 07:19 AM by Yuk Ding
Aug 02, 2017 02:49 PM|ttblum|LINK
I have a WebDAV client that keeps freezing up during WebDAV sessions to my IIS 6.2 server. I have only one WebDAV client that is affected, all other clients (WInSCP, etc.) are able to connect and transfer files OK.
Packet captures show that the WebDAV client is connecting OK, but when it issues a MKCOL command IIS stops responding. IIS then closes the connection after 2 minutes (the timeout period).
If I connect over http, the WebDAV client connects OK and is able to issue MKCOL and transfer files OK, this is only happening when connecting with https.
The WebDAV client's SSL 'Client Hello' packet is:
No. Time Source Destination Length Protocol Src Prt Dst Prt Info
4 2017-07-25 14:58:26.128 xxx.xxx.xxx.xx xxx.xxx.xxx.xx 180 SSLv2 62572 443 Client Hello
Frame 4: 180 bytes on wire (1440 bits), 92 bytes captured (736 bits) on interface 0
Internet Protocol Version 4, Src: xxx.xxx.xxx.xx (xxx.xxx.xxx.xx), Dst: xxx.xxx.xxx.xx (xxx.xxx.xxx.xx)
Transmission Control Protocol, Src Port: 62572 (62572), Dst Port: 443 (443), Seq: 1, Ack: 1, Len: 48
Secure Sockets Layer
SSLv2 Record Layer: Client Hello
[Version: SSL 2.0 (0x0002)]
Handshake Message Type: Client Hello (1)
Version: SSL 3.0 (0x0300)
Cipher Spec Length: 21
Session ID Length: 0
Challenge Length: 16
Cipher Specs (7 specs)
Cipher Spec: TLS_RSA_WITH_3DES_EDE_CBC_SHA (0x00000a)
Cipher Spec: TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA (0x000013)
Cipher Spec: TLS_RSA_WITH_RC4_128_SHA (0x000005)
Cipher Spec: TLS_RSA_WITH_RC4_128_MD5 (0x000004)
Cipher Spec: SSL2_RC4_128_WITH_MD5 (0x010080)
Cipher Spec: SSL2_DES_192_EDE3_CBC_WITH_MD5 (0x0700c0)
Cipher Spec: TLS_EMPTY_RENEGOTIATION_INFO_SCSV (0x0000ff)
Has anyone else had anything like this?
Aug 03, 2017 07:19 AM|Yuk Ding|LINK
What IIS 6.2? I never heard this version of IIS. Please ensure it is IIS6 or IIS 7 version. In addition. Do you have any log entry in IIS log? Besides, to ensure the https connection, please ensure the certificate is trusted and your IIS server have the
private key. Besides, please check whether the schannel support the SSL2.0 3.0. You could check the configuration in registry or modify the configuration with IIS crypto.
Also you could check the httperr log in C:\Windows\System32\LogFiles\HTTPERR .
In addition to allow the MKCOL method in IIS, you could go to IIS manager->site level->handler mapping->select WebDAV->request restrictions->verbs->check all verb or add MKCOL to one of the following verbs.