From: Philipp Flesch <philipp-3cc/OM5pcIkb1SvskN2V4Q@public.gmane.org>
To: linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: Steve French <smfrench-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Subject: Re: Mounting error after upgrading to wheezy - Changes in mount.cifs from 4.5 to 5.5?
Date: Wed, 18 Dec 2013 18:43:52 +0100 [thread overview]
Message-ID: <52B1DED8.9050001@phflesch.de> (raw)
In-Reply-To: <CAH2r5mv3yChbfKm0QBBZ=LymBx7Ssw6J_RmVMZQ1LJ8uDjLBuA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Hi Steve,
Am 18.12.2013 17:51, schrieb Steve French:
> I doubt that the sec=ntlm would make much of a difference but would be
> interesting to see what the access denied is coming back on - since
> from what you describe listing the contents of the root directory of
> the share should be permitted to both users so this is not an access
> denied on top of prefixpath issue as we had seen a few years ago.
Sorry, but perhaps I described the share-configuration not exact enough.
listing the contents is only allowed in the final (second) subdirectory,
but not in the root of the share and not in the first subdirectory:
no listing allowed \\fs01\Share
no listing allowed \\fs01\Share\DepartmentA
listing allowed \\fs01\Share\DepartmentA\Stats
Greetings
Philipp
prev parent reply other threads:[~2013-12-18 17:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-18 13:10 Mounting error after upgrading to wheezy - Changes in mount.cifs from 4.5 to 5.5? Philipp Flesch
2013-12-18 16:43 ` Jeff Layton
[not found] ` <20131218114326.7f719964-4QP7MXygkU+dMjc06nkz3ljfA9RmPOcC@public.gmane.org>
2013-12-18 17:39 ` Philipp Flesch
[not found] ` <52B1DDB7.3070909-3cc/OM5pcIkb1SvskN2V4Q@public.gmane.org>
2014-01-16 8:39 ` Pierre Frenkiel
2013-12-18 16:51 ` Steve French
[not found] ` <CAH2r5mv3yChbfKm0QBBZ=LymBx7Ssw6J_RmVMZQ1LJ8uDjLBuA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-12-18 17:43 ` Philipp Flesch [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52B1DED8.9050001@phflesch.de \
--to=philipp-3cc/om5pcikb1svskn2v4q@public.gmane.org \
--cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=smfrench-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.