WebDAV problem

1,152 views
Skip to first unread message

dp9903

unread,
Jun 27, 2012, 7:18:31 AM6/27/12
to tacitd...@googlegroups.com
I can't connect to my NAS drive via folderSync but I can on my computer.
My NAS is an iomega ix2-200 Storcenter Cloud Edition.

The path is https://<myNASServer>.com/WebDAV/Pictures

Is there anyone who may know the problem.

I have contacted the support team directly and attached a log file.
Has anyone else got this working?

dp9903

unread,
Jun 27, 2012, 8:09:50 AM6/27/12
to tacitd...@googlegroups.com
The url also works in the stock Android browser.
https://<myNASServer>.com/WebDAV/Pictures

Support User

unread,
Jun 27, 2012, 9:10:23 AM6/27/12
to tacitd...@googlegroups.com

Any reason you set the port to 80, as seen in the log file? Default for https is 443 which would be used had you not set it to 80.

Best regards
Anders Carlsen

www.tacit.dk
(Sent from my Galaxy Nexus)

dp9903

unread,
Jun 27, 2012, 9:16:16 AM6/27/12
to tacitd...@googlegroups.com
I didn't but I noticed that in the log too.
I've tried 443 but no difference.

Support User

unread,
Jun 27, 2012, 9:20:38 AM6/27/12
to tacitd...@googlegroups.com
What does the NAS webserver log say about the error?

Best regards
Anders Carlsen
Software Developer

If you like our apps, please give them a 5-star rating. Thanks. :-)
 
Tacit Dynamics


dp9903

unread,
Jun 27, 2012, 9:37:27 AM6/27/12
to tacitd...@googlegroups.com
Not sure how to find that.
Would I need ssh access?

Support User

unread,
Jun 27, 2012, 9:40:05 AM6/27/12
to tacitd...@googlegroups.com
I don't know. Maybe.

dp9903

unread,
Jun 29, 2012, 5:59:13 AM6/29/12
to tacitd...@googlegroups.com
Anders,
I'm sorry but I've decided not to continue debugging the webdav sync.
Other android webdav clients didn't work either.  Funny how windows just works!
I'm going to rely on smb sync instead.
Good luck with the app which is excellent.

Peter Neyt

unread,
Oct 29, 2012, 8:06:52 AM10/29/12
to tacitd...@googlegroups.com
Hi

I'm having the same problem unfortunatly. I can't connect to my iomega nas drive with webdav (Windows can connect just fine). Is there a way to debug this issue? I've also contacted iomega support. Let's solve this annoyance...

BR
Peter

Op woensdag 27 juni 2012 15:40:05 UTC+2 schreef Anders het volgende:

Support User

unread,
Oct 29, 2012, 6:46:14 PM10/29/12
to tacitd...@googlegroups.com
To fix these issues it would be a big help to get any webdav server logs that might contain reasons for connection errors.

Peter Neyt

unread,
Nov 1, 2012, 5:54:09 AM11/1/12
to tacitd...@googlegroups.com
Hi

I ran a litmus test on the Iomega disk with the results in attachment.
Hopefully this will show something.

Regards
Peter

Op maandag 29 oktober 2012 23:46:15 UTC+1 schreef Anders het volgende:
litmus.pdf

Danielo Rodríguez

unread,
Nov 6, 2012, 9:21:59 AM11/6/12
to tacitd...@googlegroups.com
I thin all you guys having this issue is because the port number.

The webdav port number can be different on each NAS / server (mine, for example is 5001).
Check that out in your servers.

The reason it works with windows It's because I think you are accessing by samba, not webdav.

Peter Neyt

unread,
Nov 6, 2012, 9:58:25 AM11/6/12
to tacitd...@googlegroups.com
Unfortunatly not. In my case, the iOmega drive responds to ports 80 (http) and 443 (https). My router is setup as it should.
In Windows Explorer I am connecting with webdav (Add Network Location - Other Locations - http://iomega/webdav ...).
Even Internet Explorer works. But not FolderSync.
I've also opened a case with iOmega. Maybe they will find what is happening with their webdav implementation.
If you want I can open a port and give you a temp account to try it yourself on my disk.

Regards
Peter

Op dinsdag 6 november 2012 15:21:59 UTC+1 schreef Danielo Rodríguez het volgende:

Support User

unread,
Nov 8, 2012, 2:40:07 PM11/8/12
to tacitd...@googlegroups.com
Sure, send it to support (at) tacit.dk
Message has been deleted

Peter Neyt

unread,
Nov 8, 2012, 5:02:43 PM11/8/12
to tacitd...@googlegroups.com
The 'solution': 

The Iomega webdav implementation definitively have a bug.
Access to this url works:    http://xxx.dyndns.org/webdav/anders
This returns 404 not found: https://ciseaux.dyndns.org:443/webdav/anders/ (it should work also)
 
If I configure a folderpair to use startfolder /webdav/anders/folder it works. So the trailing slash on the root webdav folder makes it fail, but not on any of the child folders. I tried a windows webdav client - it can initially connect if I don't add the slash to the configuration, but when I browse to a subfolder and then to parent folder that client also fails.
http://xxx.dyndns.org/webdav/anders/folder  - works
http://xxx.dyndns.org/webdav/anders/folder/ - works
A solution for you could be to specify a child folder for the account start folder field, and not the user root folder - then it should work.


Thx Anders!

Peter

Op donderdag 8 november 2012 20:40:08 UTC+1 schreef Anders het volgende:
Reply all
Reply to author
Forward
0 new messages