After installing Service Pack 2 for Windows XP, you will no longer be able to connect to your account using WebDAV.
Then, if your server uses BasicAuth (basic authentication) to verify your username and password when you connect to your account via WebDAV it might not work with your Windows XP Service pack 2 . Service Pack 2 for Windows XP disables support for BasicAuth.
You can enable BasicAuth in SP2 by adding the following registry key and setting it to a non-zero value:
HKEY_LOCAL_MACHINE > SYSTEM > CurrentControlSet > Services > WebClient > Parameters > UseBasicAuth (DWORD)
Reboot your machine, and WebDAV will begin working properly. If you don't want to reboot for some reason, you can just restart the service.
Right click 'My Computer'
Choose 'Manage'
Select 'Services and Applications' -> 'Services'
Scroll down in right panel and select 'WebClient'
Restart the service
Click here to read more information on Microsoft's decision to disable BasicAuth.
Of Note: XP SP2 allows you to use port 80 which seems to allow BasicAuth, when stating the domain to connect to use http://www.domain.com:80/webdavfolder to connect. This was reported on the original knowledgebase and has been left out.
Mac OS 9 does not natively support WebDAV folders, but there is a free client application that works very well. The application is called Goliath and it works in Mac OS X as well and supports some of the more advanced WebDAV features missing from the OS X Finder.
Goliath can be downloaded from http://www.webdav.org/goliath/.
Once it is downloaded, launch it and enter in your WebDAV-enabled folder http URL as well as the User name and Password you set up when you enabled WebDAV access, and then click ok. Note that the user info is not necessarily the same username and password you use for ftp or shell access.
These instructions apply to Windows XP, but the process in Windows 2000 is similar.
You may see two files in this directory – .htaccess and .htpasswd – when you connect to it. These files do need to be there and you won't be able to delete them, so they can safely be ignored.
Because WordPress generates an .htaccess file, you may find that after you've set up the folder as WebDAV-enabled in the control panel, you can't connect to it from your remote location of choice.
For example, if you have a WordPress installation at www.yourblognamehere.com and you want to enable WebDAV at www.yourblognamehere.com/sampleshareddirectory, you'll need to add this to the .htaccess in the site's root directory:
RewriteCond %{REQUEST_URI} ^/sampleshareddirectory/(.*)$ [OR]?
RewriteCond %{REQUEST_URI} ^/failed_auth.html$?
RewriteRule ^.*$ - [L]
Changing "sampleshareddirectory" to whatever your actual directory name is, of course.