WebDAV access Win7

[stereomic]

Hi There!

I am looking for an easy way for normal people (i.e. non-IT-wizz) to preview+download+upload pictures on my NAS. I have the webexplorer (https) and sftp working, but the webexplorer doesn't support thumbnails (unless you have rediculously small file sizes) and the sftp requires installing and running a client (which often have limited preview abilities too).

So I was hoping to set up WebDAV, and have them access it using windows explorer, internet explorer or firefox etc on Win7... klicking a single link, entering a password, and done (no hastle with plugins, clients, etc...).

This seems to be more complicated than expected:
1) using internet explorer over https results in the snapshot attached: only a list, no previews, no thumbnails

Capture.PNG

2) using windows explorer and "\\servername@SSL@port\path\" results in an error after 3 failed logins. Login is correct as 1) does work... I tried changing the BasicAuthLevel's value to "2" (HKEY_LOCAL_MACHINE >> SYSTEM>> CurrentControlSet>> Services>> webClient>> Parameters) but this didn't help...
3) mapping as a network drive: same issue as 2)

Please advise, many thanks!
Mic

[Jocko]

Hi stereomic,

Yes, use webdav is a good way for what you expects.

Indeed if you use a browser, you always get a list : this is the default webdav behaviour.

To get the same environment than with your local data, you must use a webdav client or create a network drive.

See this tutorial http://help.wildapricot.com/display/DOC/Setting+Up+WebDAV+in+Windows+7

You must change the value in registry database of your computer like you wrote. I advice you to use only a http connection from your LAN and always use a HTTPS connection from a remote share.
But from your LAN, use the samba server is the better way :whistle

Check also if the service webclient is running on your computer (set automatic start option) http://computerstepbystep.com/webclient_service.html

Every day, I use this features without trouble.

[stereomic]

Thanks for your reply Jocko!

From LAN I am indeed using Samba, which works perfect!

Remote, I am still unable to map the network drive using WebDAV. Webclient service is running on my PC and started automtically; BasicAuthLevel is set to '2'. I tried 2 address types in the network location wizard: "https://myddns:port/path" and "\\myddns@SSL@port\path\". For the path I also tried "/share/1000/publiek" aswel as simply "/publiek", but everything I try results in:
1) 3 prompts to select a local certificate: selecting one ore cancelling makes no difference
2) 3 prompts for a user name & pasword: nor admin-nas, nor my custom users are accepted
3) error message: "incorrect location"

I assume something is going wrong in the login procedure. Because all works fine when I use https in a remote browser (picture from my previous post) I kind of exclude errors in ddns, port forwarding or incorrect paswords... The first prompt on certificates does seem odd and isn't there in the browser scenario...

Help is most welcome!
stereomic

[Jocko]

Hi stereomic,

The right network location to use is : https://yourddns/sharename. If you don't change the https port is useless to specify the port 443 in the url.
About sharename, you have not to use the full path, do not include 'share/1000' in the url just the name of the share and if you want a subfolder.

The login is those set for this share with the samba server but also admin-nas who have a full access on all webdav share.

[stereomic]

Hi Jocko,

I am using a different port because my ISP blocks all below 1024. But I assume port forwarding is working fine because I have remote access to WebDAV using a browser. I tried again, without the 'share/1000' part, and using admin-nas and all other users that work when I use the browser. But none of them work when attempting to map the network drive.

Are you using WebDAV over https from a remote Win7 too? Do you also get the certificate question like I described in my previous post? I am using firmware 14, but I didn't see any WebDAV changes in the 15 release notes.

Thanks,
stereomic

[Jocko]

Hi stereomic,

I am using a different port because my ISP blocks all below 1024. But I assume port forwarding is working fine because I have remote access to WebDAV using a browser.

Yes it is but only if you tested from a remote host not from your LAN

Are you using WebDAV over https from a remote Win7 too?

Yes I use a win732bits from a remote hosts (and also behind a proxy !!!)

Do you also get the certificate question like I described in my previous post?

I don't understand what you mean with "3 prompts to select a local certificate: selecting one ore cancelling makes no difference"
You just need to import the certificate authority (CA_fvdw-sl) : download it from the web-interface in the system setup menu and install it as a "trust root authority"
note: to manage the imported certificate you can use the microsoft console: certmgr.msc

I am using firmware 14, but I didn't see any WebDAV changes in the 15 release notes.

Yes there is no change between these two versions (and firmware14 worked previously without any trouble on my win7).

Note : if your ISP allows it try to cross the in/out ports and so to add a forward rule with the router port in: yourcustomport and port out: 443. it's amazing that your box don't have a default rule for https service!

[stereomic]

Hi Jocko,

Properly installing the certificate did the trick! All is working fine now.
Downside is: installing the certificate and mapping the drive would be a challenge for e.g. my grandmother...
No alternatives for dummies?

FYI - Some background on my error: I installed the certificate on a campus PC, which silently put it in the "Intermediate CA" store instead of the "Trusted Root CA" store. This only became visible after refreshing the certmgr, because the certmgr nevertheless reports a success after every attemt to put it in the trusted root store... You know a way to get around this without admin rights? For the successful test I used a private PC with admin rights, outside my LAN.

Cheers
stereomic

[Jocko]

Hi stereomic,

Glad to hear that you have successful.

Downside is: installing the certificate and mapping the drive would be a challenge for e.g. my grandmother...
No alternatives for dummies?

:scratch , you have two solutions:
- As only one installation is required you could do it yourself but maybe the grandmother house is far...
- write a step by step tutorial howto install manually the certificate : not double click on the file but use the context menu and select the option "install certificate" and then describe the following steps (select manually the trusted autorithy root store).

FYI - Some background on my error: I installed the certificate on a campus PC, which silently put it in the "Intermediate CA" store instead of the "Trusted Root CA" store. This only became visible after refreshing the certmgr, because the certmgr nevertheless reports a success after every attemt to put it in the trusted root store... You know a way to get around this without admin rights?

This happens not because you don't have admin rights but because the fvdw-sl CA is a self-signed certificate (is not a real authority).
To get a real signed intermediate Certificate Authority, we should pay this service and there would be a problem of legal liability because we could not control a malicious use of the CA certificate to create other certificates (the private key is included in the firmware to sign your certificate)