New WebDAV Problems

Until recently, my WebDAV stuff on a Windows 2003 Server was working just
fine. I frequently update the server with all updates from
windowsupdate.microsoft.com, so these new problems may be caused by a recent
update.

I have multiple folders set up as writable for a site admin group. Folder A
is an actual sub-folder on the web site, Folder B is a virtual directory
folder on the same site that points to the same directory.

Web Site Directory: C:\Inetpub\Sample
Folder A -> http://example.com/FolderA -> C:\Inetpub\Sample\FolderA
Folder B -> http://example.com/FolderB -> C:\Inetpub\Sample\FolderA

Until now, the Site Admin group could access both Folder A and Folder B
through WebDAV. Now, Folder A is only accessible by users in the
Administrators group, and Folder B is not accessible at all.

Attempting to connect to Folder A as a Site Admin returns the error: The
folder you entered does not appear to be valid. Please choose another.

Attempting to connect to Folder A as an Administrator works fine.

Attempting to connect to Folder B as a Site Admin or even as an
Administrator returns the error: Documents in this folder are not available.
The folder may have need moved or deleted, or network problems may be
preventing a connection to the server.

(All connections are attempted from three different machines running XP SP2
through "Add a network place".)

The virtual directory FolderB is set up to allow read and write access
through the IIS settings, and the actual directory permissions for
C:\Inetpub\Sample\FolderA are Site Admin: Full Access, Administrators: Full
Access, IUSR_MACHINE: Read Access.

Again, nothing has changed as far as file/directory permissions or IIS
settings. WebDAV just stopped working. I'm interested in knowing if others
have had the same problems, if someone else can replicate this problem on
their own server, and if there is a solution.

In the mean time, I had to change my server to not use virtual directories
for WebDAV folders, and I had to give a couple of users Administrator group
access so they could upload files. This is just a workaround, though, and
not a solution.

Bryan
--
Bryan T. Siders
President / Chief Software Architect
Sypher Technology, Inc.
www.sypher.com

RE: New WebDAV Problems

Oh, I get the same errors when attempting to connect to the WebDAV folder
from the Windows 2003 Server itself (through "Add a network place"), not only
from the three Windows XP SP2 machines.

:-)
Bryan

RE: New WebDAV Problems

Hi Bryan,

WebDAV doesn't require addtional permissions than a normal HTTP
connection. So regardless 'network place', I suggest you test access
the virtual directories in IE with different user accounts. For
example, logon as a non-admin account and try browsing to
http://example.com/FolderA, will you get any 401.x or 403.x in IE? If
the web page or directory listing comes up properly, please further
test open the URL as web folder in IE File menu->Open.

Also, you haven't mentioned which authentication methods you are
using on the directories?

Wait for your update. Thanks.

Best regards,

WenJun Zhang
Microsoft Online Support
This posting is provided "AS IS" with no warranties, and confers no
rights.
Get Secure! - www.microsoft.com/security

RE: New WebDAV Problems

""WenJun Zhang[msft]"" wrote:

> WebDAV doesn't require addtional permissions than a normal HTTP
> connection. So regardless 'network place', I suggest you test access
> the virtual directories in IE with different user accounts. For
> example, logon as a non-admin account and try browsing to
> http://example.com/FolderA, will you get any 401.x or 403.x in IE? If
> the web page or directory listing comes up properly, please further
> test open the URL as web folder in IE File menu->Open.

Both come up as directory listings just fine in IE. Both give the same
errors in IE File->Open.

> Also, you haven't mentioned which authentication methods you are
> using on the directories?

Folder A has Anonymous Access turned on and has Basic and Integrated
authentication. Folder B has Anonymous turned off and has Basic and
Integrated authentication turned on.

RE: New WebDAV Problems

I attempted to replicate my problem on a Windows 2003 Server running under
Virtual PC 2004, but it wouldn't replicate. I guess it was a bit early to
ask for help if the problem cannot be replicated easily.

I can replicate the problem over and over on different web sites and
different directories on the original server. I tried uninstalling and
re-installing the WebDAV component, but it didn't change anything. I also
disabled IP Filtering (which requires a reboot :P), but that didn't change
anything.

I am still confused as to why this would stop working all-of-a-sudden,
especially across the entire server and not just one folder. Either I made a
change that I don't remember, WindowsUpdate made a change, or possibly a
virus/worm made a change. *shrug*

RE: New WebDAV Problems

Hi Bryan,

If directory listing works fine and just 'open as web folder' doesn't
work, please make sure the WebDAV Web Service extension hasn't been
turned off in IIS and if there is URLScan installed on this server.

312376 How To Configure URLScan to Allow Requests with a Null
Extension in IIS
http://support.microsoft.com/?id=312376

Also, I'd suggest you test with some other client machines with MS
Office installed. Please note the IE6 on a fresh installed Windows
2003 doesn't bulit-in support WebDAV.

Thanks.

Best regards,

WenJun Zhang
Microsoft Online Support
This posting is provided "AS IS" with no warranties, and confers no
rights.
Get Secure! - www.microsoft.com/security

RE: New WebDAV Problems

URLScan was a good guess, but it is not installed. The WebDAV Web Service is
not turned off.

I've tried connecting to this machine's WebDAV from three of my own XP SP2
boxes, from my client's XP SP2 box, and from the server itself. I've used
both the "My Network Places / Add network place" and the "IE / Open Web
Folder" methods to make the connections. In all cases, I get the same
responses:

For the normal folder shared with WebDAV, authenticated non-administrators
receive the error: "The folder you entered does not appear to be valid.
Please choose another. Connectiong to the same folder as an administrator
works just fine."

For the virtual directory folder shared with WebDAV, authenticated users as
well as administrators receive the error: "Documents in this folder are not
available. The folder may hvae been moved or deleted, or network problems
may be preventing a connection to the server."

The virtual directory folder points to the same actual folder as the first
folder to make sure they are set up identically, but they still act
differently.

In all cases as well, I can connect to other WebDAV folders on other servers
from those client machines.

""WenJun Zhang[msft]"" wrote:

> Hi Bryan,
>
> If directory listing works fine and just 'open as web folder' doesn't
> work, please make sure the WebDAV Web Service extension hasn't been
> turned off in IIS and if there is URLScan installed on this server.
>
> 312376 How To Configure URLScan to Allow Requests with a Null
> Extension in IIS
> http://support.microsoft.com/?id=312376
>
> Also, I'd suggest you test with some other client machines with MS
> Office installed. Please note the IE6 on a fresh installed Windows
> 2003 doesn't bulit-in support WebDAV.

RE: New WebDAV Problems

> For the normal folder shared with WebDAV, authenticated non-administrators
> receive the error: "The folder you entered does not appear to be valid.
> Please choose another. Connectiong to the same folder as an administrator
> works just fine."

Woops, I put the quote in the wrong place. This should have been:

For the normal folder shared with WebDAV, authenticated non-administrators
receive the error: "The folder you entered does not appear to be valid.
Please choose another." Connectiong to the same folder as an administrator
works just fine.

:-)
Bryan

RE: New WebDAV Problems

Hi Bryan,

Please further check if the site and virtual directory has been
extended in FPSE(FrontPage Server Extension). If so, the
accessibility of WebDAV is controled by FPSE. The symptom: non-admin
user cannnot open web folder but admins can is very like non-admin
hasn't been granted with at least Author role in FPSE on this site.

You can browse to Microsoft SharePoint Administration site to check
the FPSE setting. If the problematic site is actually extended, go to
its site administration to verify its user control and role setting.

Let me know if problem still persists. We'd review IIS log to
determine the root cause.
Best regards,

WenJun Zhang
Microsoft Online Support
This posting is provided "AS IS" with no warranties, and confers no
rights.
Get Secure! - www.microsoft.com/security

RE: New WebDAV Problems

That was another good guess. The site was extended, but the virtual
directory was not. Interestingly enough, if I try to extend the virtual
directory, I get an error: You cannot create a web using the URL "/FolderB",
because it is an alias. Use the URL "/FolderA" instead.

So, with FolderA being on an extended FPSE site, that was causing the
problem there. I gave the non-admin user Author access and WebDAV then
worked for her.

FolderB, though, is still weird. It wasn't extended, it can't be extended
actually, and I can't get WebDAV access to it, even with an Admin user. If
FPSE is used for part of a site, could it mess up the WebDAV access for a
non-extended folder?

As a second issue, I really don't need FPSE on the site anymore at all, as
long as turning on WebDAV for the whole site would let me connect and edit
with VS.NET. I'll probably want to turn the FPSE stuff off. It is odd,
though, that I would just begin to have problems with this now. As far as I
know, FPSE have been turned on along with WebDAV for this site for about a
year.

""WenJun Zhang[msft]"" wrote:

> Hi Bryan,
>
> Please further check if the site and virtual directory has been
> extended in FPSE(FrontPage Server Extension). If so, the
> accessibility of WebDAV is controled by FPSE. The symptom: non-admin
> user cannnot open web folder but admins can is very like non-admin
> hasn't been granted with at least Author role in FPSE on this site.
>
> You can browse to Microsoft SharePoint Administration site to check
> the FPSE setting. If the problematic site is actually extended, go to
> its site administration to verify its user control and role setting.
>
> Let me know if problem still persists. We'd review IIS log to
> determine the root cause.
> Best regards,
>
> WenJun Zhang
> Microsoft Online Support
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> Get Secure! - www.microsoft.com/security
>
>

RE: New WebDAV Problems

I ve been trying to make my Web Folder to work for 3 weeks now. I followed
the next link

http://www.microsoft.com/resources/documentation/WindowsServ /2003/standard/proddocs/en-us/Default.asp?url=/resources/doc umentation/WindowsServ/2003/standard/proddocs/en-us/pub_dav_ redirector.asp

I like the approach that user must delete FPSE completely. Removed custom
HTTP headers as well. Why my Win XP SP2 client still trying to load FPSE
then? Any registry settings left? That questions goes to Zhang he looks like
very experiencied helper.

Here is log on my Server 2003 computer.

#Fields: date time s-sitename s-computername s-ip cs-method cs-uri-stem
cs-uri-query s-port cs-username c-ip cs-version cs(User-Agent) cs(Cookie)
cs(Referer) cs-host sc-status sc-substatus sc-win32-status sc-bytes cs-bytes
time-taken
2004-10-26 15:35:24 W3SVC1 SERVER-PII 81.154.189.0 GET /_vti_inf.html - 80 -
146.191.228.3 HTTP/1.0 Mozilla/4.0+(compatible;+MS+FrontPage+6.0) - -
voronov.co.uk 404 0 2 1814 367 953
2004-10-26 15:35:24 W3SVC1 SERVER-PII 81.154.189.0 POST
/_vti_bin/shtml.exe/_vti_rpc - 80 - 146.191.228.3 HTTP/1.0 MSFrontPage/6.0 -
- voronov.co.uk 401 2 2148074254 1891 442 390

RE: New WebDAV Problems

Bryan,

Since you are not usign FPSE on this site. I suggest you clearly
remove it to let IIS handle WebDAV and test again. You can follow the
instruction below:

Working with Distributed Authoring and Versioning (DAV) and Web
Folders
http://support.microsoft.com/?id=221600

Besides this, remove the 'MicrosoftOfficeWebServer: 5.0_Pub' header
from the list of Custom HTTP headers (set on the HTTP Headers tab of
the web site's properties dialog) and make sure fpexedll.dll ISAPI
filter has been removed during the uninstallation.

Best regards,

WenJun Zhang
Microsoft Online Support
This posting is provided "AS IS" with no warranties, and confers no
rights.
Get Secure! - www.microsoft.com/security

RE: New WebDAV Problems

Andy,

Has the 'MicrosoftOfficeWebServer: 5.0_Pub' header been removed from
the list of Custom HTTP headers (set on the HTTP Headers tab of the
web site's properties dialog)? If so, this should not happen.

Best regards,

WenJun Zhang
Microsoft Online Support
This posting is provided "AS IS" with no warranties, and confers no
rights.
Get Secure! - www.microsoft.com/security

RE: New WebDAV Problems

I removed FPSE following those directions, and I made sure the fpexedll.dll
ISAPI filter was no longer in use and the 'MicrosoftOfficeWebServer: 5.0_Pub'
header was removed. I then continued with the WebDAV test from the
directions, and I ended up with the same error as before. So now, I guess we
have ruled out FPSE as the problem?

""WenJun Zhang[msft]"" wrote:

> Bryan,
>
> Since you are not usign FPSE on this site. I suggest you clearly
> remove it to let IIS handle WebDAV and test again. You can follow the
> instruction below:
>
> Working with Distributed Authoring and Versioning (DAV) and Web
> Folders
> http://support.microsoft.com/?id=221600
>
> Besides this, remove the 'MicrosoftOfficeWebServer: 5.0_Pub' header
> from the list of Custom HTTP headers (set on the HTTP Headers tab of
> the web site's properties dialog) and make sure fpexedll.dll ISAPI
> filter has been removed during the uninstallation.
>
> Best regards,
>
> WenJun Zhang
> Microsoft Online Support
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> Get Secure! - www.microsoft.com/security
>
>

RE: New WebDAV Problems

Bryan,

Please reproduce the error for several times and collect IIS log in
\WINNT\system32\LogFiles\W3SVC1
We should be able to find clues from it.

Thanks.

Best regards,

WenJun Zhang
Microsoft Online Support
This posting is provided "AS IS" with no warranties, and confers no
rights.
Get Secure! - www.microsoft.com/security

Re: New WebDAV Problems

I had this exact problem just start happening to me as well. We have had a
webdav folder running for 2 years and all of a sudden it stoped working.
The message is
Documents in this folder are not available. The folder may have been moved
or deleted, or network problems my be preventing a connection to the server.
This started happening after i installed the latest security fixes. Were
were 7 fixes that were installed so i don't know which one may have caused
the issue. Web folder won't work for any virtual directory. Web folders
will work if the directory is not a virtual directory.
""WenJun Zhang[msft]"" wrote in message
news:dq7L5mNvEHA.2092@cpmsftngxa10.phx.gbl...
> Bryan,
>
> Please reproduce the error for several times and collect IIS log in
> \WINNT\system32\LogFiles\W3SVC1
> We should be able to find clues from it.
>
> Thanks.
>
> Best regards,
>
> WenJun Zhang
> Microsoft Online Support
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> Get Secure! - www.microsoft.com/security
>

Re: New WebDAV Problems

Yay! I'm not going crazy! Oh, I mean, sorry you're having problems, Jim.

(WenJun, I'll get the logs for you shortly.)

Bryan


"Jim Field" wrote:

> I had this exact problem just start happening to me as well. We have had a
> webdav folder running for 2 years and all of a sudden it stoped working.
> The message is
> Documents in this folder are not available. The folder may have been moved
> or deleted, or network problems my be preventing a connection to the server.
> This started happening after i installed the latest security fixes. Were
> were 7 fixes that were installed so i don't know which one may have caused
> the issue. Web folder won't work for any virtual directory. Web folders
> will work if the directory is not a virtual directory.
> ""WenJun Zhang[msft]"" wrote in message
> news:dq7L5mNvEHA.2092@cpmsftngxa10.phx.gbl...
> > Bryan,
> >
> > Please reproduce the error for several times and collect IIS log in
> > \WINNT\system32\LogFiles\W3SVC1
> > We should be able to find clues from it.
> >
> > Thanks.
> >
> > Best regards,
> >
> > WenJun Zhang
> > Microsoft Online Support

Re: Big WebDAV Problems

Not only Jim having problems. I bet I removed all FPE using owsadm -o
fulluninstall and Web Folder didnt work from beginning when no any extensions
were installed at all. I visited my friend at weekend he has Windows XP SP2
connected to internet through dial up modem. First I thought my Firewall at
Uni does not allow HTTP/1.1 but thats not true. Have a look at log please

#Fields: date time s-sitename s-computername s-ip cs-method cs-uri-stem
cs-uri-query s-port cs-username c-ip cs-version cs(User-Agent) cs(Cookie)
cs(Referer) cs-host sc-status sc-substatus sc-win32-status sc-bytes cs-bytes
time-taken
2004-11-01 18:45:18 W3SVC1 SERVER-PII 81.152.63.9 GET /WebDAV - 80 -
200.96.151.169 HTTP/1.1
Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.1;+SV1;+.NET +CLR+1.1.4322) -
http://www.microsoft.com/office/community/pt-br/default.mspx ?query=webdav&dg=&cat=en&lang=en&cr=&pt=&catlist=&dglist=&pt list=&exp=&sloc=pt-br
voronov.co.uk 401 2 2148074254 1862 378 10671
2004-11-01 18:45:18 W3SVC1 SERVER-PII 81.152.63.9 GET /WebDAV - 80 TEST
200.96.151.169 HTTP/1.1
Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.1;+SV1;+.NET +CLR+1.1.4322) -
http://www.microsoft.com/office/community/pt-br/default.mspx ?query=webdav&dg=&cat=en&lang=en&cr=&pt=&catlist=&dglist=&pt list=&exp=&sloc=pt-br
voronov.co.uk 200 0 0 672 417 359
2004-11-01 18:46:38 W3SVC1 SERVER-PII 81.152.63.9 OPTIONS / - 80 -
200.96.151.169 HTTP/1.1 Microsoft-WebDAV-MiniRedir/5.1.2600 - - voronov.co.uk
200 0 0 425 149 3656
2004-11-01 18:46:38 W3SVC1 SERVER-PII 81.152.63.9 PROPFIND /WebDAV - 80 -
200.96.151.169 HTTP/1.1 Microsoft-WebDAV-MiniRedir/5.1.2600 - - voronov.co.uk
401 2 64 0 166 343
2004-11-01 18:46:46 W3SVC1 SERVER-PII 81.152.63.9 PROPFIND /WebDAV - 80 -
200.96.151.169 HTTP/1.1 Microsoft-WebDAV-MiniRedir/5.1.2600 - - voronov.co.uk
401 2 64 0 166 343
2004-11-01 18:46:53 W3SVC1 SERVER-PII 81.152.63.9 PROPFIND /WebDAV - 80 -
200.96.151.169 HTTP/1.1 Microsoft-WebDAV-MiniRedir/5.1.2600 - - voronov.co.uk
401 2 64 0 166 343
2004-11-01 18:47:01 W3SVC1 SERVER-PII 81.152.63.9 PROPFIND /WebDAV - 80 -
200.96.151.169 HTTP/1.1 Microsoft-WebDAV-MiniRedir/5.1.2600 - - voronov.co.uk
401 2 64 0 166 343

His computer just keeps asking for user name and password as my work comp
does even I entered them correctly. Can see my folder only in default view if
enter the same user name/password. I bet net use * works better in 1994 than
ten years later. Good work, great software what else can I say?

Decided install VPN instead thought wount be any problems if I just follow
the wizard. But I have USB modem and its not listed when wizard asks which
interface connected to internet. Thats mean I must spend time digging into
all VPN features. I would agree that its topic for another message board but
is that very rare situation when users have modem internet connection?

RE: New WebDAV Problems

Hello, I've been having the same problem on a couple Windows 2003 Servers
and a Windows 2000 Server.

I just resolved it on the 2003 server, but can't say exactly how.

The problem: When I tried to access http://server/DAVTest from IE as a web
folder (or network places/wizard), I couldn't authenticate (keeps asking for
user and pass).

I created a WebDAV site:
http://Server/sites/Site-Name

and created some docs, etc.

Then I was able to create a map to http://Server/sites/Site-Name/doclib
and to http://Server/DAVTest

I don't know if this resolved it or it's a coincidence. I do remember I
uploaded docs and pictures from the client machine and something got
installed on my machine (win XP, SP1, office 2002).

Hope this helps.






"sypher@nospam.nospam" wrote:

> I attempted to replicate my problem on a Windows 2003 Server running under
> Virtual PC 2004, but it wouldn't replicate. I guess it was a bit early to
> ask for help if the problem cannot be replicated easily.
>
> I can replicate the problem over and over on different web sites and
> different directories on the original server. I tried uninstalling and
> re-installing the WebDAV component, but it didn't change anything. I also
> disabled IP Filtering (which requires a reboot :P), but that didn't change
> anything.
>
> I am still confused as to why this would stop working all-of-a-sudden,
> especially across the entire server and not just one folder. Either I made a
> change that I don't remember, WindowsUpdate made a change, or possibly a
> virus/worm made a change. *shrug*