-
All replies
-
Helpful answers
-
-
-
Nov 18, 2011 9:00 AM in response to TK321by grweyer,I saw the same symptoms and found a solution that worked in my environment. The non-admin account was missing ~/Library/Logs (/Users/testuser/Library/Logs). Once I created that directory I was able to connect and observed several files appear in the Logs directory including a lock file and a pid file.
-
Nov 23, 2011 4:57 PM in response to grweyerby jjasper,Not working for my my non-admin users already have that directory
-
-
Feb 21, 2012 8:18 AM in response to akreisby TK321,I am still having the problem.
But I have not installed the latest Server OS update yet either.
-
May 31, 2012 4:30 AM in response to akreisby akreis,Problem renewed since updating to 10.7.4. Users are unable to access webdav share points (only admin can access). User accounts receive error 503.
No problems with 10.7.3
-
May 31, 2012 8:14 AM in response to TK321by David Urban,Apple has a document on setting webdav up using https. It is the only thing that got it working for me.
http://support.apple.com/kb/HT4777
David Urban
-
May 31, 2012 11:34 AM in response to David Urbanby akreis,Thanks, but I am using Lion Server 10.7.4 with Open Directory.
-
May 31, 2012 12:02 PM in response to akreisby David Urban,I am also using Lion server 10.7.4 with OD and was not able to connect to the webdav server until I followed the apple document. It didn't work unsecured and I wanted secured so when I made these changes it works great. I can get to my files on my phone and any other webdav client.
-
Aug 21, 2012 3:28 PM in response to TK321by Tarny,I know this is bumping an old thread up, but I just ran into this challenge at a customers. Try this:
Check in the /var/webdav_sharing directory, there should be a set of directories named after the short names of the users that have connected by webdav. Inside those directories are the Logs directories. Then check the ownership of those directories. The ownership needs to match the names of the directories. There are several reasons that the directories might have incorrect ownership, but the fix is easy. If there are a few Logs directories with incorrect ownership, then just chown them to the correct owner, if on the other hand you have a large number, you could rename teh webdav_sharing directory as a previous copy, create a new webdav_sharing directory and then new connections by webdav users should create correct ownership directories and Logs directories inside of them. Keep the previous copy around a while to make sure that nothing is needed from it.