WebDAV on XP

Wednesday 06 July 2005 4:32:41 pm

I searched the forum for answers to getting WebDAV to work correctly on XP but did not find any concrete answers.

Has anyone successfully gotten this to work with Ez Publish and an XP client using Windows Explorer? The problem is you can connect to the WebDAV server, but it doesnt like basic authentication and wants to prepend the username with the domain or netbios name.

I've tried re-installing the webfldrs.msi file in system32 and trying to map the drive with just the netbios name according to this Microsoft article http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q315621

I can successfully connect with a third party WebDAV client so I know my Ez Publish site is setup correctly.

Thanks,
John Axsom

Thursday 07 July 2005 11:49:30 am

Well, I kind of have it working. Apparently XP SP2 changed the way the WebDAV redirector functioned. Here is the microsoft article describing this - http://www.microsoft.com/technet/prodtechnol/winxppro/maintain/sp2netwk.mspx#EGAA.

I pretty much gave up trying to get xp to map to the webdav folder, so I installed webdrive to give it a try. Now the problem is I can cut and paste the files without any problems, but when I want to save them to the mapped drive from Office, I get a 403 Forbidden error. If I try to save from Office directly to ezpublish I get a lock in apache and Office comes back saying it can't save the file.

Anyone else having this problem on windows? I know the easy solution is to not use windows, but unfortunately thats what I have to make it work on.

Thanks again,
John Axsom

Thursday 07 July 2005 4:35:07 pm

Hey Kracker!

I am using that product (I've also tried Novell NetDrive which appears to be from the same code).

Are you able to save directly from within word or excel? I get a 403 Forbidden on both but word also spits out a Permissions error. I just don't get why I can drag and drop outside of Office but I can't save directly from Office.

I did notice in the log that word creates temp files then tries to move those temp files to the filename specified to save as. Thats when it barfs all over itself and spits out the error. The temp files stay and have to be deleted from the Ez admin interface.

Thanks,
John

Thursday 07 July 2005 9:47:09 pm

Hey John,

I haven't tried that (yet) ...

I remember that eZ publish WebDav support has has <i>known</i> problems with move/rename via WebDav.

At first I thought I could avoid these errors by switching WebDav clients, but alass I the errors persist.

I really hope that the move / rename support in eZ publish WebDav before 4.0 (hint hint :)

I avoid rename/move errors by using cut/copy/paste instead or just get the file up the folder and rename/move it inside the eZ publish admin ...

//kracker
<i>TWiT - TWiT0012H</i>

Member since: 2001.07.13 || http://ezpedia.se7enx.com/

Friday 08 July 2005 9:52:44 am

Hey Tony,

Your talking about connecting through IE right? I'm able to do that ok, just when I try to actually save in Word or Excel it bombs out.

I wasn't even able to connect through IE before I applied the registry entry noted in the M$ article.

I think I'm going to just have to train our users to save copies of their Word and Excel files locally, then copy them to the mapped Ez Publish WebDAV drive (mapped via Novell NetDrive). This works but I can hear it now - "Why do I have to do that?" "This is too hard!" "Mapped drive??"

Thanks,
John

P.S. - I forgot to mention I too am running ez 3.6.0 on Apache 2.0.52 on CentOS 4

Thursday 21 June 2007 1:28:25 pm

Here's the secret handshake that worked for me on XP SP2, IE 7, and eZ 3.9.2:

1.) Opened up IE.
2.) From the file menu, selected 'Open'
3.) Entered the URL as http://yourwebdavurl.com/# (note the # sign - also, put in your webdav URL, obviously). Checked 'open as web folder', and hit OK.
4.) IE sat for a long time at this point, and finally a 'My Computer' explorer window opened up.
5.) Went to 'Start'->'My Network Places' (selecting network places from the explorer window is OK too)
6.) You should have a new folder under My Network places with your webdav. From this point on, everything worked perfectly.