![]() As said before, the service can crash sometimes on Windows 7 or WS08R2 when someones accesses a WebDAV resource. So, if the WebClient service doesn’t run, you can forget about WebDAV and DFS working smoothly.īack to the crash now. Microsoft’s Distributed File System (DFS). It can also behave as something similar as a WebDAV client: not web based, but in a complex, distributed network file system, i.e. It does actually more than just being a WebDAV client.Sometimes it’s not a good idea to simplify descriptions or names, because it can cause more confusion… Anyway, because it’s a WebDAV client the description of the service in Windows speaks about Internet based files, although I like “web based files in a WebDAV mechanism supported” more, because it can happen on non-Internet networks too and doesn’t include every kind of Internet based file, only web based files in a WebDAV mechanism. It’s not the client for every web based action, only for WebDAV related stuff.Personally I don’t like the name “WebClient”, because of 2 reasons: So WebDAV can be considered as a mechanism for dealing with files on web locations. For your information, WebDAV is a protocol that extends the HTTP protocol and is meant for creating, editing, deleting, versioning, managing,… resources in a distributed and web-based way, meaning the resources reside in a location on the network, possibly on the Internet, and are dealt with through HTTP (SharePoint uses WebDAV for example). It is possible the Windows service WebClient crashes on Windows 7 or Windows Server 2008 R2 when someone connects to a Web-based Distributed Authoring and Versioning (WebDAV) resource. I can supply the response/requests from Fiddler if that would help anybody debug this with me.WebClient service crashes on Windows 7 or Windows Server 2008 R2 Sadly mini-redirector is the easiest to use for my potential clients, so it is imperative that it works with mini-redirector. What is frustrating is that I anticipated mini-redirector being the hardest to get working, so I made it work first on my development machine before testing it with all other clients, so I thought I was in good shape until I attempted to connect on other computers and saw that it was failing, but only with mini-redirector. I am thinking it has to be something to do with my IIS 7.5 setup on the server, or a setting on all of the other client machines except my development machine, because my code appears to be fine, the server appears to respond fine to mini-redirectors requests, it just doesn't map the drive after the 207 multistatus response like it does with all other clients.Īny help would be greatly appreciated. I have even moved my server to a secure HTTPS site with an SSL cert just in case that was the issue, and it still doesn't work. I have made sure to use the registry hack to allow basic authentication over a non-secure HTTP site. And as I mentioned above, it works perfectly on my development machine with mini-redirector(although the IIS 7.5 server I am connecting to is not on my development machine). What is weird, is the server IS found, I can see it in Fiddler, and the server is responding as expected.Įvery other 3rd Party WebDAV client has a similar exchange with my server and connects and brings up a directory listing just fine. At this point, mini-redirector brings up the login prompt again and does so 3 times in total before failing to connect with an error saying the server cannot be found. Everything seems to work fine, my server accepts the login credentials and responds back with a 207 multistatus response with an "HREF" to the root directory. After entering the password, a new PROPFIND request is sent but this time with the authorization header. ![]() This brings up a login dialog for user and password. My server responds back with a 401 unauthorized. Then mini-redirector sends a PROPFIND method with a depth of 0. When I try to map the drive, an OPTIONS header is sent and my servers responds with a 200 OK. I have used Fiddler to analyze the network traffic and everything appears fine. ![]() The strangest thing, is on my development PC where I wrote the server, I can connect just fine, however ANY other computer that tries to access the server, fails to connect with mini-redirector. It is working well with 3rd party WebDAV clients but does not work with Windows built-in mini-redirector when mapping a drive to the http location. ![]() I wrote a custom WebDAV server that authenticates users from a database and serves a virtual file system based on records from a database. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |