| |
| |||||||
| Windows Vista Discuss the different versions of Windows Vista, Fuji, or Vienna |
 |
| | LinkBack | Thread Tools |
01-02-2007, 11:17 AM
| |||
| |||
| Re: WebDav Hi Jeff- yes it is a requirement to support Depth:0 PROPFIND. It is not quite "new" for Vista since the Webdav Redirector that shipped with Windows XP had the same requirement. However, the difference is that Vista doesn't have Webfolder (another client for WebDAV) shipped inbox with Vista anymore and the WebDAV redirector (the WebDAV client that lets you map drives to a WebDAV resource) is used instead. With this, comes the limitation of supporting PROPFIND at root. Thanks. -Ather "JJK" wrote: [color=blue] > Ather, > Is the requirement for the root directory to support PROPFIND method > (with Depth: 0) new for Vista? It appears that the pre-Vista OS WebDAV > clients were able to communicate with WebDAV server that only allows OPTIONS > for the root directory. Please confirm. > > Thanks, > Jeff > > "Ather Haleem (MSFT)" wrote: >[color=green] > > It is possible that the root of the website ([url]https://sub.server.ext[/url]) doesn't > > honor OPTIONS or PROPFIND request bur /folder does. If that is the case, this > > is expected and by design and the workaround is to have the root also honor > > OPTIONS and PROPFIND request. This is most likely the reason why this is > > failing. > > > > Thanks. > > -Ather > > > > > > "Floris" wrote: > >[color=darkred] > > > Hi Ather, > > > > > > With IE, I'm now able to get the 'default' HTML page of the webfolder (after > > > I enter my credentials) by enabling 'Send LM & NTLM - use NTLMv2 session > > > security if negotiated' in the Administrative Tools section of the Control > > > Panel. Before that was enabled, this wasn´t possible. > > > > > > However, if I try to open the location as a webfolder (using a link on that > > > default HTML page or by using the Add Network Location wizard), I keep > > > getting the auth dialog. > > > > > > The net use command results in the following output: > > > --- > > > C:\Users\Floris>net use * [url]https://sub.server.ext/folder[/url] > > > Enter the user name for 'sub.server.ext': floris > > > Enter the password for sub.server.ext: > > > System error 67 has occurred. > > > The network name cannot be found. > > > --- > > > > > > Anyway, 'telnet sub.server.ext 443' does result in a connection. > > > > > > "Ather Haleem (MSFT)" wrote: > > > > > > > Hi Floris, > > > > Can you try and see if you are able to re-produce the same problem if you > > > > try to access this WebDAV resource via Internet Explorer? Also, can you check > > > > to see if "net use * <https-webdav-resources>" works via command prompt? > > > > > > > > thanks. > > > > > > > > -Ather > > > > lead software design engineer/test | windows core file systems | micorosft > > > > corporation > > > > > > > > > > > > > > > > > > > > "Rick Rogers" wrote: > > > > > > > > > Unfortunately, I don't know enough about Linux' server to tell you what else > > > > > to try. You may want to check in a 'nix group to see if others have run into > > > > > this with Vista. It may be that one of Vista's default networking protocols > > > > > isn't in a compatible format. > > > > > > > > > > -- > > > > > Best of Luck, > > > > > > > > > > Rick Rogers, aka "Nutcase" - Microsoft MVP > > > > > [url]http://mvp.support.microsoft.com/[/url] > > > > > Windows help - [url]www.rickrogers.org[/url] > > > > > > > > > > "Floris" <Floris@discussions.microsoft.com> wrote in message > > > > > news:76260B24-B3CC-427A-8574-F863A61539CD@microsoft.com... > > > > > > Yes :) > > > > > > > > > > > > "Rick Rogers" wrote: > > > > > > > > > > > >> Hi, > > > > > >> > > > > > >> So to be clear, did you try logging on while IPv6 was disabled? > > > > > >> > > > > > >> -- > > > > > >> Best of Luck, > > > > > >> > > > > > >> Rick Rogers, aka "Nutcase" - Microsoft MVP > > > > > >> [url]http://mvp.support.microsoft.com/[/url] > > > > > >> Windows help - [url]www.rickrogers.org[/url] > > > > > >> > > > > > >> "Floris" <Floris@discussions.microsoft.com> wrote in message > > > > > >> news:ED8D12CE-8EDE-40DE-98EA-27EB641C668C@microsoft.com... > > > > > >> > Thanks for your quick reply! I disabled the IPv6 option in the nic > > > > > >> > properties, disabled it, and enabled it again. However, the problem > > > > > >> > still > > > > > >> > exists. Also, the webserver reports the same error. > > > > > >> > > > > > > >> > "Rick Rogers" wrote: > > > > > >> > > > > > > >> >> Hi, > > > > > >> >> > > > > > >> >> Some have reported that disabling IPv6 has resolved this issue. You'll > > > > > >> >> find > > > > > >> >> it in the properties of the 'nic in Device Manager. > > > > > >> >> > > > > > >> >> -- > > > > > >> >> Best of Luck, > > > > > >> >> > > > > > >> >> Rick Rogers, aka "Nutcase" - Microsoft MVP > > > > > >> >> [url]http://mvp.support.microsoft.com/[/url] > > > > > >> >> Windows help - [url]www.rickrogers.org[/url] > > > > > >> >> > > > > > >> >> "Floris" <Floris@discussions.microsoft.com> wrote in message > > > > > >> >> news:99B79762-0549-4E00-ACFF-12C2B9D496DC@microsoft.com... > > > > > >> >> >I just installed Windows Vista Business N. With my previous XP > > > > > >> >> >installation, > > > > > >> >> > I could easily connect to a https-webdav location using Add Network > > > > > >> >> > Location. > > > > > >> >> > Unfortunately, with Vista, I'm unable to pass the authentication. > > > > > >> >> > I'm -very- > > > > > >> >> > sure that I'm using the right credentials. However, the auth dialog > > > > > >> >> > keeps > > > > > >> >> > popping up. > > > > > >> >> > > > > > > >> >> > I managed to get some logging from the Linux server I'm logging into > > > > > >> >> > (samba.log): > > > > > >> >> > [2006/12/07 17:41:36, 2] auth/auth.c:check_ntlm_password(319) > > > > > >> >> > check_ntlm_password: Authentication for user [FLORIS] -> [FLORIS] > > > > > >> >> > FAILED > > > > > >> >> > with error NT_STATUS_WRONG_PASSWORD > > > > > >> >> > [2006/12/07 17:41:36, 3] smbd/error.c:error_packet(146) > > > > > >> >> > error packet at smbd/sesssetup.c(1093) cmd=115 (SMBsesssetupX) > > > > > >> >> > NT_STATUS_LOGON_FAILURE > > > > > >> >> > > > > > > >> >> > With the same credentials, I'm able to login using a Win2000 > > > > > >> >> > computer. > > > > > >> >> > > > > > > >> >> > Any thoughts on this? > > > > > >> >> > > > > > >> >> > > > > > >> > > > > > >> > > > > > > > > > >[/color][/color][/color]      |
|
01-02-2007, 11:17 AM
| ||
| |
|
01-02-2007, 11:17 AM
| |||
| |||
| Re: WebDav Hi Jeff- yes it is a requirement to support Depth:0 PROPFIND. It is not quite "new" for Vista since the Webdav Redirector that shipped with Windows XP had the same requirement. However, the difference is that Vista doesn't have Webfolder (another client for WebDAV) shipped inbox with Vista anymore and the WebDAV redirector (the WebDAV client that lets you map drives to a WebDAV resource) is used instead. With this, comes the limitation of supporting PROPFIND at root. Thanks. -Ather "JJK" wrote: [color=blue] > Ather, > Is the requirement for the root directory to support PROPFIND method > (with Depth: 0) new for Vista? It appears that the pre-Vista OS WebDAV > clients were able to communicate with WebDAV server that only allows OPTIONS > for the root directory. Please confirm. > > Thanks, > Jeff > > "Ather Haleem (MSFT)" wrote: >[color=green] > > It is possible that the root of the website ([url]https://sub.server.ext[/url]) doesn't > > honor OPTIONS or PROPFIND request bur /folder does. If that is the case, this > > is expected and by design and the workaround is to have the root also honor > > OPTIONS and PROPFIND request. This is most likely the reason why this is > > failing. > > > > Thanks. > > -Ather > > > > > > "Floris" wrote: > >[color=darkred] > > > Hi Ather, > > > > > > With IE, I'm now able to get the 'default' HTML page of the webfolder (after > > > I enter my credentials) by enabling 'Send LM & NTLM - use NTLMv2 session > > > security if negotiated' in the Administrative Tools section of the Control > > > Panel. Before that was enabled, this wasn´t possible. > > > > > > However, if I try to open the location as a webfolder (using a link on that > > > default HTML page or by using the Add Network Location wizard), I keep > > > getting the auth dialog. > > > > > > The net use command results in the following output: > > > --- > > > C:\Users\Floris>net use * [url]https://sub.server.ext/folder[/url] > > > Enter the user name for 'sub.server.ext': floris > > > Enter the password for sub.server.ext: > > > System error 67 has occurred. > > > The network name cannot be found. > > > --- > > > > > > Anyway, 'telnet sub.server.ext 443' does result in a connection. > > > > > > "Ather Haleem (MSFT)" wrote: > > > > > > > Hi Floris, > > > > Can you try and see if you are able to re-produce the same problem if you > > > > try to access this WebDAV resource via Internet Explorer? Also, can you check > > > > to see if "net use * <https-webdav-resources>" works via command prompt? > > > > > > > > thanks. > > > > > > > > -Ather > > > > lead software design engineer/test | windows core file systems | micorosft > > > > corporation > > > > > > > > > > > > > > > > > > > > "Rick Rogers" wrote: > > > > > > > > > Unfortunately, I don't know enough about Linux' server to tell you what else > > > > > to try. You may want to check in a 'nix group to see if others have run into > > > > > this with Vista. It may be that one of Vista's default networking protocols > > > > > isn't in a compatible format. > > > > > > > > > > -- > > > > > Best of Luck, > > > > > > > > > > Rick Rogers, aka "Nutcase" - Microsoft MVP > > > > > [url]http://mvp.support.microsoft.com/[/url] > > > > > Windows help - [url]www.rickrogers.org[/url] > > > > > > > > > > "Floris" <Floris@discussions.microsoft.com> wrote in message > > > > > news:76260B24-B3CC-427A-8574-F863A61539CD@microsoft.com... > > > > > > Yes :) > > > > > > > > > > > > "Rick Rogers" wrote: > > > > > > > > > > > >> Hi, > > > > > >> > > > > > >> So to be clear, did you try logging on while IPv6 was disabled? > > > > > >> > > > > > >> -- > > > > > >> Best of Luck, > > > > > >> > > > > > >> Rick Rogers, aka "Nutcase" - Microsoft MVP > > > > > >> [url]http://mvp.support.microsoft.com/[/url] > > > > > >> Windows help - [url]www.rickrogers.org[/url] > > > > > >> > > > > > >> "Floris" <Floris@discussions.microsoft.com> wrote in message > > > > > >> news:ED8D12CE-8EDE-40DE-98EA-27EB641C668C@microsoft.com... > > > > > >> > Thanks for your quick reply! I disabled the IPv6 option in the nic > > > > > >> > properties, disabled it, and enabled it again. However, the problem > > > > > >> > still > > > > > >> > exists. Also, the webserver reports the same error. > > > > > >> > > > > > > >> > "Rick Rogers" wrote: > > > > > >> > > > > > > >> >> Hi, > > > > > >> >> > > > > > >> >> Some have reported that disabling IPv6 has resolved this issue. You'll > > > > > >> >> find > > > > > >> >> it in the properties of the 'nic in Device Manager. > > > > > >> >> > > > > > >> >> -- > > > > > >> >> Best of Luck, > > > > > >> >> > > > > > >> >> Rick Rogers, aka "Nutcase" - Microsoft MVP > > > > > >> >> [url]http://mvp.support.microsoft.com/[/url] > > > > > >> >> Windows help - [url]www.rickrogers.org[/url] > > > > > >> >> > > > > > >> >> "Floris" <Floris@discussions.microsoft.com> wrote in message > > > > > >> >> news:99B79762-0549-4E00-ACFF-12C2B9D496DC@microsoft.com... > > > > > >> >> >I just installed Windows Vista Business N. With my previous XP > > > > > >> >> >installation, > > > > > >> >> > I could easily connect to a https-webdav location using Add Network > > > > > >> >> > Location. > > > > > >> >> > Unfortunately, with Vista, I'm unable to pass the authentication. > > > > > >> >> > I'm -very- > > > > > >> >> > sure that I'm using the right credentials. However, the auth dialog > > > > > >> >> > keeps > > > > > >> >> > popping up. > > > > > >> >> > > > > > > >> >> > I managed to get some logging from the Linux server I'm logging into > > > > > >> >> > (samba.log): > > > > > >> >> > [2006/12/07 17:41:36, 2] auth/auth.c:check_ntlm_password(319) > > > > > >> >> > check_ntlm_password: Authentication for user [FLORIS] -> [FLORIS] > > > > > >> >> > FAILED > > > > > >> >> > with error NT_STATUS_WRONG_PASSWORD > > > > > >> >> > [2006/12/07 17:41:36, 3] smbd/error.c:error_packet(146) > > > > > >> >> > error packet at smbd/sesssetup.c(1093) cmd=115 (SMBsesssetupX) > > > > > >> >> > NT_STATUS_LOGON_FAILURE > > > > > >> >> > > > > > > >> >> > With the same credentials, I'm able to login using a Win2000 > > > > > >> >> > computer. > > > > > >> >> > > > > > > >> >> > Any thoughts on this? > > > > > >> >> > > > > > >> >> > > > > > >> > > > > > >> > > > > > > > > > >[/color][/color][/color] |
|
01-02-2007, 11:18 AM
| |||
| |||
| Re: WebDav Ather, Thank you for the clarification. I seem to encounter some dilemma here, and I am not sure if it's intended or by design. The scenario is, the user needs to logon to get a cookie to the server first. Furthermore, the user only has permission to access directory such as /users/foo/bar, but not the ones above. When the user tries to access that WebDAV resource, two different things would happen: 1. If IE7 is running protected mode (or the URL is not in the trusted zone), the WebDAV redirector did not send the cookie to the server. However, it ignored the returned 403 responses and crawled all the way to the /users/foo/bar directory (which again was rejected due to no cookie present in the request). 2. If IE7 is running non-protected mode (or the URL is listed in the trusted security zone), the WebDAV redirector did send the cookie to the server. However, it only tried the / and /users directories several times and gave up upon 403 responses. Is this expected behavior for Vista WebDAV mini-redirector? Will the installation of the Office product change the way how it behaves? Thanks again, Jeff "Ather Haleem (MSFT)" wrote: [color=blue] > Hi Jeff- yes it is a requirement to support Depth:0 PROPFIND. It is not quite > "new" for Vista since the Webdav Redirector that shipped with Windows XP had > the same requirement. However, the difference is that Vista doesn't have > Webfolder (another client for WebDAV) shipped inbox with Vista anymore and > the WebDAV redirector (the WebDAV client that lets you map drives to a WebDAV > resource) is used instead. With this, comes the limitation of supporting > PROPFIND at root. > > Thanks. > -Ather > > "JJK" wrote: >[color=green] > > Ather, > > Is the requirement for the root directory to support PROPFIND method > > (with Depth: 0) new for Vista? It appears that the pre-Vista OS WebDAV > > clients were able to communicate with WebDAV server that only allows OPTIONS > > for the root directory. Please confirm. > > > > Thanks, > > Jeff > > > > "Ather Haleem (MSFT)" wrote: > >[color=darkred] > > > It is possible that the root of the website ([url]https://sub.server.ext[/url]) doesn't > > > honor OPTIONS or PROPFIND request bur /folder does. If that is the case, this > > > is expected and by design and the workaround is to have the root also honor > > > OPTIONS and PROPFIND request. This is most likely the reason why this is > > > failing. > > > > > > Thanks. > > > -Ather > > > > > > > > > "Floris" wrote: > > > > > > > Hi Ather, > > > > > > > > With IE, I'm now able to get the 'default' HTML page of the webfolder (after > > > > I enter my credentials) by enabling 'Send LM & NTLM - use NTLMv2 session > > > > security if negotiated' in the Administrative Tools section of the Control > > > > Panel. Before that was enabled, this wasn´t possible. > > > > > > > > However, if I try to open the location as a webfolder (using a link on that > > > > default HTML page or by using the Add Network Location wizard), I keep > > > > getting the auth dialog. > > > > > > > > The net use command results in the following output: > > > > --- > > > > C:\Users\Floris>net use * [url]https://sub.server.ext/folder[/url] > > > > Enter the user name for 'sub.server.ext': floris > > > > Enter the password for sub.server.ext: > > > > System error 67 has occurred. > > > > The network name cannot be found. > > > > --- > > > > > > > > Anyway, 'telnet sub.server.ext 443' does result in a connection. > > > > > > > > "Ather Haleem (MSFT)" wrote: > > > > > > > > > Hi Floris, > > > > > Can you try and see if you are able to re-produce the same problem if you > > > > > try to access this WebDAV resource via Internet Explorer? Also, can you check > > > > > to see if "net use * <https-webdav-resources>" works via command prompt? > > > > > > > > > > thanks. > > > > > > > > > > -Ather > > > > > lead software design engineer/test | windows core file systems | micorosft > > > > > corporation > > > > > > > > > > > > > > > > > > > > > > > > > "Rick Rogers" wrote: > > > > > > > > > > > Unfortunately, I don't know enough about Linux' server to tell you what else > > > > > > to try. You may want to check in a 'nix group to see if others have run into > > > > > > this with Vista. It may be that one of Vista's default networking protocols > > > > > > isn't in a compatible format. > > > > > > > > > > > > -- > > > > > > Best of Luck, > > > > > > > > > > > > Rick Rogers, aka "Nutcase" - Microsoft MVP > > > > > > [url]http://mvp.support.microsoft.com/[/url] > > > > > > Windows help - [url]www.rickrogers.org[/url] > > > > > > > > > > > > "Floris" <Floris@discussions.microsoft.com> wrote in message > > > > > > news:76260B24-B3CC-427A-8574-F863A61539CD@microsoft.com... > > > > > > > Yes :) > > > > > > > > > > > > > > "Rick Rogers" wrote: > > > > > > > > > > > > > >> Hi, > > > > > > >> > > > > > > >> So to be clear, did you try logging on while IPv6 was disabled? > > > > > > >> > > > > > > >> -- > > > > > > >> Best of Luck, > > > > > > >> > > > > > > >> Rick Rogers, aka "Nutcase" - Microsoft MVP > > > > > > >> [url]http://mvp.support.microsoft.com/[/url] > > > > > > >> Windows help - [url]www.rickrogers.org[/url] > > > > > > >> > > > > > > >> "Floris" <Floris@discussions.microsoft.com> wrote in message > > > > > > >> news:ED8D12CE-8EDE-40DE-98EA-27EB641C668C@microsoft.com... > > > > > > >> > Thanks for your quick reply! I disabled the IPv6 option in the nic > > > > > > >> > properties, disabled it, and enabled it again. However, the problem > > > > > > >> > still > > > > > > >> > exists. Also, the webserver reports the same error. > > > > > > >> > > > > > > > >> > "Rick Rogers" wrote: > > > > > > >> > > > > > > > >> >> Hi, > > > > > > >> >> > > > > > > >> >> Some have reported that disabling IPv6 has resolved this issue. You'll > > > > > > >> >> find > > > > > > >> >> it in the properties of the 'nic in Device Manager. > > > > > > >> >> > > > > > > >> >> -- > > > > > > >> >> Best of Luck, > > > > > > >> >> > > > > > > >> >> Rick Rogers, aka "Nutcase" - Microsoft MVP > > > > > > >> >> [url]http://mvp.support.microsoft.com/[/url] > > > > > > >> >> Windows help - [url]www.rickrogers.org[/url] > > > > > > >> >> > > > > > > >> >> "Floris" <Floris@discussions.microsoft.com> wrote in message > > > > > > >> >> news:99B79762-0549-4E00-ACFF-12C2B9D496DC@microsoft.com... > > > > > > >> >> >I just installed Windows Vista Business N. With my previous XP > > > > > > >> >> >installation, > > > > > > >> >> > I could easily connect to a https-webdav location using Add Network > > > > > > >> >> > Location. > > > > > > >> >> > Unfortunately, with Vista, I'm unable to pass the authentication. > > > > > > >> >> > I'm -very- > > > > > > >> >> > sure that I'm using the right credentials. However, the auth dialog > > > > > > >> >> > keeps > > > > > > >> >> > popping up. > > > > > > >> >> > > > > > > > >> >> > I managed to get some logging from the Linux server I'm logging into > > > > > > >> >> > (samba.log): > > > > > > >> >> > [2006/12/07 17:41:36, 2] auth/auth.c:check_ntlm_password(319) > > > > > > >> >> > check_ntlm_password: Authentication for user [FLORIS] -> [FLORIS] > > > > > > >> >> > FAILED > > > > > > >> >> > with error NT_STATUS_WRONG_PASSWORD > > > > > > >> >> > [2006/12/07 17:41:36, 3] smbd/error.c:error_packet(146) > > > > > > >> >> > error packet at smbd/sesssetup.c(1093) cmd=115 (SMBsesssetupX) > > > > > > >> >> > NT_STATUS_LOGON_FAILURE > > > > > > >> >> > > > > > > > >> >> > With the same credentials, I'm able to login using a Win2000 > > > > > > >> >> > computer. > > > > > > >> >> > > > > > > > >> >> > Any thoughts on this? > > > > > > >> >> > > > > > > >> >> > > > > > > >> > > > > > > >> > > > > > > > > > > > >[/color][/color][/color] |
|
01-02-2007, 11:18 AM
| |||
| |||
| Re: WebDav Ather, Thank you for the clarification. I seem to encounter some dilemma here, and I am not sure if it's intended or by design. The scenario is, the user needs to logon to get a cookie to the server first. Furthermore, the user only has permission to access directory such as /users/foo/bar, but not the ones above. When the user tries to access that WebDAV resource, two different things would happen: 1. If IE7 is running protected mode (or the URL is not in the trusted zone), the WebDAV redirector did not send the cookie to the server. However, it ignored the returned 403 responses and crawled all the way to the /users/foo/bar directory (which again was rejected due to no cookie present in the request). 2. If IE7 is running non-protected mode (or the URL is listed in the trusted security zone), the WebDAV redirector did send the cookie to the server. However, it only tried the / and /users directories several times and gave up upon 403 responses. Is this expected behavior for Vista WebDAV mini-redirector? Will the installation of the Office product change the way how it behaves? Thanks again, Jeff "Ather Haleem (MSFT)" wrote: [color=blue] > Hi Jeff- yes it is a requirement to support Depth:0 PROPFIND. It is not quite > "new" for Vista since the Webdav Redirector that shipped with Windows XP had > the same requirement. However, the difference is that Vista doesn't have > Webfolder (another client for WebDAV) shipped inbox with Vista anymore and > the WebDAV redirector (the WebDAV client that lets you map drives to a WebDAV > resource) is used instead. With this, comes the limitation of supporting > PROPFIND at root. > > Thanks. > -Ather > > "JJK" wrote: >[color=green] > > Ather, > > Is the requirement for the root directory to support PROPFIND method > > (with Depth: 0) new for Vista? It appears that the pre-Vista OS WebDAV > > clients were able to communicate with WebDAV server that only allows OPTIONS > > for the root directory. Please confirm. > > > > Thanks, > > Jeff > > > > "Ather Haleem (MSFT)" wrote: > >[color=darkred] > > > It is possible that the root of the website ([url]https://sub.server.ext[/url]) doesn't > > > honor OPTIONS or PROPFIND request bur /folder does. If that is the case, this > > > is expected and by design and the workaround is to have the root also honor > > > OPTIONS and PROPFIND request. This is most likely the reason why this is > > > failing. > > > > > > Thanks. > > > -Ather > > > > > > > > > "Floris" wrote: > > > > > > > Hi Ather, > > > > > > > > With IE, I'm now able to get the 'default' HTML page of the webfolder (after > > > > I enter my credentials) by enabling 'Send LM & NTLM - use NTLMv2 session > > > > security if negotiated' in the Administrative Tools section of the Control > > > > Panel. Before that was enabled, this wasn´t possible. > > > > > > > > However, if I try to open the location as a webfolder (using a link on that > > > > default HTML page or by using the Add Network Location wizard), I keep > > > > getting the auth dialog. > > > > > > > > The net use command results in the following output: > > > > --- > > > > C:\Users\Floris>net use * [url]https://sub.server.ext/folder[/url] > > > > Enter the user name for 'sub.server.ext': floris > > > > Enter the password for sub.server.ext: > > > > System error 67 has occurred. > > > > The network name cannot be found. > > > > --- > > > > > > > > Anyway, 'telnet sub.server.ext 443' does result in a connection. > > > > > > > > "Ather Haleem (MSFT)" wrote: > > > > > > > > > Hi Floris, > > > > > Can you try and see if you are able to re-produce the same problem if you > > > > > try to access this WebDAV resource via Internet Explorer? Also, can you check > > > > > to see if "net use * <https-webdav-resources>" works via command prompt? > > > > > > > > > > thanks. > > > > > > > > > > -Ather > > > > > lead software design engineer/test | windows core file systems | micorosft > > > > > corporation > > > > > > > > > > > > > > > > > > > > > > > > > "Rick Rogers" wrote: > > > > > > > > > > > Unfortunately, I don't know enough about Linux' server to tell you what else > > > > > > to try. You may want to check in a 'nix group to see if others have run into > > > > > > this with Vista. It may be that one of Vista's default networking protocols > > > > > > isn't in a compatible format. > > > > > > > > > > > > -- > > > > > > Best of Luck, > > > > > > > > > > > > Rick Rogers, aka "Nutcase" - Microsoft MVP > > > > > > [url]http://mvp.support.microsoft.com/[/url] > > > > > > Windows help - [url]www.rickrogers.org[/url] > > > > > > > > > > > > "Floris" <Floris@discussions.microsoft.com> wrote in message > > > > > > news:76260B24-B3CC-427A-8574-F863A61539CD@microsoft.com... > > > > > > > Yes :) > > > > > > > > > > > > > > "Rick Rogers" wrote: > > > > > > > > > > > > > >> Hi, > > > > > > >> > > > > > > >> So to be clear, did you try logging on while IPv6 was disabled? > > > > > > >> > > > > > > >> -- > > > > > > >> Best of Luck, > > > > > > >> > > > > > > >> Rick Rogers, aka "Nutcase" - Microsoft MVP > > > > > > >> [url]http://mvp.support.microsoft.com/[/url] > > > > > > >> Windows help - [url]www.rickrogers.org[/url] > > > > > > >> > > > > > > >> "Floris" <Floris@discussions.microsoft.com> wrote in message > > > > > > >> news:ED8D12CE-8EDE-40DE-98EA-27EB641C668C@microsoft.com... > > > > > > >> > Thanks for your quick reply! I disabled the IPv6 option in the nic > > > > > > >> > properties, disabled it, and enabled it again. However, the problem > > > > > > >> > still > > > > > > >> > exists. Also, the webserver reports the same error. > > > > > > >> > > > > > > > >> > "Rick Rogers" wrote: > > > > > > >> > > > > > > > >> >> Hi, > > > > > > >> >> > > > > > > >> >> Some have reported that disabling IPv6 has resolved this issue. You'll > > > > > > >> >> find > > > > > > >> >> it in the properties of the 'nic in Device Manager. > > > > > > >> >> > > > > > > >> >> -- > > > > > > >> >> Best of Luck, > > > > > > >> >> > > > > > > >> >> Rick Rogers, aka "Nutcase" - Microsoft MVP > > > > > > >> >> [url]http://mvp.support.microsoft.com/[/url] > > > > > > >> >> Windows help - [url]www.rickrogers.org[/url] > > > > > > >> >> > > > > > > >> >> "Floris" <Floris@discussions.microsoft.com> wrote in message > > > > > > >> >> news:99B79762-0549-4E00-ACFF-12C2B9D496DC@microsoft.com... > > > > > > >> >> >I just installed Windows Vista Business N. With my previous XP > > > > > > >> >> >installation, > > > > > > >> >> > I could easily connect to a https-webdav location using Add Network > > > > > > >> >> > Location. > > > > > > >> >> > Unfortunately, with Vista, I'm unable to pass the authentication. > > > > > > >> >> > I'm -very- > > > > > > >> >> > sure that I'm using the right credentials. However, the auth dialog > > > > > > >> >> > keeps > > > > > > >> >> > popping up. > > > > > > >> >> > > > > > > > >> >> > I managed to get some logging from the Linux server I'm logging into > > > > > > >> >> > (samba.log): > > > > > > >> >> > [2006/12/07 17:41:36, 2] auth/auth.c:check_ntlm_password(319) > > > > > > >> >> > check_ntlm_password: Authentication for user [FLORIS] -> [FLORIS] > > > > > > >> >> > FAILED > > > > > > >> >> > with error NT_STATUS_WRONG_PASSWORD > > > > > > >> >> > [2006/12/07 17:41:36, 3] smbd/error.c:error_packet(146) > > > > > > >> >> > error packet at smbd/sesssetup.c(1093) cmd=115 (SMBsesssetupX) > > > > > > >> >> > NT_STATUS_LOGON_FAILURE > > > > > > >> >> > > > > > > > >> >> > With the same credentials, I'm able to login using a Win2000 > > > > > > >> >> > computer. > > > > > > >> >> > > > > > > > >> >> > Any thoughts on this? > > > > > > >> >> > > > > > > >> >> > > > > > > >> > > > > > > >> > > > > > > > > > > > >[/color][/color][/color] |
|
01-02-2007, 11:20 AM
| |||
| |||
| Re: WebDav Hi Jeff, if you run IE7 in protected mode, WebDAV redirector will treat the cookie as unsafe and it will NOT use that cookie for authentication. It will only send the cookie if you first mark the URL as trusted in IE7 and access the website, WebDAV redirector WILL send the cookie for auth. For cookies to work, WebDAV redir first tries the root directory (/). If we get 403 (HTTP_STATUS_FORBIDDEN) back, that essentially means the cookie auth did not work so we don't try further deep in the directory tree. This is also by design. If you want Forms Based Authentication (via cookie) to work, the server needs to accept the cookie at the root. If you install Office 2003, WebFolders WILL get installed however any attempt to add a network connection via explorer or "net use" will still go via WebDAV redirector. I hope that answers your questions. The right way to fix this problem is to have the server honor OPTIONS and PROPFIND requests at the root as well as accept the cookie (for Forms Based Auth). Thanks -Ather "JJK" wrote: [color=blue] > Ather, > Thank you for the clarification. I seem to encounter some dilemma here, > and I am not sure if it's intended or by design. > The scenario is, the user needs to logon to get a cookie to the server > first. Furthermore, the user only has permission to access directory such as > /users/foo/bar, but not the ones above. When the user tries to access that > WebDAV resource, two different things would happen: > > 1. If IE7 is running protected mode (or the URL is not in the trusted zone), > the WebDAV redirector did not send the cookie to the server. However, it > ignored the returned 403 responses and crawled all the way to the > /users/foo/bar directory (which again was rejected due to no cookie present > in the request). > 2. If IE7 is running non-protected mode (or the URL is listed in the trusted > security zone), the WebDAV redirector did send the cookie to the server. > However, it only tried the / and /users directories several times and gave up > upon 403 responses. > > Is this expected behavior for Vista WebDAV mini-redirector? Will the > installation of the Office product change the way how it behaves? > > Thanks again, > Jeff > > "Ather Haleem (MSFT)" wrote: >[color=green] > > Hi Jeff- yes it is a requirement to support Depth:0 PROPFIND. It is not quite > > "new" for Vista since the Webdav Redirector that shipped with Windows XP had > > the same requirement. However, the difference is that Vista doesn't have > > Webfolder (another client for WebDAV) shipped inbox with Vista anymore and > > the WebDAV redirector (the WebDAV client that lets you map drives to a WebDAV > > resource) is used instead. With this, comes the limitation of supporting > > PROPFIND at root. > > > > Thanks. > > -Ather > > > > "JJK" wrote: > >[color=darkred] > > > Ather, > > > Is the requirement for the root directory to support PROPFIND method > > > (with Depth: 0) new for Vista? It appears that the pre-Vista OS WebDAV > > > clients were able to communicate with WebDAV server that only allows OPTIONS > > > for the root directory. Please confirm. > > > > > > Thanks, > > > Jeff > > > > > > "Ather Haleem (MSFT)" wrote: > > > > > > > It is possible that the root of the website ([url]https://sub.server.ext[/url]) doesn't > > > > honor OPTIONS or PROPFIND request bur /folder does. If that is the case, this > > > > is expected and by design and the workaround is to have the root also honor > > > > OPTIONS and PROPFIND request. This is most likely the reason why this is > > > > failing. > > > > > > > > Thanks. > > > > -Ather > > > > > > > > > > > > "Floris" wrote: > > > > > > > > > Hi Ather, > > > > > > > > > > With IE, I'm now able to get the 'default' HTML page of the webfolder (after > > > > > I enter my credentials) by enabling 'Send LM & NTLM - use NTLMv2 session > > > > > security if negotiated' in the Administrative Tools section of the Control > > > > > Panel. Before that was enabled, this wasn´t possible. > > > > > > > > > > However, if I try to open the location as a webfolder (using a link on that > > > > > default HTML page or by using the Add Network Location wizard), I keep > > > > > getting the auth dialog. > > > > > > > > > > The net use command results in the following output: > > > > > --- > > > > > C:\Users\Floris>net use * [url]https://sub.server.ext/folder[/url] > > > > > Enter the user name for 'sub.server.ext': floris > > > > > Enter the password for sub.server.ext: > > > > > System error 67 has occurred. > > > > > The network name cannot be found. > > > > > --- > > > > > > > > > > Anyway, 'telnet sub.server.ext 443' does result in a connection. > > > > > > > > > > "Ather Haleem (MSFT)" wrote: > > > > > > > > > > > Hi Floris, > > > > > > Can you try and see if you are able to re-produce the same problem if you > > > > > > try to access this WebDAV resource via Internet Explorer? Also, can you check > > > > > > to see if "net use * <https-webdav-resources>" works via command prompt? > > > > > > > > > > > > thanks. > > > > > > > > > > > > -Ather > > > > > > lead software design engineer/test | windows core file systems | micorosft > > > > > > corporation > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > "Rick Rogers" wrote: > > > > > > > > > > > > > Unfortunately, I don't know enough about Linux' server to tell you what else > > > > > > > to try. You may want to check in a 'nix group to see if others have run into > > > > > > > this with Vista. It may be that one of Vista's default networking protocols > > > > > > > isn't in a compatible format. > > > > > > > > > > > > > > -- > > > > > > > Best of Luck, > > > > > > > > > > > > > > Rick Rogers, aka "Nutcase" - Microsoft MVP > > > > > > > [url]http://mvp.support.microsoft.com/[/url] > > > > > > > Windows help - [url]www.rickrogers.org[/url] > > > > > > > > > > > > > > "Floris" <Floris@discussions.microsoft.com> wrote in message > > > > > > > news:76260B24-B3CC-427A-8574-F863A61539CD@microsoft.com... > > > > > > > > Yes :) > > > > > > > > > > > > > > > > "Rick Rogers" wrote: > > > > > > > > > > > > > > > >> Hi, > > > > > > > >> > > > > > > > >> So to be clear, did you try logging on while IPv6 was disabled? > > > > > > > >> > > > > > > > >> -- > > > > > > > >> Best of Luck, > > > > > > > >> > > > > > > > >> Rick Rogers, aka "Nutcase" - Microsoft MVP > > > > > > > >> [url]http://mvp.support.microsoft.com/[/url] > > > > > > > >> Windows help - [url]www.rickrogers.org[/url] > > > > > > > >> > > > > > > > >> "Floris" <Floris@discussions.microsoft.com> wrote in message > > > > > > > >> news:ED8D12CE-8EDE-40DE-98EA-27EB641C668C@microsoft.com... > > > > > > > >> > Thanks for your quick reply! I disabled the IPv6 option in the nic > > > > > > > >> > properties, disabled it, and enabled it again. However, the problem > > > > > > > >> > still > > > > > > > >> > exists. Also, the webserver reports the same error. > > > > > > > >> > > > > > > > > >> > "Rick Rogers" wrote: > > > > > > > >> > > > > > > > > >> >> Hi, > > > > > > > >> >> > > > > > > > >> >> Some have reported that disabling IPv6 has resolved this issue. You'll > > > > > > > >> >> find > > > > > > > >> >> it in the properties of the 'nic in Device Manager. > > > > > > > >> >> > > > > > > > >> >> -- > > > > > > > >> >> Best of Luck, > > > > > > > >> >> > > > > > > > >> >> Rick Rogers, aka "Nutcase" - Microsoft MVP > > > > > > > >> >> [url]http://mvp.support.microsoft.com/[/url] > > > > > > > >> >> Windows help - [url]www.rickrogers.org[/url] > > > > > > > >> >> > > > > > > > >> >> "Floris" <Floris@discussions.microsoft.com> wrote in message > > > > > > > >> >> news:99B79762-0549-4E00-ACFF-12C2B9D496DC@microsoft.com... > > > > > > > >> >> >I just installed Windows Vista Business N. With my previous XP > > > > > > > >> >> >installation, > > > > > > > >> >> > I could easily connect to a https-webdav location using Add Network > > > > > > > >> >> > Location. > > > > > > > >> >> > Unfortunately, with Vista, I'm unable to pass the authentication. > > > > > > > >> >> > I'm -very- > > > > > > > >> >> > sure that I'm using the right credentials. However, the auth dialog > > > > > > > >> >> > keeps > > > > > > > >> >> > popping up. > > > > > > > >> >> > > > > > > > > >> >> > I managed to get some logging from the Linux server I'm logging into > > > > > > > >> >> > (samba.log): > > > > > > > >> >> > [2006/12/07 17:41:36, 2] auth/auth.c:check_ntlm_password(319) > > > > > > > >> >> > check_ntlm_password: Authentication for user [FLORIS] -> [FLORIS] > > > > > > > >> >> > FAILED > > > > > > > >> >> > with error NT_STATUS_WRONG_PASSWORD > > > > > > > >> >> > [2006/12/07 17:41:36, 3] smbd/error.c:error_packet(146) > > > > > > > >> >> > error packet at smbd/sesssetup.c(1093) cmd=115 (SMBsesssetupX) > > > > > > > >> >> > NT_STATUS_LOGON_FAILURE > > > > > > > >> >> > > > > > > > > >> >> > With the same credentials, I'm able to login using a Win2000 > > > > > > > >> >> > computer. > > > > > > > >> >> > > > > > > > > >> >> > Any thoughts on this? > > > > > > > >> >> > > > > > > > >> >> > > > > > > > >> > > > > > > > >> > > > > > > > > > > > > > >[/color][/color][/color] |
|
01-02-2007, 11:20 AM
| |||
| |||
| Re: WebDav Hi Jeff, if you run IE7 in protected mode, WebDAV redirector will treat the cookie as unsafe and it will NOT use that cookie for authentication. It will only send the cookie if you first mark the URL as trusted in IE7 and access the website, WebDAV redirector WILL send the cookie for auth. For cookies to work, WebDAV redir first tries the root directory (/). If we get 403 (HTTP_STATUS_FORBIDDEN) back, that essentially means the cookie auth did not work so we don't try further deep in the directory tree. This is also by design. If you want Forms Based Authentication (via cookie) to work, the server needs to accept the cookie at the root. If you install Office 2003, WebFolders WILL get installed however any attempt to add a network connection via explorer or "net use" will still go via WebDAV redirector. I hope that answers your questions. The right way to fix this problem is to have the server honor OPTIONS and PROPFIND requests at the root as well as accept the cookie (for Forms Based Auth). Thanks -Ather "JJK" wrote: [color=blue] > Ather, > Thank you for the clarification. I seem to encounter some dilemma here, > and I am not sure if it's intended or by design. > The scenario is, the user needs to logon to get a cookie to the server > first. Furthermore, the user only has permission to access directory such as > /users/foo/bar, but not the ones above. When the user tries to access that > WebDAV resource, two different things would happen: > > 1. If IE7 is running protected mode (or the URL is not in the trusted zone), > the WebDAV redirector did not send the cookie to the server. However, it > ignored the returned 403 responses and crawled all the way to the > /users/foo/bar directory (which again was rejected due to no cookie present > in the request). > 2. If IE7 is running non-protected mode (or the URL is listed in the trusted > security zone), the WebDAV redirector did send the cookie to the server. > However, it only tried the / and /users directories several times and gave up > upon 403 responses. > > Is this expected behavior for Vista WebDAV mini-redirector? Will the > installation of the Office product change the way how it behaves? > > Thanks again, > Jeff > > "Ather Haleem (MSFT)" wrote: >[color=green] > > Hi Jeff- yes it is a requirement to support Depth:0 PROPFIND. It is not quite > > "new" for Vista since the Webdav Redirector that shipped with Windows XP had > > the same requirement. However, the difference is that Vista doesn't have > > Webfolder (another client for WebDAV) shipped inbox with Vista anymore and > > the WebDAV redirector (the WebDAV client that lets you map drives to a WebDAV > > resource) is used instead. With this, comes the limitation of supporting > > PROPFIND at root. > > > > Thanks. > > -Ather > > > > "JJK" wrote: > >[color=darkred] > > > Ather, > > > Is the requirement for the root directory to support PROPFIND method > > > (with Depth: 0) new for Vista? It appears that the pre-Vista OS WebDAV > > > clients were able to communicate with WebDAV server that only allows OPTIONS > > > for the root directory. Please confirm. > > > > > > Thanks, > > > Jeff > > > > > > "Ather Haleem (MSFT)" wrote: > > > > > > > It is possible that the root of the website ([url]https://sub.server.ext[/url]) doesn't > > > > honor OPTIONS or PROPFIND request bur /folder does. If that is the case, this > > > > is expected and by design and the workaround is to have the root also honor > > > > OPTIONS and PROPFIND request. This is most likely the reason why this is > > > > failing. > > > > > > > > Thanks. > > > > -Ather > > > > > > > > > > > > "Floris" wrote: > > > > > > > > > Hi Ather, > > > > > > > > > > With IE, I'm now able to get the 'default' HTML page of the webfolder (after > > > > > I enter my credentials) by enabling 'Send LM & NTLM - use NTLMv2 session > > > > > security if negotiated' in the Administrative Tools section of the Control > > > > > Panel. Before that was enabled, this wasn´t possible. > > > > > > > > > > However, if I try to open the location as a webfolder (using a link on that > > > > > default HTML page or by using the Add Network Location wizard), I keep > > > > > getting the auth dialog. > > > > > > > > > > The net use command results in the following output: > > > > > --- > > > > > C:\Users\Floris>net use * [url]https://sub.server.ext/folder[/url] > > > > > Enter the user name for 'sub.server.ext': floris > > > > > Enter the password for sub.server.ext: > > > > > System error 67 has occurred. > > > > > The network name cannot be found. > > > > > --- > > > > > > > > > > Anyway, 'telnet sub.server.ext 443' does result in a connection. > > > > > > > > > > "Ather Haleem (MSFT)" wrote: > > > > > > > > > > > Hi Floris, > > > > > > Can you try and see if you are able to re-produce the same problem if you > > > > > > try to access this WebDAV resource via Internet Explorer? Also, can you check > > > > > > to see if "net use * <https-webdav-resources>" works via command prompt? > > > > > > > > > > > > thanks. > > > > > > > > > > > > -Ather > > > > > > lead software design engineer/test | windows core file systems | micorosft > > > > > > corporation > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > "Rick Rogers" wrote: > > > > > > > > > > > > > Unfortunately, I don't know enough about Linux' server to tell you what else > > > > > > > to try. You may want to check in a 'nix group to see if others have run into > > > > > > > this with Vista. It may be that one of Vista's default networking protocols > > > > > > > isn't in a compatible format. > > > > > > > > > > > > > > -- > > > > > > > Best of Luck, > > > > > > > > > > > > > > Rick Rogers, aka "Nutcase" - Microsoft MVP > > > > > > > [url]http://mvp.support.microsoft.com/[/url] > > > > > > > Windows help - [url]www.rickrogers.org[/url] > > > > > > > > > > > > > > "Floris" <Floris@discussions.microsoft.com> wrote in message > > > > > > > news:76260B24-B3CC-427A-8574-F863A61539CD@microsoft.com... > > > > > > > > Yes :) > > > > > > > > > > > > > > > > "Rick Rogers" wrote: > > > > > > > > > > > > > > > >> Hi, > > > > > > > >> > > > > > > > >> So to be clear, did you try logging on while IPv6 was disabled? > > > > > > > >> > > > > > > > >> -- > > > > > > > >> Best of Luck, > > > > > > > >> > > > > > > > >> Rick Rogers, aka "Nutcase" - Microsoft MVP > > > > > > > >> [url]http://mvp.support.microsoft.com/[/url] > > > > > > > >> Windows help - [url]www.rickrogers.org[/url] > > > > > > > >> > > > > > > > >> "Floris" <Floris@discussions.microsoft.com> wrote in message > > > > > > > >> news:ED8D12CE-8EDE-40DE-98EA-27EB641C668C@microsoft.com... > > > > > > > >> > Thanks for your quick reply! I disabled the IPv6 option in the nic > > > > > > > >> > properties, disabled it, and enabled it again. However, the problem > > > > > > > >> > still > > > > > > > >> > exists. Also, the webserver reports the same error. > > > > > > > >> > > > > > > > > >> > "Rick Rogers" wrote: > > > > > > > >> > > > > > > > > >> >> Hi, > > > > > > > >> >> > > > > > > > >> >> Some have reported that disabling IPv6 has resolved this issue. You'll > > > > > > > >> >> find > > > > > > > >> >> it in the properties of the 'nic in Device Manager. > > > > > > > >> >> > > > > > > > >> >> -- > > > > > > > >> >> Best of Luck, > > > > > > > >> >> > > > > > > > >> >> Rick Rogers, aka "Nutcase" - Microsoft MVP > > > > > > > >> >> [url]http://mvp.support.microsoft.com/[/url] > > > > > > > >> >> Windows help - [url]www.rickrogers.org[/url] > > > > > > > >> >> > > > > > > > >> >> "Floris" <Floris@discussions.microsoft.com> wrote in message > > > > > > > >> >> news:99B79762-0549-4E00-ACFF-12C2B9D496DC@microsoft.com... > > > > > > > >> >> >I just installed Windows Vista Business N. With my previous XP > > > > > > > >> >> >installation, > > > > > > > >> >> > I could easily connect to a https-webdav location using Add Network > > > > > > > >> >> > Location. > > > > > > > >> >> > Unfortunately, with Vista, I'm unable to pass the authentication. > > > > > > > >> >> > I'm -very- > > > > > > > >> >> > sure that I'm using the right credentials. However, the auth dialog > > > > > > > >> >> > keeps > > > > > > > >> >> > popping up. > > > > > > > >> >> > > > > > > > > >> >> > I managed to get some logging from the Linux server I'm logging into > > > > > > > >> >> > (samba.log): > > > > > > > >> >> > [2006/12/07 17:41:36, 2] auth/auth.c:check_ntlm_password(319) > > > > > > > >> >> > check_ntlm_password: Authentication for user [FLORIS] -> [FLORIS] > > > > > > > >> >> > FAILED > > > > > > > >> >> > with error NT_STATUS_WRONG_PASSWORD > > > > > > > >> >> > [2006/12/07 17:41:36, 3] smbd/error.c:error_packet(146) > > > > > > > >> >> > error packet at smbd/sesssetup.c(1093) cmd=115 (SMBsesssetupX) > > > > > > > >> >> > NT_STATUS_LOGON_FAILURE > > > > > > > >> >> > > > > > > > > >> >> > With the same credentials, I'm able to login using a Win2000 > > > > > > > >> >> > computer. > > > > > > > >> >> > > > > > > > > >> >> > Any thoughts on this? > > > > > > > >> >> > > > > > > > >> >> > > > > > > > >> > > > > > > > >> > > > > > > > > > > > > > >[/color][/color][/color] |
|
01-02-2007, 11:21 AM
| |||
| |||
| Re: WebDav Ather, The cookie restriction makes sense, and it obviously is a result of the new Vista security model. However, I am not sure about the crawling abort upon 403's as you described. My experience was, the mini-redirector indeeded tried the next level down (i.e. /users in my example) before giving up, even though it received a 403 on the top level. Also, if the PROPFIND on the root got a 207 (Multi Status) response, but the status code in the response WebDAV XML is a 403, does it also considered a 403 or it is considered a success? The reason that I am digging further here is because the behavior is different from pre-Vista, where the crawling were attempted with errors ignoed but a request with the desired URL was still sent. I am trying to understand if this is a webdav implementation change or a potential bug there. Thank you for your time and helpful information. Sincerely, Jeff "JJK" wrote: [color=blue] > Ather, > Thank you for the clarification. I seem to encounter some dilemma here, > and I am not sure if it's intended or by design. > The scenario is, the user needs to logon to get a cookie to the server > first. Furthermore, the user only has permission to access directory such as > /users/foo/bar, but not the ones above. When the user tries to access that > WebDAV resource, two different things would happen: > > 1. If IE7 is running protected mode (or the URL is not in the trusted zone), > the WebDAV redirector did not send the cookie to the server. However, it > ignored the returned 403 responses and crawled all the way to the > /users/foo/bar directory (which again was rejected due to no cookie present > in the request). > 2. If IE7 is running non-protected mode (or the URL is listed in the trusted > security zone), the WebDAV redirector did send the cookie to the server. > However, it only tried the / and /users directories several times and gave up > upon 403 responses. > > Is this expected behavior for Vista WebDAV mini-redirector? Will the > installation of the Office product change the way how it behaves? > > Thanks again, > Jeff > > "Ather Haleem (MSFT)" wrote: >[color=green] > > Hi Jeff- yes it is a requirement to support Depth:0 PROPFIND. It is not quite > > "new" for Vista since the Webdav Redirector that shipped with Windows XP had > > the same requirement. However, the difference is that Vista doesn't have > > Webfolder (another client for WebDAV) shipped inbox with Vista anymore and > > the WebDAV redirector (the WebDAV client that lets you map drives to a WebDAV > > resource) is used instead. With this, comes the limitation of supporting > > PROPFIND at root. > > > > Thanks. > > -Ather > > > > "JJK" wrote: > >[color=darkred] > > > Ather, > > > Is the requirement for the root directory to support PROPFIND method > > > (with Depth: 0) new for Vista? It appears that the pre-Vista OS WebDAV > > > clients were able to communicate with WebDAV server that only allows OPTIONS > > > for the root directory. Please confirm. > > > > > > Thanks, > > > Jeff > > > > > > "Ather Haleem (MSFT)" wrote: > > > > > > > It is possible that the root of the website ([url]https://sub.server.ext[/url]) doesn't > > > > honor OPTIONS or PROPFIND request bur /folder does. If that is the case, this > > > > is expected and by design and the workaround is to have the root also honor > > > > OPTIONS and PROPFIND request. This is most likely the reason why this is > > > > failing. > > > > > > > > Thanks. > > > > -Ather > > > > > > > > > > > > "Floris" wrote: > > > > > > > > > Hi Ather, > > > > > > > > > > With IE, I'm now able to get the 'default' HTML page of the webfolder (after > > > > > I enter my credentials) by enabling 'Send LM & NTLM - use NTLMv2 session > > > > > security if negotiated' in the Administrative Tools section of the Control > > > > > Panel. Before that was enabled, this wasn´t possible. > > > > > > > > > > However, if I try to open the location as a webfolder (using a link on that > > > > > default HTML page or by using the Add Network Location wizard), I keep > > > > > getting the auth dialog. > > > > > > > > > > The net use command results in the following output: > > > > > --- > > > > > C:\Users\Floris>net use * [url]https://sub.server.ext/folder[/url] > > > > > Enter the user name for 'sub.server.ext': floris > > > > > Enter the password for sub.server.ext: > > > > > System error 67 has occurred. > > > > > The network name cannot be found. > > > > > --- > > > > > > > > > > Anyway, 'telnet sub.server.ext 443' does result in a connection. > > > > > > > > > > "Ather Haleem (MSFT)" wrote: > > > > > > > > > > > Hi Floris, > > > > > > Can you try and see if you are able to re-produce the same problem if you > > > > > > try to access this WebDAV resource via Internet Explorer? Also, can you check > > > > > > to see if "net use * <https-webdav-resources>" works via command prompt? > > > > > > > > > > > > thanks. > > > > > > > > > > > > -Ather > > > > > > lead software design engineer/test | windows core file systems | micorosft > > > > > > corporation > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > "Rick Rogers" wrote: > > > > > > > > > > > > > Unfortunately, I don't know enough about Linux' server to tell you what else > > > > > > > to try. You may want to check in a 'nix group to see if others have run into > > > > > > > this with Vista. It may be that one of Vista's default networking protocols > > > > > > > isn't in a compatible format. > > > > > > > > > > > > > > -- > > > > > > > Best of Luck, > > > > > > > > > > > > > > Rick Rogers, aka "Nutcase" - Microsoft MVP > > > > > > > [url]http://mvp.support.microsoft.com/[/url] > > > > > > > Windows help - [url]www.rickrogers.org[/url] > > > > > > > > > > > > > > "Floris" <Floris@discussions.microsoft.com> wrote in message > > > > > > > news:76260B24-B3CC-427A-8574-F863A61539CD@microsoft.com... > > > > > > > > Yes :) > > > > > > > > > > > > > > > > "Rick Rogers" wrote: > > > > > > > > > > > > > > > >> Hi, > > > > > > > >> > > > > > > > >> So to be clear, did you try logging on while IPv6 was disabled? > > > > > > > >> > > > > > > > >> -- > > > > > > > >> Best of Luck, > > > > > > > >> > > > > > > > >> Rick Rogers, aka "Nutcase" - Microsoft MVP > > > > > > > >> [url]http://mvp.support.microsoft.com/[/url] > > > > > > > >> Windows help - [url]www.rickrogers.org[/url] > > > > > > > >> > > > > > > > >> "Floris" <Floris@discussions.microsoft.com> wrote in message > > > > > > > >> news:ED8D12CE-8EDE-40DE-98EA-27EB641C668C@microsoft.com... > > > > > > > >> > Thanks for your quick reply! I disabled the IPv6 option in the nic > > > > > > > >> > properties, disabled it, and enabled it again. However, the problem > > > > > > > >> > still > > > > > > > >> > exists. Also, the webserver reports the same error. > > > > > > > >> > > > > > > > > >> > "Rick Rogers" wrote: > > > > > > > >> > > > > > > > > >> >> Hi, > > > > > > > >> >> > > > > > > > >> >> Some have reported that disabling IPv6 has resolved this issue. You'll > > > > > > > >> >> find > > > > > > > >> >> it in the properties of the 'nic in Device Manager. > > > > > > > >> >> > > > > > > > >> >> -- > > > > > > > >> >> Best of Luck, > > > > > > > >> >> > > > > > > > >> >> Rick Rogers, aka "Nutcase" - Microsoft MVP > > > > > > > >> >> [url]http://mvp.support.microsoft.com/[/url] > > > > > > > >> >> Windows help - [url]www.rickrogers.org[/url] > > > > > > > >> >> > > > > > > > >> >> "Floris" <Floris@discussions.microsoft.com> wrote in message > > > > > > > >> >> news:99B79762-0549-4E00-ACFF-12C2B9D496DC@microsoft.com... > > > > > > > >> >> >I just installed Windows Vista Business N. With my previous XP > > > > > > > >> >> >installation, > > > > > > > >> >> > I could easily connect to a https-webdav location using Add Network > > > > > > > >> >> > Location. > > > > > > > >> >> > Unfortunately, with Vista, I'm unable to pass the authentication. > > > > > > > >> >> > I'm -very- > > > > > > > >> >> > sure that I'm using the right credentials. However, the auth dialog > > > > > > > >> >> > keeps > > > > > > > >> >> > popping up. > > > > > > > >> >> > > > > > > > > >> >> > I managed to get some logging from the Linux server I'm logging into > > > > > > > >> >> > (samba.log): > > > > > > > >> >> > [2006/12/07 17:41:36, 2] auth/auth.c:check_ntlm_password(319) > > > > > > > >> >> > check_ntlm_password: Authentication for user [FLORIS] -> [FLORIS] > > > > > > > >> >> > FAILED > > > > > > > >> >> > with error NT_STATUS_WRONG_PASSWORD > > > > > > > >> >> > [2006/12/07 17:41:36, 3] smbd/error.c:error_packet(146) > > > > > > > >> >> > error packet at smbd/sesssetup.c(1093) cmd=115 (SMBsesssetupX) > > > > > > > >> >> > NT_STATUS_LOGON_FAILURE > > > > > > > >> >> > > > > > > > > >> >> > With the same credentials, I'm able to login using a Win2000 > > > > > > > >> >> > computer. > > > > > > > >> >> > > > > > > > > >> >> > Any thoughts on this? > > > > > > > >> >> > > > > > > > >> >> > > > > > > > >> > > > > > > > >> > > > > > > > > > > > > > >[/color][/color][/color] |
|
01-02-2007, 11:21 AM
| |||
| |||
| Re: WebDav Ather, The cookie restriction makes sense, and it obviously is a result of the new Vista security model. However, I am not sure about the crawling abort upon 403's as you described. My experience was, the mini-redirector indeeded tried the next level down (i.e. /users in my example) before giving up, even though it received a 403 on the top level. Also, if the PROPFIND on the root got a 207 (Multi Status) response, but the status code in the response WebDAV XML is a 403, does it also considered a 403 or it is considered a success? The reason that I am digging further here is because the behavior is different from pre-Vista, where the crawling were attempted with errors ignoed but a request with the desired URL was still sent. I am trying to understand if this is a webdav implementation change or a potential bug there. Thank you for your time and helpful information. Sincerely, Jeff "JJK" wrote: [color=blue] > Ather, > Thank you for the clarification. I seem to encounter some dilemma here, > and I am not sure if it's intended or by design. > The scenario is, the user needs to logon to get a cookie to the server > first. Furthermore, the user only has permission to access directory such as > /users/foo/bar, but not the ones above. When the user tries to access that > WebDAV resource, two different things would happen: > > 1. If IE7 is running protected mode (or the URL is not in the trusted zone), > the WebDAV redirector did not send the cookie to the server. However, it > ignored the returned 403 responses and crawled all the way to the > /users/foo/bar directory (which again was rejected due to no cookie present > in the request). > 2. If IE7 is running non-protected mode (or the URL is listed in the trusted > security zone), the WebDAV redirector did send the cookie to the server. > However, it only tried the / and /users directories several times and gave up > upon 403 responses. > > Is this expected behavior for Vista WebDAV mini-redirector? Will the > installation of the Office product change the way how it behaves? > > Thanks again, > Jeff > > "Ather Haleem (MSFT)" wrote: >[color=green] > > Hi Jeff- yes it is a requirement to support Depth:0 PROPFIND. It is not quite > > "new" for Vista since the Webdav Redirector that shipped with Windows XP had > > the same requirement. However, the difference is that Vista doesn't have > > Webfolder (another client for WebDAV) shipped inbox with Vista anymore and > > the WebDAV redirector (the WebDAV client that lets you map drives to a WebDAV > > resource) is used instead. With this, comes the limitation of supporting > > PROPFIND at root. > > > > Thanks. > > -Ather > > > > "JJK" wrote: > >[color=darkred] > > > Ather, > > > Is the requirement for the root directory to support PROPFIND method > > > (with Depth: 0) new for Vista? It appears that the pre-Vista OS WebDAV > > > clients were able to communicate with WebDAV server that only allows OPTIONS > > > for the root directory. Please confirm. > > > > > > Thanks, > > > Jeff > > > > > > "Ather Haleem (MSFT)" wrote: > > > > > > > It is possible that the root of the website ([url]https://sub.server.ext[/url]) doesn't > > > > honor OPTIONS or PROPFIND request bur /folder does. If that is the case, this > > > > is expected and by design and the workaround is to have the root also honor > > > > OPTIONS and PROPFIND request. This is most likely the reason why this is > > > > failing. > > > > > > > > Thanks. > > > > -Ather > > > > > > > > > > > > "Floris" wrote: > > > > > > > > > Hi Ather, > > > > > > > > > > With IE, I'm now able to get the 'default' HTML page of the webfolder (after > > > > > I enter my credentials) by enabling 'Send LM & NTLM - use NTLMv2 session > > > > > security if negotiated' in the Administrative Tools section of the Control > > > > > Panel. Before that was enabled, this wasn´t possible. > > > > > > > > > > However, if I try to open the location as a webfolder (using a link on that > > > > > default HTML page or by using the Add Network Location wizard), I keep > > > > > getting the auth dialog. > > > > > > > > > > The net use command results in the following output: > > > > > --- > > > > > C:\Users\Floris>net use * [url]https://sub.server.ext/folder[/url] > > > > > Enter the user name for 'sub.server.ext': floris > > > > > Enter the password for sub.server.ext: > > > > > System error 67 has occurred. > > > > > The network name cannot be found. > > > > > --- > > > > > > > > > > Anyway, 'telnet sub.server.ext 443' does result in a connection. > > > > > > > > > > "Ather Haleem (MSFT)" wrote: > > > > > > > > > > > Hi Floris, > > > > > > Can you try and see if you are able to re-produce the same problem if you > > > > > > try to access this WebDAV resource via Internet Explorer? Also, can you check > > > > > > to see if "net use * <https-webdav-resources>" works via command prompt? > > > > > > > > > > > > thanks. > > > > > > > > > > > > -Ather > > > > > > lead software design engineer/test | windows core file systems | micorosft > > > > > > corporation > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > "Rick Rogers" wrote: > > > > > > > > > > > > > Unfortunately, I don't know enough about Linux' server to tell you what else > > > > > > > to try. You may want to check in a 'nix group to see if others have run into > > > > > > > this with Vista. It may be that one of Vista's default networking protocols > > > > > > > isn't in a compatible format. > > > > > > > > > > > > > > -- > > > > > > > Best of Luck, > > > > > > > > > > > > > > Rick Rogers, aka "Nutcase" - Microsoft MVP > > > > > > > [url]http://mvp.support.microsoft.com/[/url] > > > > > > > Windows help - [url]www.rickrogers.org[/url] > > > > > > > > > > > > > > "Floris" <Floris@discussions.microsoft.com> wrote in message > > > > > > > news:76260B24-B3CC-427A-8574-F863A61539CD@microsoft.com... > > > > > > > > Yes :) > > > > > > > > > > > > > > > > "Rick Rogers" wrote: > > > > > > > > > > > > > > > >> Hi, > > > > > > > >> > > > > > > > >> So to be clear, did you try logging on while IPv6 was disabled? > > > > > > > >> > > > > > > > >> -- > > > > > > > >> Best of Luck, > > > > > > > >> > > > > > > > >> Rick Rogers, aka "Nutcase" - Microsoft MVP > > > > > > > >> [url]http://mvp.support.microsoft.com/[/url] > > > > > > > >> Windows help - [url]www.rickrogers.org[/url] > > > > > > > >> > > > > > > > >> "Floris" <Floris@discussions.microsoft.com> wrote in message > > > > > > > >> news:ED8D12CE-8EDE-40DE-98EA-27EB641C668C@microsoft.com... > > > > > > > >> > Thanks for your quick reply! I disabled the IPv6 option in the nic > > > > > > > >> > properties, disabled it, and enabled it again. However, the problem > > > > > > > >> > still > > > > > > > >> > exists. Also, the webserver reports the same error. > > > > > > > >> > > > > > > > > >> > "Rick Rogers" wrote: > > > > > > > >> > > > > > > > > >> >> Hi, > > > > > > > >> >> > > > > > > > >> >> Some have reported that disabling IPv6 has resolved this issue. You'll > > > > > > > >> >> find > > > > > > > >> >> it in the properties of the 'nic in Device Manager. > > > > > > > >> >> > > > > > > > >> >> -- > > > > > > > >> >> Best of Luck, > > > > > > > >> >> > > > > > > > >> >> Rick Rogers, aka "Nutcase" - Microsoft MVP > > > > > > > >> >> [url]http://mvp.support.microsoft.com/[/url] > > > > > > > >> >> Windows help - [url]www.rickrogers.org[/url] > > > > > > > >> >> > > > > > > > >> >> "Floris" <Floris@discussions.microsoft.com> wrote in message > > > > > > > >> >> news:99B79762-0549-4E00-ACFF-12C2B9D496DC@microsoft.com... > > > > > > > >> >> >I just installed Windows Vista Business N. With my previous XP > > > > > > > >> >> >installation, > > > > > > > >> >> > I could easily connect to a https-webdav location using Add Network > > > > > > > >> >> > Location. > > > > > > > >> >> > Unfortunately, with Vista, I'm unable to pass the authentication. > > > > > > > >> >> > I'm -very- > > > > > > > >> >> > sure that I'm using the right credentials. However, the auth dialog > > > > > > > >> >> > keeps > > > > > > > >> >> > popping up. > > > > > > > >> >> > > > > > > > > >> >> > I managed to get some logging from the Linux server I'm logging into > > > > > > > >> >> > (samba.log): > > > > > > > >> >> > [2006/12/07 17:41:36, 2] auth/auth.c:check_ntlm_password(319) > > > > > > > >> >> > check_ntlm_password: Authentication for user [FLORIS] -> [FLORIS] > > > > > > > >> >> > FAILED > > > > > > > >> >> > with error NT_STATUS_WRONG_PASSWORD > > > > > > > >> >> > [2006/12/07 17:41:36, 3] smbd/error.c:error_packet(146) > > > > > > > >> >> > error packet at smbd/sesssetup.c(1093) cmd=115 (SMBsesssetupX) > > > > > > > >> >> > NT_STATUS_LOGON_FAILURE > > > > > > > >> >> > > > > > > > > >> >> > With the same credentials, I'm able to login using a Win2000 > > > > > > > >> >> > computer. > > > > > > > >> >> > > > > > > > > >> >> > Any thoughts on this? > > > > > > > >> >> > > > > > > > >> >> > > > > > > > >> > > > > > > > >> > > > > > > > > > > > > > >[/color][/color][/color] |
|
01-02-2007, 11:25 AM
| |||
| |||
| Re: WebDav a 403 response back DOES result in an abort and we do not try the next level down. it's possible that in your case, the response to OPTIONS on root was multi-status and thus WebDAV redirector tried the next level (/users). Multi-status response will be treated as "possible" success (i.e. redirector assumes that something below may actually speak WebDAV since the root returned multi-status). The WebDAV redirector implementation has been like this eversince Windows XP. The difference (as I may have mentioned before) is that Windows XP had webfolders which didn't have any such restriction. WebFolders has been removed from Vista and WebDAV redirector is the answer to all WebDAV related traffic. We do understand that not being able to navigate to a WebDAV site where OPTIONS doesn't get honored on root is an issue and we are looking to address this in the next release. I apologize if this causing you any trouble. Let me know if I can be of any further help or if you need more clarification regarding anything here. thanks -Ather "JJK" wrote: [color=blue] > Ather, > The cookie restriction makes sense, and it obviously is a result of the > new Vista security model. However, I am not sure about the crawling abort > upon 403's as you described. My experience was, the mini-redirector indeeded > tried the next level down (i.e. /users in my example) before giving up, even > though it received a 403 on the top level. Also, if the PROPFIND on the root > got a 207 (Multi Status) response, but the status code in the response WebDAV > XML is a 403, does it also considered a 403 or it is considered a success? > The reason that I am digging further here is because the behavior is > different from pre-Vista, where the crawling were attempted with errors > ignoed but a request with the desired URL was still sent. I am trying to > understand if this is a webdav implementation change or a potential bug > there. Thank you for your time and helpful information. > > Sincerely, > Jeff > > "JJK" wrote: >[color=green] > > Ather, > > Thank you for the clarification. I seem to encounter some dilemma here, > > and I am not sure if it's intended or by design. > > The scenario is, the user needs to logon to get a cookie to the server > > first. Furthermore, the user only has permission to access directory such as > > /users/foo/bar, but not the ones above. When the user tries to access that > > WebDAV resource, two different things would happen: > > > > 1. If IE7 is running protected mode (or the URL is not in the trusted zone), > > the WebDAV redirector did not send the cookie to the server. However, it > > ignored the returned 403 responses and crawled all the way to the > > /users/foo/bar directory (which again was rejected due to no cookie present > > in the request). > > 2. If IE7 is running non-protected mode (or the URL is listed in the trusted > > security zone), the WebDAV redirector did send the cookie to the server. > > However, it only tried the / and /users directories several times and gave up > > upon 403 responses. > > > > Is this expected behavior for Vista WebDAV mini-redirector? Will the > > installation of the Office product change the way how it behaves? > > > > Thanks again, > > Jeff > > > > "Ather Haleem (MSFT)" wrote: > >[color=darkred] > > > Hi Jeff- yes it is a requirement to support Depth:0 PROPFIND. It is not quite > > > "new" for Vista since the Webdav Redirector that shipped with Windows XP had > > > the same requirement. However, the difference is that Vista doesn't have > > > Webfolder (another client for WebDAV) shipped inbox with Vista anymore and > > > the WebDAV redirector (the WebDAV client that lets you map drives to a WebDAV > > > resource) is used instead. With this, comes the limitation of supporting > > > PROPFIND at root. > > > > > > Thanks. > > > -Ather > > > > > > "JJK" wrote: > > > > > > > Ather, > > > > Is the requirement for the root directory to support PROPFIND method > > > > (with Depth: 0) new for Vista? It appears that the pre-Vista OS WebDAV > > > > clients were able to communicate with WebDAV server that only allows OPTIONS > > > > for the root directory. Please confirm. > > > > > > > > Thanks, > > > > Jeff > > > > > > > > "Ather Haleem (MSFT)" wrote: > > > > > > > > > It is possible that the root of the website ([url]https://sub.server.ext[/url]) doesn't > > > > > honor OPTIONS or PROPFIND request bur /folder does. If that is the case, this > > > > > is expected and by design and the workaround is to have the root also honor > > > > > OPTIONS and PROPFIND request. This is most likely the reason why this is > > > > > failing. > > > > > > > > > > Thanks. > > > > > -Ather > > > > > > > > > > > > > > > "Floris" wrote: > > > > > > > > > > > Hi Ather, > > > > > > > > > > > > With IE, I'm now able to get the 'default' HTML page of the webfolder (after > > > > > > I enter my credentials) by enabling 'Send LM & NTLM - use NTLMv2 session > > > > > > security if negotiated' in the Administrative Tools section of the Control > > > > > > Panel. Before that was enabled, this wasn´t possible. > > > > > > > > > > > > However, if I try to open the location as a webfolder (using a link on that > > > > > > default HTML page or by using the Add Network Location wizard), I keep > > > > > > getting the auth dialog. > > > > > > > > > > > > The net use command results in the following output: > > > > > > --- > > > > > > C:\Users\Floris>net use * [url]https://sub.server.ext/folder[/url] > > > > > > Enter the user name for 'sub.server.ext': floris > > > > > > Enter the password for sub.server.ext: > > > > > > System error 67 has occurred. > > > > > > The network name cannot be found. > > > > > > --- > > > > > > > > > > > > Anyway, 'telnet sub.server.ext 443' does result in a connection. > > > > > > > > > > > > "Ather Haleem (MSFT)" wrote: > > > > > > > > > > > > > Hi Floris, > > > > > > > Can you try and see if you are able to re-produce the same problem if you > > > > > > > try to access this WebDAV resource via Internet Explorer? Also, can you check > > > > > > > to see if "net use * <https-webdav-resources>" works via command prompt? > > > > > > > > > > > > > > thanks. > > > > > > > > > > > > > > -Ather > > > > > > > lead software design engineer/test | windows core file systems | micorosft > > > > > > > corporation > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > "Rick Rogers" wrote: > > > > > > > > > > > > > > > Unfortunately, I don't know enough about Linux' server to tell you what else > > > > > > > > to try. You may want to check in a 'nix group to see if others have run into > > > > > > > > this with Vista. It may be that one of Vista's default networking protocols > > > > > > > > isn't in a compatible format. > > > > > > > > > > > > > > > > -- > > > > > > > > Best of Luck, > > > > > > > > > > > > > > > > Rick Rogers, aka "Nutcase" - Microsoft MVP > > > > > > > > [url]http://mvp.support.microsoft.com/[/url] > > > > > > > > Windows help - [url]www.rickrogers.org[/url] > > > > > > > > > > > > > > > > "Floris" <Floris@discussions.microsoft.com> wrote in message > > > > > > > > news:76260B24-B3CC-427A-8574-F863A61539CD@microsoft.com... > > > > > > > > > Yes :) > > > > > > > > > > > > > > > > > > "Rick Rogers" wrote: > > > > > > > > > > > > > > > > > >> Hi, > > > > > > > > >> > > > > > > > > >> So to be clear, did you try logging on while IPv6 was disabled? > > > > > > > > >> > > > > > > > > >> -- > > > > > > > > >> Best of Luck, > > > > > > > > >> > > > > > > > > >> Rick Rogers, aka "Nutcase" - Microsoft MVP > > > > > > > > >> [url]http://mvp.support.microsoft.com/[/url] > > > > > > > > >> Windows help - [url]www.rickrogers.org[/url] > > > > > > > > >> > > > > > > > > >> "Floris" <Floris@discussions.microsoft.com> wrote in message > > > > > > > > >> news:ED8D12CE-8EDE-40DE-98EA-27EB641C668C@microsoft.com... > > > > > > > > >> > Thanks for your quick reply! I disabled the IPv6 option in the nic > > > > > > > > >> > properties, disabled it, and enabled it again. However, the problem > > > > > > > > >> > still > > > > > > > > >> > exists. Also, the webserver reports the same error. > > > > > > > > >> > > > > > > > > > >> > "Rick Rogers" wrote: > > > > > > > > >> > > > > > > > > > >> >> Hi, > > > > > > > > >> >> > > > > > > > > >> >> Some have reported that disabling IPv6 has resolved this issue. You'll > > > > > > > > >> >> find > > > > > > > > >> >> it in the properties of the 'nic in Device Manager. > > > > > > > > >> >> > > > > > > > > >> >> -- > > > > > > > > >> >> Best of Luck, > > > > > > > > >> >> > > > > > > > > >> >> Rick Rogers, aka "Nutcase" - Microsoft MVP > > > > > > > > >> >> [url]http://mvp.support.microsoft.com/[/url] > > > > > > > > >> >> Windows help - [url]www.rickrogers.org[/url] > > > > > > > > >> >> > > > > > > > > >> >> "Floris" <Floris@discussions.microsoft.com> wrote in message > > > > > > > > >> >> news:99B79762-0549-4E00-ACFF-12C2B9D496DC@microsoft.com... > > > > > > > > >> >> >I just installed Windows Vista Business N. With my previous XP > > > > > > > > >> >> >installation, > > > > > > > > >> >> > I could easily connect to a https-webdav location using Add Network > > > > > > > > >> >> > Location. > > > > > > > > >> >> > Unfortunately, with Vista, I'm unable to pass the authentication. > > > > > > > > >> >> > I'm -very- > > > > > > > > >> >> > sure that I'm using the right credentials. However, the auth dialog > > > > > > > > >> >> > keeps > > > > > > > > >> >> > popping up. > > > > > > > > >> >> > > > > > > > > > >> >> > I managed to get some logging from the Linux server I'm logging into > > > > > > > > >> >> > (samba.log): > > > > > > > > >> >> > [2006/12/07 17:41:36, 2] auth/auth.c:check_ntlm_password(319) > > > > > > > > >> >> > check_ntlm_password: Authentication for user [FLORIS] -> [FLORIS] > > > > > > > > >> >> > FAILED > > > > > > > > >> >> > with error NT_STATUS_WRONG_PASSWORD > > > > > > > > >> >> > [2006/12/07 17:41:36, 3] smbd/error.c:error_packet(146) > > > > > > > > >> >> > error packet at smbd/sesssetup.c(1093) cmd=115 (SMBsesssetupX) > > > > > > > > >> >> > NT_STATUS_LOGON_FAILURE > > > > > > > > >> >> > > > > > > > > > >> >> > With the same credentials, I'm able to login using a Win2000 > > > > > > > > >> >> > computer. > > > > > > > > >> >> > > > > > > > > > >> >> > Any thoughts on this? > > > > > > > > >> >> > > > > > > > > >> >> > > > > > > > > >> > > > > > > > > >> > > > > > > > > > > > > > > > >[/color][/color][/color] |
|
01-02-2007, 11:25 AM
| |||
| |||
| Re: WebDav a 403 response back DOES result in an abort and we do not try the next level down. it's possible that in your case, the response to OPTIONS on root was multi-status and thus WebDAV redirector tried the next level (/users). Multi-status response will be treated as "possible" success (i.e. redirector assumes that something below may actually speak WebDAV since the root returned multi-status). The WebDAV redirector implementation has been like this eversince Windows XP. The difference (as I may have mentioned before) is that Windows XP had webfolders which didn't have any such restriction. WebFolders has been removed from Vista and WebDAV redirector is the answer to all WebDAV related traffic. We do understand that not being able to navigate to a WebDAV site where OPTIONS doesn't get honored on root is an issue and we are looking to address this in the next release. I apologize if this causing you any trouble. Let me know if I can be of any further help or if you need more clarification regarding anything here. thanks -Ather "JJK" wrote: [color=blue] > Ather, > The cookie restriction makes sense, and it obviously is a result of the > new Vista security model. However, I am not sure about the crawling abort > upon 403's as you described. My experience was, the mini-redirector indeeded > tried the next level down (i.e. /users in my example) before giving up, even > though it received a 403 on the top level. Also, if the PROPFIND on the root > got a 207 (Multi Status) response, but the status code in the response WebDAV > XML is a 403, does it also considered a 403 or it is considered a success? > The reason that I am digging further here is because the behavior is > different from pre-Vista, where the crawling were attempted with errors > ignoed but a request with the desired URL was still sent. I am trying to > understand if this is a webdav implementation change or a potential bug > there. Thank you for your time and helpful information. > > Sincerely, > Jeff > > "JJK" wrote: >[color=green] > > Ather, > > Thank you for the clarification. I seem to encounter some dilemma here, > > and I am not sure if it's intended or by design. > > The scenario is, the user needs to logon to get a cookie to the server > > first. Furthermore, the user only has permission to access directory such as > > /users/foo/bar, but not the ones above. When the user tries to access that > > WebDAV resource, two different things would happen: > > > > 1. If IE7 is running protected mode (or the URL is not in the trusted zone), > > the WebDAV redirector did not send the cookie to the server. However, it > > ignored the returned 403 responses and crawled all the way to the > > /users/foo/bar directory (which again was rejected due to no cookie present > > in the request). > > 2. If IE7 is running non-protected mode (or the URL is listed in the trusted > > security zone), the WebDAV redirector did send the cookie to the server. > > However, it only tried the / and /users directories several times and gave up > > upon 403 responses. > > > > Is this expected behavior for Vista WebDAV mini-redirector? Will the > > installation of the Office product change the way how it behaves? > > > > Thanks again, > > Jeff > > > > "Ather Haleem (MSFT)" wrote: > >[color=darkred] > > > Hi Jeff- yes it is a requirement to support Depth:0 PROPFIND. It is not quite > > > "new" for Vista since the Webdav Redirector that shipped with Windows XP had > > > the same requirement. However, the difference is that Vista doesn't have > > > Webfolder (another client for WebDAV) shipped inbox with Vista anymore and > > > the WebDAV redirector (the WebDAV client that lets you map drives to a WebDAV > > > resource) is used instead. With this, comes the limitation of supporting > > > PROPFIND at root. > > > > > > Thanks. > > > -Ather > > > > > > "JJK" wrote: > > > > > > > Ather, > > > > Is the requirement for the root directory to support PROPFIND method > > > > (with Depth: 0) new for Vista? It appears that the pre-Vista OS WebDAV > > > > clients were able to communicate with WebDAV server that only allows OPTIONS > > > > for the root directory. Please confirm. > > > > > > > > Thanks, > > > > Jeff > > > > > > > > "Ather Haleem (MSFT)" wrote: > > > > > > > > > It is possible that the root of the website ([url]https://sub.server.ext[/url]) doesn't > > > > > honor OPTIONS or PROPFIND request bur /folder does. If that is the case, this > > > > > is expected and by design and the workaround is to have the root also honor > > > > > OPTIONS and PROPFIND request. This is most likely the reason why this is > > > > > failing. > > > > > > > > > > Thanks. > > > > > -Ather > > > > > > > > > > > > > > > "Floris" wrote: > > > > > > > > > > > Hi Ather, > > > > > > > > > > > > With IE, I'm now able to get the 'default' HTML page of the webfolder (after > > > > > > I enter my credentials) by enabling 'Send LM & NTLM - use NTLMv2 session > > > > > > security if negotiated' in the Administrative Tools section of the Control > > > > > > Panel. Before that was enabled, this wasn´t possible. > > > > > > > > > > > > However, if I try to open the location as a webfolder (using a link on that > > > > > > default HTML page or by using the Add Network Location wizard), I keep > > > > > > getting the auth dialog. > > > > > > > > > > > > The net use command results in the following output: > > > > > > --- > > > > > > C:\Users\Floris>net use * [url]https://sub.server.ext/folder[/url] > > > > > > Enter the user name for 'sub.server.ext': floris > > > > > > Enter the password for sub.server.ext: > > > > > > System error 67 has occurred. > > > > > > The network name cannot be found. > > > > > > --- > > > > > > > > > > > > Anyway, 'telnet sub.server.ext 443' does result in a connection. > > > > > > > > > > > > "Ather Haleem (MSFT)" wrote: > > > > > > > > > > > > > Hi Floris, > > > > > > > Can you try and see if you are able to re-produce the same problem if you > > > > > > > try to access this WebDAV resource via Internet Explorer? Also, can you check > > > > > > > to see if "net use * <https-webdav-resources>" works via command prompt? > > > > > > > > > > > > > > thanks. > > > > > > > > > > > > > > -Ather > > > > > > > lead software design engineer/test | windows core file systems | micorosft > > > > > > > corporation > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > "Rick Rogers" wrote: > > > > > > > > > > > > > > > Unfortunately, I don't know enough about Linux' server to tell you what else > > > > > > > > to try. You may want to check in a 'nix group to see if others have run into > > > > > > > > this with Vista. It may be that one of Vista's default networking protocols > > > > > > > > isn't in a compatible format. > > > > > > > > > > > > > > > > -- > > > > > > > > Best of Luck, > > > > > > > > > > > > > > > > Rick Rogers, aka "Nutcase" - Microsoft MVP > > > > > > > > [url]http://mvp.support.microsoft.com/[/url] > > > > > > > > Windows help - [url]www.rickrogers.org[/url] > > > > > > > > > > > > > > > > "Floris" <Floris@discussions.microsoft.com> wrote in message > > > > > > > > news:76260B24-B3CC-427A-8574-F863A61539CD@microsoft.com... > > > > > > > > > Yes :) > > > > > > > > > > > > > > > > > > "Rick Rogers" wrote: > > > > > > > > > > > > > > > > > >> Hi, > > > > > > > > >> > > > > > > > > >> So to be clear, did you try logging on while IPv6 was disabled? > > > > > > > > >> > > > > > > > > >> -- > > > > > > > > >> Best of Luck, > > > > > > > > >> > > > > > > > > >> Rick Rogers, aka "Nutcase" - Microsoft MVP > > > > > > > > >> [url]http://mvp.support.microsoft.com/[/url] > > > > > > > > >> Windows help - [url]www.rickrogers.org[/url] > > > > > > > > >> > > > > > > > > >> "Floris" <Floris@discussions.microsoft.com> wrote in message > > > > > > > > >> news:ED8D12CE-8EDE-40DE-98EA-27EB641C668C@microsoft.com... > > > > > > > > >> > Thanks for your quick reply! I disabled the IPv6 option in the nic > > > > > > > > >> > properties, disabled it, and enabled it again. However, the problem > > > > > > > > >> > still > > > > > > > > >> > exists. Also, the webserver reports the same error. > > > > > > > > >> > > > > > > > > > >> > "Rick Rogers" wrote: > > > > > > > > >> > > > > > > > > > >> >> Hi, > > > > > > > > >> >> > > > > > > > > >> >> Some have reported that disabling IPv6 has resolved this issue. You'll > > > > > > > > >> >> find > > > > > > > > >> >> it in the properties of the 'nic in Device Manager. > > > > > > > > >> >> > > > > > > > > >> >> -- > > > > > > > > >> >> Best of Luck, > > > > > > > > >> >> > > > > > > > > >> >> Rick Rogers, aka "Nutcase" - Microsoft MVP > > > > > > > > >> >> [url]http://mvp.support.microsoft.com/[/url] > > > > > > > > >> >> Windows help - [url]www.rickrogers.org[/url] > > > > > > > > >> >> > > > > > > > > >> >> "Floris" <Floris@discussions.microsoft.com> wrote in message > > > > > > > > >> >> news:99B79762-0549-4E00-ACFF-12C2B9D496DC@microsoft.com... > > > > > > > > >> >> >I just installed Windows Vista Business N. With my previous XP > > > > > > > > >> >> >installation, > > > > > > > > >> >> > I could easily connect to a https-webdav location using Add Network > > > > > > > > >> >> > Location. > > > > > > > > >> >> > Unfortunately, with Vista, I'm unable to pass the authentication. > > > > > > > > >> >> > I'm -very- > > > > > > > > >> >> > sure that I'm using the right credentials. However, the auth dialog > > > > > > > > >> >> > keeps > > > > > > > > >> >> > popping up. > > > > > > > > >> >> > > > > > > > > > >> >> > I managed to get some logging from the Linux server I'm logging into > > > > > > > > >> >> > (samba.log): > > > > > > > > >> >> > [2006/12/07 17:41:36, 2] auth/auth.c:check_ntlm_password(319) > > > > > > > > >> >> > check_ntlm_password: Authentication for user [FLORIS] -> [FLORIS] > > > > > > > > >> >> > FAILED > > > > > > > > >> >> > with error NT_STATUS_WRONG_PASSWORD > > > > > > > > >> >> > [2006/12/07 17:41:36, 3] smbd/error.c:error_packet(146) > > > > > > > > >> >> > error packet at smbd/sesssetup.c(1093) cmd=115 (SMBsesssetupX) > > > > > > > > >> >> > NT_STATUS_LOGON_FAILURE > > > > > > > > >> >> > > > > > > > > > >> >> > With the same credentials, I'm able to login using a Win2000 > > > > > > > > >> >> > computer. > > > > > > > > >> >> > > > > > > > > > >> >> > Any thoughts on this? > > > > > > > > >> >> > > > > > > > > >> >> > > > > > > > > >> > > > > > > > > >> > > > > > > > > > > > > > > > >[/color][/color][/color] |
|
01-02-2007, 11:26 AM
| |||
| |||
| Re: WebDav Ather, The OPTIONS command on the root resulted in a 200 OK. Just for the sake of it, I made sure the server returned 207 but has status code 403 in the WebDAV response XML. Now the fun part is, the Vista mini-redirector crawled to the right directory, and got a 207 with status code 200 inside, but it still complained that it couldn't open the URL as a web folder (tried with or without Office 2007 installed). I also tried your suggestion of using "net use * https://10.1.2.3/users/foo/bar" from the command line, but I got a system error 67. Based on the description of that error code, it's regarding domain controller. Does this mean the Vista mini-redirector can only talk to a server that is part of the same domain, or it does reverse DNS lookup on the server IP and give up if that failed? I am wondering, is there any way to debug or enable some logging to give me more information what needs to be done? I really appreciate your spending time answering questions here. It's absolutely helpful for whoever is interested in running webdav on Vista. Best Regards, Jeff "Ather Haleem (MSFT)" wrote: [color=blue] > a 403 response back DOES result in an abort and we do not try the next level > down. it's possible that in your case, the response to OPTIONS on root was > multi-status and thus WebDAV redirector tried the next level (/users). > Multi-status response will be treated as "possible" success (i.e. redirector > assumes that something below may actually speak WebDAV since the root > returned multi-status). > > The WebDAV redirector implementation has been like this eversince Windows > XP. The difference (as I may have mentioned before) is that Windows XP had > webfolders which didn't have any such restriction. WebFolders has been > removed from Vista and WebDAV redirector is the answer to all WebDAV related > traffic. > > We do understand that not being able to navigate to a WebDAV site where > OPTIONS doesn't get honored on root is an issue and we are looking to address > this in the next release. I apologize if this causing you any trouble. > > Let me know if I can be of any further help or if you need more > clarification regarding anything here. > > thanks > -Ather > > "JJK" wrote: >[color=green] > > Ather, > > The cookie restriction makes sense, and it obviously is a result of the > > new Vista security model. However, I am not sure about the crawling abort > > upon 403's as you described. My experience was, the mini-redirector indeeded > > tried the next level down (i.e. /users in my example) before giving up, even > > though it received a 403 on the top level. Also, if the PROPFIND on the root > > got a 207 (Multi Status) response, but the status code in the response WebDAV > > XML is a 403, does it also considered a 403 or it is considered a success? > > The reason that I am digging further here is because the behavior is > > different from pre-Vista, where the crawling were attempted with errors > > ignoed but a request with the desired URL was still sent. I am trying to > > understand if this is a webdav implementation change or a potential bug > > there. Thank you for your time and helpful information. > > > > Sincerely, > > Jeff > > > > "JJK" wrote: > >[color=darkred] > > > Ather, > > > Thank you for the clarification. I seem to encounter some dilemma here, > > > and I am not sure if it's intended or by design. > > > The scenario is, the user needs to logon to get a cookie to the server > > > first. Furthermore, the user only has permission to access directory such as > > > /users/foo/bar, but not the ones above. When the user tries to access that > > > WebDAV resource, two different things would happen: > > > > > > 1. If IE7 is running protected mode (or the URL is not in the trusted zone), > > > the WebDAV redirector did not send the cookie to the server. However, it > > > ignored the returned 403 responses and crawled all the way to the > > > /users/foo/bar directory (which again was rejected due to no cookie present > > > in the request). > > > 2. If IE7 is running non-protected mode (or the URL is listed in the trusted > > > security zone), the WebDAV redirector did send the cookie to the server. > > > However, it only tried the / and /users directories several times and gave up > > > upon 403 responses. > > > > > > Is this expected behavior for Vista WebDAV mini-redirector? Will the > > > installation of the Office product change the way how it behaves? > > > > > > Thanks again, > > > Jeff > > > > > > "Ather Haleem (MSFT)" wrote: > > > > > > > Hi Jeff- yes it is a requirement to support Depth:0 PROPFIND. It is not quite > > > > "new" for Vista since the Webdav Redirector that shipped with Windows XP had > > > > the same requirement. However, the difference is that Vista doesn't have > > > > Webfolder (another client for WebDAV) shipped inbox with Vista anymore and > > > > the WebDAV redirector (the WebDAV client that lets you map drives to a WebDAV > > > > resource) is used instead. With this, comes the limitation of supporting > > > > PROPFIND at root. > > > > > > > > Thanks. > > > > -Ather > > > > > > > > "JJK" wrote: > > > > > > > > > Ather, > > > > > Is the requirement for the root directory to support PROPFIND method > > > > > (with Depth: 0) new for Vista? It appears that the pre-Vista OS WebDAV > > > > > clients were able to communicate with WebDAV server that only allows OPTIONS > > > > > for the root directory. Please confirm. > > > > > > > > > > Thanks, > > > > > Jeff > > > > > > > > > > "Ather Haleem (MSFT)" wrote: > > > > > > > > > > > It is possible that the root of the website ([url]https://sub.server.ext[/url]) doesn't > > > > > > honor OPTIONS or PROPFIND request bur /folder does. If that is the case, this > > > > > > is expected and by design and the workaround is to have the root also honor > > > > > > OPTIONS and PROPFIND request. This is most likely the reason why this is > > > > > > failing. > > > > > > > > > > > > Thanks. > > > > > > -Ather > > > > > > > > > > > > > > > > > > "Floris" wrote: > > > > > > > > > > > > > Hi Ather, > > > > > > > > > > > > > > With IE, I'm now able to get the 'default' HTML page of the webfolder (after > > > > > > > I enter my credentials) by enabling 'Send LM & NTLM - use NTLMv2 session > > > > > > > security if negotiated' in the Administrative Tools section of the Control > > > > > > > Panel. Before that was enabled, this wasn´t possible. > > > > > > > > > > > > > > However, if I try to open the location as a webfolder (using a link on that > > > > > > > default HTML page or by using the Add Network Location wizard), I keep > > > > > > > getting the auth dialog. > > > > > > > > > > > > > > The net use command results in the following output: > > > > > > > --- > > > > > > > C:\Users\Floris>net use * [url]https://sub.server.ext/folder[/url] > > > > > > > Enter the user name for 'sub.server.ext': floris > > > > > > > Enter the password for sub.server.ext: > > > > > > > System error 67 has occurred. > > > > > > > The network name cannot be found. > > > > > > > --- > > > > > > > > > > > > > > Anyway, 'telnet sub.server.ext 443' does result in a connection. > > > > > > > > > > > > > > "Ather Haleem (MSFT)" wrote: > > > > > > > > > > > > > > > Hi Floris, > > > > > > > > Can you try and see if you are able to re-produce the same problem if you > > > > > > > > try to access this WebDAV resource via Internet Explorer? Also, can you check > > > > > > > > to see if "net use * <https-webdav-resources>" works via command prompt? > > > > > > > > > > > > > > > > thanks. > > > > > > > > > > > > > > > > -Ather > > > > > > > > lead software design engineer/test | windows core file systems | micorosft > > > > > > > > corporation > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > "Rick Rogers" wrote: > > > > > > > > > > > > > > > > > Unfortunately, I don't know enough about Linux' server to tell you what else > > > > > > > > > to try. You may want to check in a 'nix group to see if others have run into > > > > > > > > > this with Vista. It may be that one of Vista's default networking protocols > > > > > > > > > isn't in a compatible format. > > > > > > > > > > > > > > > > > > -- > > > > > > > > > Best of Luck, > > > > > > > > > > > > > > > > > > Rick Rogers, aka "Nutcase" - Microsoft MVP > > > > > > > > > [url]http://mvp.support.microsoft.com/[/url] > > > > > > > > > Windows help - [url]www.rickrogers.org[/url] > > > > > > > > > > > > > > > > > > "Floris" <Floris@discussions.microsoft.com> wrote in message > > > > > > > > > news:76260B24-B3CC-427A-8574-F863A61539CD@microsoft.com... > > > > > > > > > > Yes :) > > > > > > > > > > > > > > > > > > > > "Rick Rogers" wrote: > > > > > > > > > > > > > > > > > > > >> Hi, > > > > > > > > > >> > > > > > > > > > >> So to be clear, did you try logging on while IPv6 was disabled? > > > > > > > > > >> > > > > > > > > > >> -- > > > > > > > > > >> Best of Luck, > > > > > > > > > >> > > > > > > > > > >> Rick Rogers, aka "Nutcase" - Microsoft MVP > > > > > > > > > >> [url]http://mvp.support.microsoft.com/[/url] > > > > > > > > > >> Windows help - [url]www.rickrogers.org[/url] > > > > > > > > > >> > > > > > > > > > >> "Floris" <Floris@discussions.microsoft.com> wrote in message > > > > > > > > > >> news:ED8D12CE-8EDE-40DE-98EA-27EB641C668C@microsoft.com... > > > > > > > > > >> > Thanks for your quick reply! I disabled the IPv6 option in the nic > > > > > > > > > >> > properties, disabled it, and enabled it again. However, the problem > > > > > > > > > >> > still > > > > > > > > > >> > exists. Also, the webserver reports the same error. > > > > > > > > > >> > > > > > > > > > > >> > "Rick Rogers" wrote: > > > > > > > > > >> > > > > > > > > > > >> >> Hi, > > > > > > > > > >> >> > > > > > > > > > >> >> Some have reported that disabling IPv6 has resolved this issue. You'll > > > > > > > > > >> >> find > > > > > > > > > >> >> it in the properties of the 'nic in Device Manager. > > > > > > > > > >> >> > > > > > > > > > >> >> -- > > > > > > > > > >> >> Best of Luck, > > > > > > > > > >> >> > > > > > > > > > >> >> Rick Rogers, aka "Nutcase" - Microsoft MVP > > > > > > > > > >> >> [url]http://mvp.support.microsoft.com/[/url] > > > > > > > > > >> >> Windows help - [url]www.rickrogers.org[/url] > > > > > > > > > >> >> > > > > > > > > > >> >> "Floris" <Floris@discussions.microsoft.com> wrote in message > > > > > > > > > >> >> news:99B79762-0549-4E00-ACFF-12C2B9D496DC@microsoft.com... > > > > > > > > > >> >> >I just installed Windows Vista Business N. With my previous XP > > > > > > > > > >> >> >installation, > > > > > > > > > >> >> > I could easily connect to a https-webdav location using Add Network > > > > > > > > > >> >> > Location. > > > > > > > > > >> >> > Unfortunately, with Vista, I'm unable to pass the authentication. > > > > > > > > > >> >> > I'm -very- > > > > > > > > > >> >> > sure that I'm using the right credentials. However, the auth dialog > > > > > > > > > >> >> > keeps > > > > > > > > > >> >> > popping up. > > > > > > > > > >> >> > > > > > > > > > > >> >> > I managed to get some logging from the Linux server I'm logging into > > > > > > > > > >> >> > (samba.log): > > > > > > > > > >> >> > [2006/12/07 17:41:36, 2] auth/auth.c:check_ntlm_password(319) > > > > > > > > > >> >> > check_ntlm_password: Authentication for user [FLORIS] -> [FLORIS] > > > > > > > > > >> >> > FAILED > > > > > > > > > >> >> > with error NT_STATUS_WRONG_PASSWORD > > > > > > > > > >> >> > [2006/12/07 17:41:36, 3] smbd/error.c:error_packet(146) > > > > > > > > > >> >> > error packet at smbd/sesssetup.c(1093) cmd=115 (SMBsesssetupX) > > > > > > > > > >> >> > NT_STATUS_LOGON_FAILURE > > > > > > > > > >> >> > > > > > > > > > > >> >> > With the same credentials, I'm able to login using a Win2000 > > > > > > > > > >> >> > computer. > > > > > > > > > >> >> > > > > > > > > > > >> >> > Any thoughts on this? > > > > > > > > > >> >> > > > > > > > > > >> >> > > > > > > > > > >> > > > > > > > > > >> > > > > > > > > > > > > > > > > > >[/color][/color][/color] |
|
01-02-2007, 11:26 AM
| |||
| |||
| Re: WebDav Ather, The OPTIONS command on the root resulted in a 200 OK. Just for the sake of it, I made sure the server returned 207 but has status code 403 in the WebDAV response XML. Now the fun part is, the Vista mini-redirector crawled to the right directory, and got a 207 with status code 200 inside, but it still complained that it couldn't open the URL as a web folder (tried with or without Office 2007 installed). I also tried your suggestion of using "net use * https://10.1.2.3/users/foo/bar" from the command line, but I got a system error 67. Based on the description of that error code, it's regarding domain controller. Does this mean the Vista mini-redirector can only talk to a server that is part of the same domain, or it does reverse DNS lookup on the server IP and give up if that failed? I am wondering, is there any way to debug or enable some logging to give me more information what needs to be done? I really appreciate your spending time answering questions here. It's absolutely helpful for whoever is interested in running webdav on Vista. Best Regards, Jeff "Ather Haleem (MSFT)" wrote: [color=blue] > a 403 response back DOES result in an abort and we do not try the next level > down. it's possible that in your case, the response to OPTIONS on root was > multi-status and thus WebDAV redirector tried the next level (/users). > Multi-status response will be treated as "possible" success (i.e. redirector > assumes that something below may actually speak WebDAV since the root > returned multi-status). > > The WebDAV redirector implementation has been like this eversince Windows > XP. The difference (as I may have mentioned before) is that Windows XP had > webfolders which didn't have any such restriction. WebFolders has been > removed from Vista and WebDAV redirector is the answer to all WebDAV related > traffic. > > We do understand that not being able to navigate to a WebDAV site where > OPTIONS doesn't get honored on root is an issue and we are looking to address > this in the next release. I apologize if this causing you any trouble. > > Let me know if I can be of any further help or if you need more > clarification regarding anything here. > > thanks > -Ather > > "JJK" wrote: >[color=green] > > Ather, > > The cookie restriction makes sense, and it obviously is a result of the > > new Vista security model. However, I am not sure about the crawling abort > > upon 403's as you described. My experience was, the mini-redirector indeeded > > tried the next level down (i.e. /users in my example) before giving up, even > > though it received a 403 on the top level. Also, if the PROPFIND on the root > > got a 207 (Multi Status) response, but the status code in the response WebDAV > > XML is a 403, does it also considered a 403 or it is considered a success? > > The reason that I am digging further here is because the behavior is > > different from pre-Vista, where the crawling were attempted with errors > > ignoed but a request with the desired URL was still sent. I am trying to > > understand if this is a webdav implementation change or a potential bug > > there. Thank you for your time and helpful information. > > > > Sincerely, > > Jeff > > > > "JJK" wrote: > >[color=darkred] > > > Ather, > > > Thank you for the clarification. I seem to encounter some dilemma here, > > > and I am not sure if it's intended or by design. > > > The scenario is, the user needs to logon to get a cookie to the server > > > first. Furthermore, the user only has permission to access directory such as > > > /users/foo/bar, but not the ones above. When the user tries to access that > > > WebDAV resource, two different things would happen: > > > > > > 1. If IE7 is running protected mode (or the URL is not in the trusted zone), > > > the WebDAV redirector did not send the cookie to the server. However, it > > > ignored the returned 403 responses and crawled all the way to the > > > /users/foo/bar directory (which again was rejected due to no cookie present > > > in the request). > > > 2. If IE7 is running non-protected mode (or the URL is listed in the trusted > > > security zone), the WebDAV redirector did send the cookie to the server. > > > However, it only tried the / and /users directories several times and gave up > > > upon 403 responses. > > > > > > Is this expected behavior for Vista WebDAV mini-redirector? Will the > > > installation of the Office product change the way how it behaves? > > > > > > Thanks again, > > > Jeff > > > > > > "Ather Haleem (MSFT)" wrote: > > > > > > > Hi Jeff- yes it is a requirement to support Depth:0 PROPFIND. It is not quite > > > > "new" for Vista since the Webdav Redirector that shipped with Windows XP had > > > > the same requirement. However, the difference is that Vista doesn't have > > > > Webfolder (another client for WebDAV) shipped inbox with Vista anymore and > > > > the WebDAV redirector (the WebDAV client that lets you map drives to a WebDAV > > > > resource) is used instead. With this, comes the limitation of supporting > > > > PROPFIND at root. > > > > > > > > Thanks. > > > > -Ather > > > > > > > > "JJK" wrote: > > > > > > > > > Ather, > > > > > Is the requirement for the root directory to support PROPFIND method > > > > > (with Depth: 0) new for Vista? It appears that the pre-Vista OS WebDAV > > > > > clients were able to communicate with WebDAV server that only allows OPTIONS > > > > > for the root directory. Please confirm. > > > > > > > > > > Thanks, > > > > > Jeff > > > > > > > > > > "Ather Haleem (MSFT)" wrote: > > > > > > > > > > > It is possible that the root of the website ([url]https://sub.server.ext[/url]) doesn't > > > > > > honor OPTIONS or PROPFIND request bur /folder does. If that is the case, this > > > > > > is expected and by design and the workaround is to have the root also honor > > > > > > OPTIONS and PROPFIND request. This is most likely the reason why this is > > > > > > failing. > > > > > > > > > > > > Thanks. > > > > > > -Ather > > > > > > > > > > > > > > > > > > "Floris" wrote: > > > > > > > > > > > > > Hi Ather, > > > > > > > > > > > > > > With IE, I'm now able to get the 'default' HTML page of the webfolder (after > > > > > > > I enter my credentials) by enabling 'Send LM & NTLM - use NTLMv2 session > > > > > > > security if negotiated' in the Administrative Tools section of the Control > > > > > > > Panel. Before that was enabled, this wasn´t possible. > > > > > > > > > > > > > > However, if I try to open the location as a webfolder (using a link on that > > > > > > > default HTML page or by using the Add Network Location wizard), I keep > > > > > > > getting the auth dialog. > > > > > > > > > > > > > > The net use command results in the following output: > > > > > > > --- > > > > > > > C:\Users\Floris>net use * [url]https://sub.server.ext/folder[/url] > > > > > > > Enter the user name for 'sub.server.ext': floris > > > > > > > Enter the password for sub.server.ext: > > > > > > > System error 67 has occurred. > > > > > > > The network name cannot be found. > > > > > > > --- > > > > > > > > > > > > > > Anyway, 'telnet sub.server.ext 443' does result in a connection. > > > > > > > > > > > > > > "Ather Haleem (MSFT)" wrote: > > > > > > > > > > > > > > > Hi Floris, > > > > > > > > Can you try and see if you are able to re-produce the same problem if you > > > > > > > > try to access this WebDAV resource via Internet Explorer? Also, can you check > > > > > > > > to see if "net use * <https-webdav-resources>" works via command prompt? > > > > > > > > > > > > > > > > thanks. > > > > > > > > > > > > > > > > -Ather > > > > > > > > lead software design engineer/test | windows core file systems | micorosft > > > > > > > > corporation > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > "Rick Rogers" wrote: > > > > > > > > > > > > > > > > > Unfortunately, I don't know enough about Linux' server to tell you what else > > > > > > > > > to try. You may want to check in a 'nix group to see if others have run into > > > > > > > > > this with Vista. It may be that one of Vista's default networking protocols > > > > > > > > > isn't in a compatible format. > > > > > > > > > > > > > > > > > > -- > > > > > > > > > Best of Luck, > > > > > > > > > > > > > > > > > > Rick Rogers, aka "Nutcase" - Microsoft MVP > > > > > > > > > [url]http://mvp.support.microsoft.com/[/url] > > > > > > > > > Windows help - [url]www.rickrogers.org[/url] > > > > > > > > > > > > > > > > > > "Floris" <Floris@discussions.microsoft.com> wrote in message > > > > > > > > > news:76260B24-B3CC-427A-8574-F863A61539CD@microsoft.com... > > > > > > > > > > Yes :) > > > > > > > > > > > > > > > > > > > > "Rick Rogers" wrote: > > > > > > > > > > > > > > > > > > > >> Hi, > > > > > > > > > >> > > > > > > > > > >> So to be clear, did you try logging on while IPv6 was disabled? > > > > > > > > > >> > > > > > > > > > >> -- > > > > > > > > > >> Best of Luck, > > > > > > > > > >> > > > > > > > > > >> Rick Rogers, aka "Nutcase" - Microsoft MVP > > > > > > > > > >> [url]http://mvp.support.microsoft.com/[/url] > > > > > > > > > >> Windows help - [url]www.rickrogers.org[/url] > > > > > > > > > >> > > > > > > > > > >> "Floris" <Floris@discussions.microsoft.com> wrote in message > > > > > > > > > >> news:ED8D12CE-8EDE-40DE-98EA-27EB641C668C@microsoft.com... > > > > > > > > > >> > Thanks for your quick reply! I disabled the IPv6 option in the nic > > > > > > > > > >> > properties, disabled it, and enabled it again. However, the problem > > > > > > > > > >> > still > > > > > > > > > >> > exists. Also, the webserver reports the same error. > > > > > > > > > >> > > > > > > > > > > >> > "Rick Rogers" wrote: > > > > > > > > > >> > > > > > > > > > > >> >> Hi, > > > > > > > > > >> >> > > > > > > > > > >> >> Some have reported that disabling IPv6 has resolved this issue. You'll > > > > > > > > > >> >> find > > > > > > > > > >> >> it in the properties of the 'nic in Device Manager. > > > > > > > > > >> >> > > > > > > > > > >> >> -- > > > > > > > > > >> >> Best of Luck, > > > > > > > > > >> >> > > > > > > > > > >> >> Rick Rogers, aka "Nutcase" - Microsoft MVP > > > > > > > > > >> >> [url]http://mvp.support.microsoft.com/[/url] > > > > > > > > > >> >> Windows help - [url]www.rickrogers.org[/url] > > > > > > > > > >> >> > > > > > > > > > >> >> "Floris" <Floris@discussions.microsoft.com> wrote in message > > > > > > > > > >> >> news:99B79762-0549-4E00-ACFF-12C2B9D496DC@microsoft.com... > > > > > > > > > >> >> >I just installed Windows Vista Business N. With my previous XP > > > > > > > > > >> >> >installation, > > > > > > > > > >> >> > I could easily connect to a https-webdav location using Add Network > > > > > > > > > >> >> > Location. > > > > > > > > > >> >> > Unfortunately, with Vista, I'm unable to pass the authentication. > > > > > > > > > >> >> > I'm -very- > > > > > > > > > >> >> > sure that I'm using the right credentials. However, the auth dialog > > > > > > > > > >> >> > keeps > > > > > > > > > >> >> > popping up. > > > > > > > > > >> >> > > > > > > > > > > >> >> > I managed to get some logging from the Linux server I'm logging into > > > > > > > > > >> >> > (samba.log): > > > > > > > > > >> >> > [2006/12/07 17:41:36, 2] auth/auth.c:check_ntlm_password(319) > > > > > > > > > >> >> > check_ntlm_password: Authentication for user [FLORIS] -> [FLORIS] > > > > > > > > > >> >> > FAILED > > > > > > > > > >> >> > with error NT_STATUS_WRONG_PASSWORD > > > > > > > > > >> >> > [2006/12/07 17:41:36, 3] smbd/error.c:error_packet(146) > > > > > > > > > >> >> > error packet at smbd/sesssetup.c(1093) cmd=115 (SMBsesssetupX) > > > > > > > > > >> >> > NT_STATUS_LOGON_FAILURE > > > > > > > > > >> >> > > > > > > > > > > >> >> > With the same credentials, I'm able to login using a Win2000 > > > > > > > > > >> >> > computer. > > > > > > > > > >> >> > > > > > > > > > > >> >> > Any thoughts on this? > > > > > > > > > >> >> > > > > > > > > > >> >> > > > > > > > > > >> > > > > > > > > > >> > > > > > > > > > > > > > > > > > >[/color][/color][/color] |
|
01-02-2007, 11:30 AM
| |||
| |||
| Re: WebDav error 67 is not necessarily a dc error. it basically means that the dns lookup failed. are you able to access the site if you try it via IE7? On a related note, WebDAV redirector picks up the proxy settings from IE7 so you may need to check that as well. you might also want to try accessing the site directly via IP address or perhaps the FQDN (if it's on intranet) to see if that works? thanks -ather "JJK" wrote: [color=blue] > Ather, > The OPTIONS command on the root resulted in a 200 OK. Just for the sake > of it, I made sure the server returned 207 but has status code 403 in the > WebDAV response XML. Now the fun part is, the Vista mini-redirector crawled > to the right directory, and got a 207 with status code 200 inside, but it > still complained that it couldn't open the URL as a web folder (tried with or > without Office 2007 installed). > I also tried your suggestion of using "net use * > https://10.1.2.3/users/foo/bar" from the command line, but I got a system > error 67. Based on the description of that error code, it's regarding domain > controller. Does this mean the Vista mini-redirector can only talk to a > server that is part of the same domain, or it does reverse DNS lookup on the > server IP and give up if that failed? I am wondering, is there any way to > debug or enable some logging to give me more information what needs to be > done? > I really appreciate your spending time answering questions here. It's > absolutely helpful for whoever is interested in running webdav on Vista. > > Best Regards, > Jeff > > "Ather Haleem (MSFT)" wrote: >[color=green] > > a 403 response back DOES result in an abort and we do not try the next level > > down. it's possible that in your case, the response to OPTIONS on root was > > multi-status and thus WebDAV redirector tried the next level (/users). > > Multi-status response will be treated as "possible" success (i.e. redirector > > assumes that something below may actually speak WebDAV since the root > > returned multi-status). > > > > The WebDAV redirector implementation has been like this eversince Windows > > XP. The difference (as I may have mentioned before) is that Windows XP had > > webfolders which didn't have any such restriction. WebFolders has been > > removed from Vista and WebDAV redirector is the answer to all WebDAV related > > traffic. > > > > We do understand that not being able to navigate to a WebDAV site where > > OPTIONS doesn't get honored on root is an issue and we are looking to address > > this in the next release. I apologize if this causing you any trouble. > > > > Let me know if I can be of any further help or if you need more > > clarification regarding anything here. > > > > thanks > > -Ather > > > > "JJK" wrote: > >[color=darkred] > > > Ather, > > > The cookie restriction makes sense, and it obviously is a result of the > > > new Vista security model. However, I am not sure about the crawling abort > > > upon 403's as you described. My experience was, the mini-redirector indeeded > > > tried the next level down (i.e. /users in my example) before giving up, even > > > though it received a 403 on the top level. Also, if the PROPFIND on the root > > > got a 207 (Multi Status) response, but the status code in the response WebDAV > > > XML is a 403, does it also considered a 403 or it is considered a success? > > > The reason that I am digging further here is because the behavior is > > > different from pre-Vista, where the crawling were attempted with errors > > > ignoed but a request with the desired URL was still sent. I am trying to > > > understand if this is a webdav implementation change or a potential bug > > > there. Thank you for your time and helpful information. > > > > > > Sincerely, > > > Jeff > > > > > > "JJK" wrote: > > > > > > > Ather, > > > > Thank you for the clarification. I seem to encounter some dilemma here, > > > > and I am not sure if it's intended or by design. > > > > The scenario is, the user needs to logon to get a cookie to the server > > > > first. Furthermore, the user only has permission to access directory such as > > > > /users/foo/bar, but not the ones above. When the user tries to access that > > > > WebDAV resource, two different things would happen: > > > > > > > > 1. If IE7 is running protected mode (or the URL is not in the trusted zone), > > > > the WebDAV redirector did not send the cookie to the server. However, it > > > > ignored the returned 403 responses and crawled all the way to the > > > > /users/foo/bar directory (which again was rejected due to no cookie present > > > > in the request). > > > > 2. If IE7 is running non-protected mode (or the URL is listed in the trusted > > > > security zone), the WebDAV redirector did send the cookie to the server. > > > > However, it only tried the / and /users directories several times and gave up > > > > upon 403 responses. > > > > > > > > Is this expected behavior for Vista WebDAV mini-redirector? Will the > > > > installation of the Office product change the way how it behaves? > > > > > > > > Thanks again, > > > > Jeff > > > > > > > > "Ather Haleem (MSFT)" wrote: > > > > > > > > > Hi Jeff- yes it is a requirement to support Depth:0 PROPFIND. It is not quite > > > > > "new" for Vista since the Webdav Redirector that shipped with Windows XP had > > > > > the same requirement. However, the difference is that Vista doesn't have > > > > > Webfolder (another client for WebDAV) shipped inbox with Vista anymore and > > > > > the WebDAV redirector (the WebDAV client that lets you map drives to a WebDAV > > > > > resource) is used instead. With this, comes the limitation of supporting > > > > > PROPFIND at root. > > > > > > > > > > Thanks. > > > > > -Ather > > > > > > > > > > "JJK" wrote: > > > > > > > > > > > Ather, > > > > > > Is the requirement for the root directory to support PROPFIND method > > > > > > (with Depth: 0) new for Vista? It appears that the pre-Vista OS WebDAV > > > > > > clients were able to communicate with WebDAV server that only allows OPTIONS > > > > > > for the root directory. Please confirm. > > > > > > > > > > > > Thanks, > > > > > > Jeff > > > > > > > > > > > > "Ather Haleem (MSFT)" wrote: > > > > > > > > > > > > > It is possible that the root of the website ([url]https://sub.server.ext[/url]) doesn't > > > > > > > honor OPTIONS or PROPFIND request bur /folder does. If that is the case, this > > > > > > > is expected and by design and the workaround is to have the root also honor > > > > > > > OPTIONS and PROPFIND request. This is most likely the reason why this is > > > > > > > failing. > > > > > > > > > > > > > > Thanks. > > > > > > > -Ather > > > > > > > > > > > > > > > > > > > > > "Floris" wrote: > > > > > > > > > > > > > > > Hi Ather, > > > > > > > > > > > > > > > > With IE, I'm now able to get the 'default' HTML page of the webfolder (after > > > > > > > > I enter my credentials) by enabling 'Send LM & NTLM - use NTLMv2 session > > > > > > > > security if negotiated' in the Administrative Tools section of the Control > > > > > > > > Panel. Before that was enabled, this wasn´t possible. > > > > > > > > > > > > > > > > However, if I try to open the location as a webfolder (using a link on that > > > > > > > > default HTML page or by using the Add Network Location wizard), I keep > > > > > > > > getting the auth dialog. > > > > > > > > > > > > > > > > The net use command results in the following output: > > > > > > > > --- > > > > > > > > C:\Users\Floris>net use * [url]https://sub.server.ext/folder[/url] > > > > > > > > Enter the user name for 'sub.server.ext': floris > > > > > > > > Enter the password for sub.server.ext: > > > > > > > > System error 67 has occurred. > > > > > > > > The network name cannot be found. > > > > > > > > --- > > > > > > > > > > > > > > > > Anyway, 'telnet sub.server.ext 443' does result in a connection. > > > > > > > > > > > > > > > > "Ather Haleem (MSFT)" wrote: > > > > > > > > > > > > > > > > > Hi Floris, > > > > > > > > > Can you try and see if you are able to re-produce the same problem if you > > > > > > > > > try to access this WebDAV resource via Internet Explorer? Also, can you check > > > > > > > > > to see if "net use * <https-webdav-resources>" works via command prompt? > > > > > > > > > > > > > > > > > > thanks. > > > > > > > > > > > > > > > > > > -Ather > > > > > > > > > lead software design engineer/test | windows core file systems | micorosft > > > > > > > > > corporation > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > "Rick Rogers" wrote: > > > > > > > > > > > > > > > > > > > Unfortunately, I don't know enough about Linux' server to tell you what else > > > > > > > > > > to try. You may want to check in a 'nix group to see if others have run into > > > > > > > > > > this with Vista. It may be that one of Vista's default networking protocols > > > > > > > > > > isn't in a compatible format. > > > > > > > > > > > > > > > > > > > > -- > > > > > > > > > > Best of Luck, > > > > > > > > > > > > > > > > > > > > Rick Rogers, aka "Nutcase" - Microsoft MVP > > > > > > > > > > [url]http://mvp.support.microsoft.com/[/url] > > > > > > > > > > Windows help - [url]www.rickrogers.org[/url] > > > > > > > > > > > > > > > > > > > > "Floris" <Floris@discussions.microsoft.com> wrote in message > > > > > > > > > > news:76260B24-B3CC-427A-8574-F863A61539CD@microsoft.com... > > > > > > > > > > > Yes :) > > > > > > > > > > > > > > > > > > > > > > "Rick Rogers" wrote: > > > > > > > > > > > > > > > > > > > > > >> Hi, > > > > > > > > > > >> > > > > > > > > > > >> So to be clear, did you try logging on while IPv6 was disabled? > > > > > > > > > > >> > > > > > > > > > > >> -- > > > > > > > > > > >> Best of Luck, > > > > > > > > > > >> > > > > > > > > > > >> Rick Rogers, aka "Nutcase" - Microsoft MVP > > > > > > > > > > >> [url]http://mvp.support.microsoft.com/[/url] > > > > > > > > > > >> Windows help - [url]www.rickrogers.org[/url] > > > > > > > > > > >> > > > > > > > > > > >> "Floris" <Floris@discussions.microsoft.com> wrote in message > > > > > > > > > > >> news:ED8D12CE-8EDE-40DE-98EA-27EB641C668C@microsoft.com... > > > > > > > > > > >> > Thanks for your quick reply! I disabled the IPv6 option in the nic > > > > > > > > > > >> > properties, disabled it, and enabled it again. However, the problem > > > > > > > > > > >> > still > > > > > > > > > > >> > exists. Also, the webserver reports the same error. > > > > > > > > > > >> > > > > > > > > > > > >> > "Rick Rogers" wrote: > > > > > > > > > > >> > > > > > > > > > > > >> >> Hi, > > > > > > > > > > >> >> > > > > > > > > > > >> >> Some have reported that disabling IPv6 has resolved this issue. You'll > > > > > > > > > > >> >> find > > > > > > > > > > >> >> it in the properties of the 'nic in Device Manager. > > > > > > > > > > >> >> > > > > > > > > > > >> >> -- > > > > > > > > > > >> >> Best of Luck, > > > > > > > > > > >> >> > > > > > > > > > > >> >> Rick Rogers, aka "Nutcase" - Microsoft MVP > > > > > > > > > > >> >> [url]http://mvp.support.microsoft.com/[/url] > > > > > > > > > > >> >> Windows help - [url]www.rickrogers.org[/url] > > > > > > > > > > >> >> > > > > > > > > > > >> >> "Floris" <Floris@discussions.microsoft.com> wrote in message > > > > > > > > > > >> >> news:99B79762-0549-4E00-ACFF-12C2B9D496DC@microsoft.com... > > > > > > > > > > >> >> >I just installed Windows Vista Business N. With my previous XP > > > > > > > > > > >> >> >installation, > > > > > > > > > > >> >> > I could easily connect to a https-webdav location using Add Network > > > > > > > > > > >> >> > Location. > > > > > > > > > > >> >> > Unfortunately, with Vista, I'm unable to pass the authentication. > > > > > > > > > > >> >> > I'm -very- > > > > > > > > > > >> >> > sure that I'm using the right credentials. However, the auth dialog > > > > > > > > > > >> >> > keeps > > > > > > > > > > >> >> > popping up. > > > > > > > > > > >> >> > > > > > > > > > > > >> >> > I managed to get some logging from the Linux server I'm logging into > > > > > > > > > > >> >> > (samba.log): > > > > > > > > > > >> >> > [2006/12/07 17:41:36, 2] auth/auth.c:check_ntlm_password(319) > > > > > > > > > > >> >> > check_ntlm_password: Authentication for user [FLORIS] -> [FLORIS] > > > > > > > > > > >> >> > FAILED > > > > > > > > > > >> >> > with error NT_STATUS_WRONG_PASSWORD > > > > > > > > > > >> >> > [2006/12/07 17:41:36, 3] smbd/error.c:error_packet(146) > > > > > > > > > > >> >> > error packet at smbd/sesssetup.c(1093) cmd=115 (SMBsesssetupX) > > > > > > > > > > >> >> > NT_STATUS_LOGON_FAILURE > > > > > > > > > > >> >> > > > > > > > > > > > >> >> > With the same credentials, I'm able to login using a Win2000 > > > > > > > > > > >> >> > computer. > > > > > > > > > > >> >> > > > > > > > > > > > >> >> > Any thoughts on this? > > > > > > > > > > >> >> > > > > > > > > > > >> >> > > > > > > > > > > >> > > > > > > > > > > >> > > > > > > > > > > > > > > > > > > > >[/color][/color][/color] |
|
01-02-2007, 11:30 AM
| |||
| |||
| Re: WebDav Ather, I was using the IP address when I specified the full URL in the 'net use' command. There is no proxy used, and I had no problem accessing the URL from IE7. One thing that could be a problem is that, the server uses a self-signed certificate, and I didn't import the server cert into the trusted list. Does the mini-redirector picks up the certificate state from the process (IE7) to ignore the 'bad' certificate if the user already selected to trust it when IE7 first connected to the server? Other than that, I had no idea why Vista mini-redirector decided to claim that it couldn't open the URL as a web folder after it got a succesful 207 response back. Once again, thanks!! Jeff "Ather Haleem (MSFT)" wrote: [color=blue] > error 67 is not necessarily a dc error. it basically means that the dns > lookup failed. are you able to access the site if you try it via IE7? > > On a related note, WebDAV redirector picks up the proxy settings from IE7 so > you may need to check that as well. > > you might also want to try accessing the site directly via IP address or > perhaps the FQDN (if it's on intranet) to see if that works? > > thanks > -ather > > "JJK" wrote: >[color=green] > > Ather, > > The OPTIONS command on the root resulted in a 200 OK. Just for the sake > > of it, I made sure the server returned 207 but has status code 403 in the > > WebDAV response XML. Now the fun part is, the Vista mini-redirector crawled > > to the right directory, and got a 207 with status code 200 inside, but it > > still complained that it couldn't open the URL as a web folder (tried with or > > without Office 2007 installed). > > I also tried your suggestion of using "net use * > > https://10.1.2.3/users/foo/bar" from the command line, but I got a system > > error 67. Based on the description of that error code, it's regarding domain > > controller. Does this mean the Vista mini-redirector can only talk to a > > server that is part of the same domain, or it does reverse DNS lookup on the > > server IP and give up if that failed? I am wondering, is there any way to > > debug or enable some logging to give me more information what needs to be > > done? > > I really appreciate your spending time answering questions here. It's > > absolutely helpful for whoever is interested in running webdav on Vista. > > > > Best Regards, > > Jeff > > > > "Ather Haleem (MSFT)" wrote: > >[color=darkred] > > > a 403 response back DOES result in an abort and we do not try the next level > > > down. it's possible that in your case, the response to OPTIONS on root was > > > multi-status and thus WebDAV redirector tried the next level (/users). > > > Multi-status response will be treated as "possible" success (i.e. redirector > > > assumes that something below may actually speak WebDAV since the root > > > returned multi-status). > > > > > > The WebDAV redirector implementation has been like this eversince Windows > > > XP. The difference (as I may have mentioned before) is that Windows XP had > > > webfolders which didn't have any such restriction. WebFolders has been > > > removed from Vista and WebDAV redirector is the answer to all WebDAV related > > > traffic. > > > > > > We do understand that not being able to navigate to a WebDAV site where > > > OPTIONS doesn't get honored on root is an issue and we are looking to address > > > this in the next release. I apologize if this causing you any trouble. > > > > > > Let me know if I can be of any further help or if you need more > > > clarification regarding anything here. > > > > > > thanks > > > -Ather > > > > > > "JJK" wrote: > > > > > > > Ather, > > > > The cookie restriction makes sense, and it obviously is a result of the > > > > new Vista security model. However, I am not sure about the crawling abort > > > > upon 403's as you described. My experience was, the mini-redirector indeeded > > > > tried the next level down (i.e. /users in my example) before giving up, even > > > > though it received a 403 on the top level. Also, if the PROPFIND on the root > > > > got a 207 (Multi Status) response, but the status code in the response WebDAV > > > > XML is a 403, does it also considered a 403 or it is considered a success? > > > > The reason that I am digging further here is because the behavior is > > > > different from pre-Vista, where the crawling were attempted with errors > > > > ignoed but a request with the desired URL was still sent. I am trying to > > > > understand if this is a webdav implementation change or a potential bug > > > > there. Thank you for your time and helpful information. > > > > > > > > Sincerely, > > > > Jeff > > > > > > > > "JJK" wrote: > > > > > > > > > Ather, > > > > > Thank you for the clarification. I seem to encounter some dilemma here, > > > > > and I am not sure if it's intended or by design. > > > > > The scenario is, the user needs to logon to get a cookie to the server > > > > > first. Furthermore, the user only has permission to access directory such as > > > > > /users/foo/bar, but not the ones above. When the user tries to access that > > > > > WebDAV resource, two different things would happen: > > > > > > > > > > 1. If IE7 is running protected mode (or the URL is not in the trusted zone), > > > > > the WebDAV redirector did not send the cookie to the server. However, it > > > > > ignored the returned 403 responses and crawled all the way to the > > > > > /users/foo/bar directory (which again was rejected due to no cookie present > > > > > in the request). > > > > > 2. If IE7 is running non-protected mode (or the URL is listed in the trusted > > > > > security zone), the WebDAV redirector did send the cookie to the server. > > > > > However, it only tried the / and /users directories several times and gave up > > > > > upon 403 responses. > > > > > > > > > > Is this expected behavior for Vista WebDAV mini-redirector? Will the > > > > > installation of the Office product change the way how it behaves? > > > > > > > > > > Thanks again, > > > > > Jeff > > > > > > > > > > "Ather Haleem (MSFT)" wrote: > > > > > > > > > > > Hi Jeff- yes it is a requirement to support Depth:0 PROPFIND. It is not quite > > > > > > "new" for Vista since the Webdav Redirector that shipped with Windows XP had > > > > > > the same requirement. However, the difference is that Vista doesn't have > > > > > > Webfolder (another client for WebDAV) shipped inbox with Vista anymore and > > > > > > the WebDAV redirector (the WebDAV client that lets you map drives to a WebDAV > > > > > > resource) is used instead. With this, comes the limitation of supporting > > > > > > PROPFIND at root. > > > > > > > > > > > > Thanks. > > > > > > -Ather > > > > > > > > > > > > "JJK" wrote: > > > > > > > > > > > > > Ather, > > > > > > > Is the requirement for the root directory to support PROPFIND method > > > > > > > (with Depth: 0) new for Vista? It appears that the pre-Vista OS WebDAV > > > > > > > clients were able to communicate with WebDAV server that only allows OPTIONS > > > > > > > for the root directory. Please confirm. > > > > > > > > > > > > > > Thanks, > > > > > > > Jeff > > > > > > > > > > > > > > "Ather Haleem (MSFT)" wrote: > > > > > > > > > > > > > > > It is possible that the root of the website ([url]https://sub.server.ext[/url]) doesn't > > > > > > > > honor OPTIONS or PROPFIND request bur /folder does. If that is the case, this > > > > > > > > is expected and by design and the workaround is to have the root also honor > > > > > > > > OPTIONS and PROPFIND request. This is most likely the reason why this is > > > > > > > > failing. > > > > > > > > > > > > > > > > Thanks. > > > > > > > > -Ather > > > > > > > > > > > > > > > > > > > > > > > > "Floris" wrote: > > > > > > > > > > > > > > > > > Hi Ather, > > > > > > > > > > > > > > > > > > With IE, I'm now able to get the 'default' HTML page of the webfolder (after > > > > > > > > > I enter my credentials) by enabling 'Send LM & NTLM - use NTLMv2 session > > > > > > > > > security if negotiated' in the Administrative Tools section of the Control > > > > > > > > > Panel. Before that was enabled, this wasn´t possible. > > > > > > > > > > > > > > > > > > However, if I try to open the location as a webfolder (using a link on that > > > > > > > > > default HTML page or by using the Add Network Location wizard), I keep > > > > > > > > > getting the auth dialog. > > > > > > > > > > > > > > > > > > The net use command results in the following output: > > > > > > > > > --- > > > > > > > > > C:\Users\Floris>net use * [url]https://sub.server.ext/folder[/url] > > > > > > > > > Enter the user name for 'sub.server.ext': floris > > > > > > > > > Enter the password for sub.server.ext: > > > > > > > > > System error 67 has occurred. > > > > > > > > > The network name cannot be found. > > > > > > > > > --- > > > > > > > > > > > > > > > > > > Anyway, 'telnet sub.server.ext 443' does result in a connection. > > > > > > > > > > > > > > > > > > "Ather Haleem (MSFT)" wrote: > > > > > > > > > > > > > > > > > > > Hi Floris, > > > > > > > > > > Can you try and see if you are able to re-produce the same problem if you > > > > > > > > > > try to access this WebDAV resource via Internet Explorer? Also, can you check > > > > > > > > > > to see if "net use * <https-webdav-resources>" works via command prompt? > > > > > > > > > > > > > > > > > > > > thanks. > > > > > > > > > > > > > > > > > > > > -Ather > > > > > > > > > > lead software design engineer/test | windows core file systems | micorosft > > > > > > > > > > corporation > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > "Rick Rogers" wrote: > > > > > > > > > > > > > > > > > > > > > Unfortunately, I don't know enough about Linux' server to tell you what else > > > > > > > > > > > to try. You may want to check in a 'nix group to see if others have run into > > > > > > > > > > > this with Vista. It may be that one of Vista's default networking protocols > > > > > > > > > > > isn't in a compatible format. > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > > > > > Best of Luck, > > > > > > > > > > > > > > > > > > > > > > Rick Rogers, aka "Nutcase" - Microsoft MVP > > > > > > > > > > > [url]http://mvp.support.microsoft.com/[/url] > > > > > > > > > > > Windows help - [url]www.rickrogers.org[/url] > > > > > > > > > > > > > > > > > > > > > > "Floris" <Floris@discussions.microsoft.com> wrote in message > > > > > > > > > > > news:76260B24-B3CC-427A-8574-F863A61539CD@microsoft.com... > > > > > > > > > > > > Yes :) > > > > > > > > > > > > > > > > > > > > > > > > "Rick Rogers" wrote: > > > > > > > > > > > > > > > > > > > > > > > >> Hi, > > > > > > > > > > > >> > > > > > > > > > > > >> So to be clear, did you try logging on while IPv6 was disabled? > > > > > > > > > > > >> > > > > > > > > > > > >> -- > > > > > > > > > > > >> Best of Luck, > > > > > > > > > > > >> > > > > > > > > > > > >> Rick Rogers, aka "Nutcase" - Microsoft MVP > > > > > > > > > > > >> [url]http://mvp.support.microsoft.com/[/url] > > > > > > > > > > > >> Windows help - [url]www.rickrogers.org[/url] > > > > > > > > > > > >> > > > > > > > > > > > >> "Floris" <Floris@discussions.microsoft.com> wrote in message > > > > > > > > > > > >> news:ED8D12CE-8EDE-40DE-98EA-27EB641C668C@microsoft.com... > > > > > > > > > > > >> > Thanks for your quick reply! I disabled the IPv6 option in the nic > > > > > > > > > > > >> > properties, disabled it, and enabled it again. However, the problem > > > > > > > > > > > >> > still > > > > > > > > > > > >> > exists. Also, the webserver reports the same error. > > > > > > > > > > > >> > > > > > > > > > > > > >> > "Rick Rogers" wrote: > > > > > > > > > > > >> > > > > > > > > > > > > >> >> Hi, > > > > > > > > > > > >> >> > > > > > > > > > > > >> >> Some have reported that disabling IPv6 has resolved this issue. You'll > > > > > > > > > > > >> >> find > > > > > > > > > > > >> >> it in the properties of the 'nic in Device Manager. > > > > > > > > > > > >> >> > > > > > > > > > > > >> >> -- > > > > > > > > > > > >> >> Best of Luck, > > > > > > > > > > > >> >> > > > > > > > > > > > >> >> Rick Rogers, aka "Nutcase" - Microsoft MVP > > > > > > > > > > > >> >> [url]http://mvp.support.microsoft.com/[/url] > > > > > > > > > > > >> >> Windows help - [url]www.rickrogers.org[/url] > > > > > > > > > > > >> >> > > > > > > > > > > > >> >> "Floris" <Floris@discussions.microsoft.com> wrote in message > > > > > > > > > > > >> >> news:99B79762-0549-4E00-ACFF-12C2B9D496DC@microsoft.com... > > > > > > > > > > > >> >> >I just installed Windows Vista Business N. With my previous XP > > > > > > > > > > > >> >> >installation, > > > > > > > > > > > >> >> > I could easily connect to a https-webdav location using Add Network > > > > > > > > > > > >> >> > Location. > > > > > > > > > > > >> >> > Unfortunately, with Vista, I'm unable to pass the authentication. > > > > > > > > > > > >> >> > I'm -very- > > > > > > > > > > > >> >> > sure that I'm using the right credentials. However, the auth dialog > > > > > > > > > > > >> >> > keeps > > > > > > > > > > > >> >> > popping up. > > > > > > > > > > > >> >> > > > > > > > > > > > > >> >> > I managed to get some logging from the Linux server I'm logging into > > > > > > > > > > > >> >> > (samba.log): > > > > > > > > > > > >> >> > [2006/12/07 17:41:36, 2] auth/auth.c:check_ntlm_password(319) > > > > > > > > > > > >> >> > check_ntlm_password: Authentication for user [FLORIS] -> [FLORIS] > > > > > > > > > > > >> >> > FAILED > > > > > > > > > > > >> >> > with error NT_STATUS_WRONG_PASSWORD > > > > > > > > > > > >> >> > [2006/12/07 17:41:36, 3] smbd/error.c:error_packet(146) > > > > > > > > > > > >> >> > error packet at smbd/sesssetup.c(1093) cmd=115 (SMBsesssetupX) > > > > > > > > > > > >> >> > NT_STATUS_LOGON_FAILURE > > > > > > > > > > > >> >> > > > > > > > > > > > > >> >> > With the same credentials, I'm able to login using a Win2000 > > > > > > > > > > > >> >> > computer. > > > > > > > > > > > >> >> > > > > > > > > > > > > >> >> > Any thoughts on this? > > > > > > > > > > > >> >> > > > > > > > > > > > >> >> > > > > > > > > > > > >> > > > > > > > > > > > >> > > > > > > > > > > > > > > > > > > > > > >[/color][/color][/color] |
|
01-02-2007, 11:30 AM
| |||
| |||
| Re: WebDav Ather, I was using the IP address when I specified the full URL in the 'net use' command. There is no proxy used, and I had no problem accessing the URL from IE7. One thing that could be a problem is that, the server uses a self-signed certificate, and I didn't import the server cert into the trusted list. Does the mini-redirector picks up the certificate state from the process (IE7) to ignore the 'bad' certificate if the user already selected to trust it when IE7 first connected to the server? Other than that, I had no idea why Vista mini-redirector decided to claim that it couldn't open the URL as a web folder after it got a succesful 207 response back. Once again, thanks!! Jeff "Ather Haleem (MSFT)" wrote: [color=blue] > error 67 is not necessarily a dc error. it basically means that the dns > lookup failed. are you able to access the site if you try it via IE7? > > On a related note, WebDAV redirector picks up the proxy settings from IE7 so > you may need to check that as well. > > you might also want to try accessing the site directly via IP address or > perhaps the FQDN (if it's on intranet) to see if that works? > > thanks > -ather > > "JJK" wrote: >[color=green] > > Ather, > > The OPTIONS command on the root resulted in a 200 OK. Just for the sake > > of it, I made sure the server returned 207 but has status code 403 in the > > WebDAV response XML. Now the fun part is, the Vista mini-redirector crawled > > to the right directory, and got a 207 with status code 200 inside, but it > > still complained that it couldn't open the URL as a web folder (tried with or > > without Office 2007 installed). > > I also tried your suggestion of using "net use * > > https://10.1.2.3/users/foo/bar" from the command line, but I got a system > > error 67. Based on the description of that error code, it's regarding domain > > controller. Does this mean the Vista mini-redirector can only talk to a > > server that is part of the same domain, or it does reverse DNS lookup on the > > server IP and give up if that failed? I am wondering, is there any way to > > debug or enable some logging to give me more information what needs to be > > done? > > I really appreciate your spending time answering questions here. It's > > absolutely helpful for whoever is interested in running webdav on Vista. > > > > Best Regards, > > Jeff > > > > "Ather Haleem (MSFT)" wrote: > >[color=darkred] > > > a 403 response back DOES result in an abort and we do not try the next level > > > down. it's possible that in your case, the response to OPTIONS on root was > > > multi-status and thus WebDAV redirector tried the next level (/users). > > > Multi-status response will be treated as "possible" success (i.e. redirector > > > assumes that something below may actually speak WebDAV since the root > > > returned multi-status). > > > > > > The WebDAV redirector implementation has been like this eversince Windows > > > XP. The difference (as I may have mentioned before) is that Windows XP had > > > webfolders which didn't have any such restriction. WebFolders has been > > > removed from Vista and WebDAV redirector is the answer to all WebDAV related > > > traffic. > > > > > > We do understand that not being able to navigate to a WebDAV site where > > > OPTIONS doesn't get honored on root is an issue and we are looking to address > > > this in the next release. I apologize if this causing you any trouble. > > > > > > Let me know if I can be of any further help or if you need more > > > clarification regarding anything here. > > > > > > thanks > > > -Ather > > > > > > "JJK" wrote: > > > > > > > Ather, > > > > The cookie restriction makes sense, and it obviously is a result of the > > > > new Vista security model. However, I am not sure about the crawling abort > > > > upon 403's as you described. My experience was, the mini-redirector indeeded > > > > tried the next level down (i.e. /users in my example) before giving up, even > > > > though it received a 403 on the top level. Also, if the PROPFIND on the root > > > > got a 207 (Multi Status) response, but the status code in the response WebDAV > > > > XML is a 403, does it also considered a 403 or it is considered a success? > > > > The reason that I am digging further here is because the behavior is > > > > different from pre-Vista, where the crawling were attempted with errors > > > > ignoed but a request with the desired URL was still sent. I am trying to > > > > understand if this is a webdav implementation change or a potential bug > > > > there. Thank you for your time and helpful information. > > > > > > > > Sincerely, > > > > Jeff > > > > > > > > "JJK" wrote: > > > > > > > > > Ather, > > > > > Thank you for the clarification. I seem to encounter some dilemma here, > > > > > and I am not sure if it's intended or by design. > > > > > The scenario is, the user needs to logon to get a cookie to the server > > > > > first. Furthermore, the user only has permission to access directory such as > > > > > /users/foo/bar, but not the ones above. When the user tries to access that > > > > > WebDAV resource, two different things would happen: > > > > > > > > > > 1. If IE7 is running protected mode (or the URL is not in the trusted zone), > > > > > the WebDAV redirector did not send the cookie to the server. However, it > > > > > ignored the returned 403 responses and crawled all the way to the > > > > > /users/foo/bar directory (which again was rejected due to no cookie present > > > > > in the request). > > > > > 2. If IE7 is running non-protected mode (or the URL is listed in the trusted > > > > > security zone), the WebDAV redirector did send the cookie to the server. > > > > > However, it only tried the / and /users directories several times and gave up > > > > > upon 403 responses. > > > > > > > > > > Is this expected behavior for Vista WebDAV mini-redirector? Will the > > > > > installation of the Office product change the way how it behaves? > > > > > > > > > > Thanks again, > > > > > Jeff > > > > > > > > > > "Ather Haleem (MSFT)" wrote: > > > > > > > > > > > Hi Jeff- yes it is a requirement to support Depth:0 PROPFIND. It is not quite > > > > > > "new" for Vista since the Webdav Redirector that shipped with Windows XP had > > > > > > the same requirement. However, the difference is that Vista doesn't have > > > > > > Webfolder (another client for WebDAV) shipped inbox with Vista anymore and > > > > > > the WebDAV redirector (the WebDAV client that lets you map drives to a WebDAV > > > > > > resource) is used instead. With this, comes the limitation of supporting > > > > > > PROPFIND at root. > > > > > > > > > > > > Thanks. > > > > > > -Ather > > > > > > > > > > > > "JJK" wrote: > > > > > > > > > > > > > Ather, > > > > > > > Is the requirement for the root directory to support PROPFIND method > > > > > > > (with Depth: 0) new for Vista? It appears that the pre-Vista OS WebDAV > > > > > > > clients were able to communicate with WebDAV server that only allows OPTIONS > > > > > > > for the root directory. Please confirm. > > > > > > > > > > > > > > Thanks, > > > > > > > Jeff > > > > > > > > > > > > > > "Ather Haleem (MSFT)" wrote: > > > > > > > > > > > > > > > It is possible that the root of the website ([url]https://sub.server.ext[/url]) doesn't > > > > > > > > honor OPTIONS or PROPFIND request bur /folder does. If that is the case, this > > > > > > > > is expected and by design and the workaround is to have the root also honor > > > > > > > > OPTIONS and PROPFIND request. This is most likely the reason why this is > > > > > > > > failing. > > > > > > > > > > > > > > > > Thanks. > > > > > > > > -Ather > > > > > > > > > > > > > > > > > > > > > > > > "Floris" wrote: > > > > > > > > > > > > > > > > > Hi Ather, > > > > > > > > > > > > > > > > > > With IE, I'm now able to get the 'default' HTML page of the webfolder (after > > > > > > > > > I enter my credentials) by enabling 'Send LM & NTLM - use NTLMv2 session > > > > > > > > > security if negotiated' in the Administrative Tools section of the Control > > > > > > > > > Panel. Before that was enabled, this wasn´t possible. > > > > > > > > > > > > > > > > > > However, if I try to open the location as a webfolder (using a link on that > > > > > > > > > default HTML page or by using the Add Network Location wizard), I keep > > > > > > > > > getting the auth dialog. > > > > > > > > > > > > > > > > > > The net use command results in the following output: > > > > > > > > > --- > > > > > > > > > C:\Users\Floris>net use * [url]https://sub.server.ext/folder[/url] > > > > > > > > > Enter the user name for 'sub.server.ext': floris > > > > > > > > > Enter the password for sub.server.ext: > > > > > > > > > System error 67 has occurred. > > > > > > > > > The network name cannot be found. > > > > > > > > > --- > > > > > > > > > > > > > > > > > > Anyway, 'telnet sub.server.ext 443' does result in a connection. > > > > > > > > > > > > > > > > > > "Ather Haleem (MSFT)" wrote: > > > > > > > > > > > > > > > > > > > Hi Floris, > > > > > > > > > > Can you try and see if you are able to re-produce the same problem if you > > > > > > > > > > try to access this WebDAV resource via Internet Explorer? Also, can you check > > > > > > > > > > to see if "net use * <https-webdav-resources>" works via command prompt? > > > > > > > > > > > > > > > > > > > > thanks. > > > > > > > > > > > > > > > > > > > > -Ather > > > > > > > > > > lead software design engineer/test | windows core file systems | micorosft > > > > > > > > > > corporation > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > "Rick Rogers" wrote: > > > > > > > > > > > > > > > > > > > > > Unfortunately, I don't know enough about Linux' server to tell you what else > > > > > > > > > > > to try. You may want to check in a 'nix group to see if others have run into > > > > > > > > > > > this with Vista. It may be that one of Vista's default networking protocols > > > > > > > > > > > isn't in a compatible format. > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > > > > > Best of Luck, > > > > > > > > > > > > > > > > > > > > > > Rick Rogers, aka "Nutcase" - Microsoft MVP > > > > > > > > > > > [url]http://mvp.support.microsoft.com/[/url] > > > > > > > > > > > Windows help - [url]www.rickrogers.org[/url] > > > > > > > > > > > > > > > > > > > > > > "Floris" <Floris@discussions.microsoft.com> wrote in message > > > > > > > > > > > news:76260B24-B3CC-427A-8574-F863A61539CD@microsoft.com... > > > > > > > > > > > > Yes :) > > > > > > > > > > > > > > > > > > > > > > > > "Rick Rogers" wrote: > > > > > > > > > > > > > > > > > > > > > > > >> Hi, > > > > > > > > > > > >> > > > > > > > > > > > >> So to be clear, did you try logging on while IPv6 was disabled? > > > > > > > > > > > >> > > > > > > > > > > > >> -- > > > > > > > > > > > >> Best of Luck, > > > > > > > > > > > >> > > > > > > > > > > > >> Rick Rogers, aka "Nutcase" - Microsoft MVP > > > > > > > > > > > >> [url]http://mvp.support.microsoft.com/[/url] > > > > > > > > > > > >> Windows help - [url]www.rickrogers.org[/url] > > > > > > > > > > > >> > > > > > > > > > > > >> "Floris" <Floris@discussions.microsoft.com> wrote in message > > > > > > > > > > > >> news:ED8D12CE-8EDE-40DE-98EA-27EB641C668C@microsoft.com... > > > > > > > > > > > >> > Thanks for your quick reply! I disabled the IPv6 option in the nic > > > > > > > > > > > >> > properties, disabled it, and enabled it again. However, the problem > > > > > > > > > > > >> > still > > > > > > > > > > > >> > exists. Also, the webserver reports the same error. > > > > > > > > > > > >> > > > > > > > > > > > > >> > "Rick Rogers" wrote: > > > > > > > > > > > >> > > > > > > > > > > > > >> >> Hi, > > > > > > > > > > > >> >> > > > > > > > > > > > >> >> Some have reported that disabling IPv6 has resolved this issue. You'll > > > > > > > > > > > >> >> find > > > > > > > > > > > >> >> it in the properties of the 'nic in Device Manager. > > > > > > > > > > > >> >> > > > > > > > > > > > >> >> -- > > > > > > > > > > > >> >> Best of Luck, > > > > > > > > > > > >> >> > > > > > > > > > > > >> >> Rick Rogers, aka "Nutcase" - Microsoft MVP > > > > > > > > > > > >> >> [url]http://mvp.support.microsoft.com/[/url] > > > > > > > > > > > >> >> Windows help - [url]www.rickrogers.org[/url] > > > > > > > > > > > >> >> > > > > > > > > > > > >> >> "Floris" <Floris@discussions.microsoft.com> wrote in message > > > > > > > > > > > >> >> news:99B79762-0549-4E00-ACFF-12C2B9D496DC@microsoft.com... > > > > > > > > > > > >> >> >I just installed Windows Vista Business N. With my previous XP > > > > > > > > > > > >> >> >installation, > > > > > > > > > > > >> >> > I could easily connect to a https-webdav location using Add Network > > > > > > > > > > > >> >> > Location. > > > > > > > > > > > >> >> > Unfortunately, with Vista, I'm unable to pass the authentication. > > > > > > > > > > > >> >> > I'm -very- > > > > > > > > > > > >> >> > sure that I'm using the right credentials. However, the auth dialog > > > > > > > > > > > >> >> > keeps > > > > > > > > > > > >> >> > popping up. > > > > > > > > > > > >> >> > > > > > > > > > > > > >> >> > I managed to get some logging from the Linux server I'm logging into > > > > > > > > > > > >> >> > (samba.log): > > > > > > > > > > > >> >> > [2006/12/07 17:41:36, 2] auth/auth.c:check_ntlm_password(319) > > > > > > > > > > > >> >> > check_ntlm_password: Authentication for user [FLORIS] -> [FLORIS] > > > > > > > > > > > >> >> > FAILED > > > > > > > > > > > >> >> > with error NT_STATUS_WRONG_PASSWORD > > > > > > > > > > > >> >> > [2006/12/07 17:41:36, 3] smbd/error.c:error_packet(146) > > > > > > > > > > > >> >> > error packet at smbd/sesssetup.c(1093) cmd=115 (SMBsesssetupX) > > > > > > > > > > > >> >> > NT_STATUS_LOGON_FAILURE > > > > > > > > > > > >> >> > > > > > > > > > > > > >> >> > With the same credentials, I'm able to login using a Win2000 > > > > > > > > > > > >> >> > computer. > > > > > > > > > > > >> >> > > > > > > > > > > > > >> >> > Any thoughts on this? > > > > > > > > > > > >> >> > > > > > > > > > > > >> >> > > > > > > > > > > > >> > > > > > > > > > > > >> > > > > > > > > > > > > > > > > > > > > > >[/color][/color][/color] |
|
| Bookmarks |
| Thread Tools | |
| |
Similar Threads | ||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| WEBDAV | Brian Sullivan | Windows Vista | 3 | 03-25-2008 11:50 AM |
| WebDAV problems | I. Kinal | Windows Vista | 7 | 01-27-2008 10:20 PM |
| redirecting to a webdav URL | Andy Fish | Windows XP | 3 | 06-05-2007 09:00 AM |
| How to get Mac OSX (10.2.4) to communicate with Webdav? | Some One Else | Apple Macintosh Hardware | 0 | 02-06-2007 03:56 PM |
| XP and WebDAV ? | Al Dykes | Windows XP | 0 | 01-04-2007 02:05 AM |
| New To Technology Questions? | Do You Need Help with Your Computer or Device? | Do You Need Help with this site? |
