0

I posted a question earlier this week about our IIS8.5/WebDAV setup: IIS8.5 with WebDAV only serves read-only files

I have the basics working, but now having trouble with mapping the WebDAV to a drive letter on a client PC (Windows 10).

My IIS setup looks like this:

sites

The highlighted "Z-Drive" app points to the Z: drive on the server. Just below that is a separate Site (running on port #8080) that has the exact same setup (same physical path, same app-pool, same WebDAV Authoring Rules).

However, these 2 URLs behave very differently!

  1. http://server/Z-Drive can be mapped to a local drive letter on a PC, but it's read-only. Testing this with curl (curl --ntlm --u username:password -T file.docx http://server/Z-drive) returns a 409.0 error ("Conflict").
  2. http://server:8080 works properly with curl (same curl command copies the file to the server), but that URL cannot be mapped as a local drive letter. net use Z: http://server:8080 gives System error 1920 has occurred. I can map sub-folders of that Z: drive (net use Z: http://server:8080/subfolder), but I need the users to be able to get that whole Z: drive through WebDav, as one drive one their PC's.

I'm willing to use either URL (http://server/Z-Drive or http://server:8080), but one maps to a drive-letter as read-only and the other won't even map. Any suggestions for either problem?

1

I've found most WebDAV-Problems by enabling and analyzing the IIS Site Logfiles.

We used tworeferences to setup WebDAV - maybe one offers some help for you:

Unfortunately, compared to our other Linux WebDAV-Servers, the Microsoft IIS WebDAV service creates many problems - and Microsoft did not fixed them sincy many years. (E.g. we have problems with File Locking, Filename-Encoding, "long" filenames [we have 2016 and Microsoft could just use the right Win32 API which supports real long filenames], etc.)

Additionally, since many years the Windows WebDAV Client is very annoying: on some clients the WebDAV-Connection just works, while the same net use command just throw errors on other Clients. It also has problems with SSH-Certificates.

Therefore, we use 3rd party Software on the Clients to map WebDAV Drives - they are much more stable, often much faster and they behave identical on all of our Windows Clients.

Kind regards, Tom

| improve this answer | |
  • When you mention a Linux WebDAV server, was it Apache? I could install that on the Windows server. I don't have to use IIS. Any recommendations for a Windows client? – jimtut Dec 10 '16 at 16:46

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.