Netgear ReadyNas 212 & WebDav Over HTTPS Not working!

[StanTheMan01]

Hi all,

Recently got a Ready Nas 212 and i'm struggling using WebDav over HTTPS.

WebDav Over HTTP works fine, I can add it as a network location, or map it as a drive and it works fine.

If I try to add the network location with https instead of http I get the error 'The folder you entered does not appear to be valid. Please chose another location'.

I'm assuming this could be to do with the SSL certificate, so i've downloaded the certificate, added it to trusted root store but still get the same issue.

Any ideas?

Thanks

[JennC]

Hello StanTheMan01,

Have you enabled HTTPS? That is in the admin page's System > Settings.

Welcome to the community!

Regards,

[StanTheMan01]

Hi Jennc,

Thanks for the reply. Yes, HTTPS is enabled, in fact, over a web browser, I can access the https interface of my shared folder and view the files in a browser, but using WebDav, it refuses to work.

Any ideas?

Thanks

[JennC]

Hello StanTheMan01,

Can you try this on another computer? Add or create a drive letter pointing to https://<NAS IP>

Article: http://kb.netgear.com/app/answers/detail/a_id/24784/~/readynas-os-6%3A-configure-webdav-access-from-...

Regards,

[StephenB]

There is a patch for webdav here: https://community.netgear.com/t5/Using-your-ReadyNAS/Error-while-uploading-with-webdav-after-upgradi...

It might not be relevant for your issue, but perhaps worth a try.

[StanTheMan01]

Thanks for the replies.

I tried mapping the network drive as https://ipaddress I get prompted for a username/password and after entering them i get an error "a device attached to the system is not functioning"

So I tried mapping https://ipaddress/Share (Share is the actual name of my share) and i get the error 'unexpected network error occured'

I also installed the patch for WebDav that was suggested and this also didn't help.

If I map the drive as  http://ipaddress/Share it works fine.

This is definetly something specific to webdav and HTTPS. I'm not sure if this is an issue with Netgear implementation or if it's a Windows issue. I've now tried a Windows 7 machine, a Windows 8 machine, and a Windows 10 machine all with the same problem.

Thanks

[JennC]

Hello StanTheMan01,

How about changing the share name to a unique one?

Regards,

[JennC]

Hello StanTheMan01,

We’d greatly appreciate hearing your feedback letting us know if the information we provided has helped resolve your issue or if you need further assistance. 

If your issue is now resolved, we encourage you to mark the appropriate reply as the “Accept as Solution” or post what resolved it and mark it as solution so others can be confident in benefiting from the solution. 
 
The Netgear community looks forward to hearing from you and being a helpful resource in the future!
 
Regards,

[IT-SW]

I have this same issue on my Rn3138 and my 312.  Would love to have a solution to this.

[StanTheMan01]

Hi, sorry for the slow reply, been on holiday!

Changing the share name appears to make no difference, i've made several shares with different names and it happens to them all.

I feel like this is some kind of fundamental issue with how webdav/SSL has been implement on the device, either that or an issue with how webdav operators on Windows. Although having said that, i have tried this on Windows 7, 8 & 10, all with the same error.

Thanks

Ed