If I go via: Computer/Map network drive/Connect to a web site.../Next/Next, then type in http://www.lamplighter.co.uk:2077/public_html/ it fails.It works in XP, well, but it failed in Vista too and no answer.It means hosting and updating an internet site using MS Publisher under 7 x64 is not really possible(practical), same as in VIsta x64.Dave

WebDAV is horribly broken in all versions of Windows. It is not meant to connect to non-Microsoft servers, and it appears your server is Linux/Apache based.Sometimes, you can get WebDAV to work. But mostly, it won't. You are right in that it seems to have gotten progressively worse as the windows version number increases. Even the webdav support in XP SP1 worked better than that of XP SP2.Try typing Windows Webdav Client into google. There are some free options out there, but they won't allow you to do drive mapping, only file copying.Another thing you can do if you have root access to that Linux server is to monitor the apache access logs and find out what Windows is trying to do. I was able to tweak my local Apache server to work better with broken Microsoft WebDAV this way.

drg40 said: If I go via: Computer/Map network drive/Connect to a web site.../Next/Next, then type in http://www.lamplighter.co.uk:2077/public_html/ it fails.It works in XP, well, but it failed in Vista too and no answer.It means hosting and updating an internet site using MS Publisher under 7 x64 is not really possible(practical), same as in VIsta x64. Dave HiTo connect to web server you should use Add network location instead of map network driveAlso path you specify is invalid because it muststart withhttps, but not withhttpYour web server must support https in order to connect in that wayYou can try to use ftp instead of https, but in W7 beta there is some bug and it does not work

Thank you very much for that. Until you said I would never have thought that a right click would lead me to 'add a network place' while a left click would take me to 'mapping a network drive'. It's all a bit like those original dungeons and dragons games, isn't it? Guess where the secret pathway is hidden.Anyway, it doesn't work for me. IE8 takes the https form, and whilst complaining bitterly about wrong certificates does connect me, while the http form connects quite happily.Neither of the forms works when adding a network location, both saying that the file is invalid.I have asked the host for help with 'tweaking the Apache server', but their problem is that it's not their bug. DaveDave

I think this is W7 bug, if you would like read list of bugs I found in W7 betahttp://social.technet.microsoft.com/Forums/en/w7itprogeneral/thread/ee88ae8d-27d4-42b6-96d3-b68eedfcac64/

I think this is W7 bug, if you would like read list of bugs I found in W7 betahttp://social.technet.microsoft.com/Forums/en/w7itprogeneral/thread/ee88ae8d-27d4-42b6-96d3-b68eedfcac64/

The problem is that it isn't a W7 bug. It's the same (or appears to be) bug as in Vista prior to SP1 which MS knew about: it was there after Vista SP1, which they knew about and now, here it is in in W7 beta.Gives you every confidence in the product, doesn't it?It would help if there was a knowledge base article saying that they accepted that the whole area was a complete pig's armpit but the bugs weren't going to be fixed and the workround is to use MS hosting sites only.Thanks for the list. The only major one I can see you've missed are the repeated unexplained crashed of IE8.Dave

Ok then better look here:http://www.webdavsystem.com/server/documentation/troubleshootingthis is big because problem is that web and ftp sites cannot be oppened in Windows explorer. This is bug No 3 in my bug list. Webdav require open of website in windows explorer but this is not possible so this is bug with windows explorer.I cannot see web folders in windows components in W7 so maybe this is reason for problems with webdav in W7IE8 crashes by themselvs are not included because they are reported on each crash, but specific aspects if IE crashes are included