[OpenAFS] weird access denied issues with windows client
Mon, 21 May 2012 21:01:36 +0200
hm. In all cases observed so far, we have been able to eliminate this
issue by installing the latest version of the windows client and by
doing a "fs flushall". I'll let you know whether it reappears on those
On 18.05.2012 14:55, Jeffrey Altman wrote:
> The lack of event log messages is good in that it indicates that
> the afsd_service is not experiencing communication
> issues with your file servers and volumes are not inaccessible.
> The troubleshooting section of the Release Notes which are installed
> on each OpenAFS client machine provides hints on how to use the
> "fs trace" commands and SysInternals Process Monitor to collect
> information about what operations OpenAFS client is performing
> and what the result for each operation is. "fs trace" provides the view
> from the afsd_service.exe and Process Monitor provides the view from
> the application.
> (Start Menu->Programs->OpenAFS->Documentation->Release Notes)
> On Friday, May 18, 2012 2:26:01 AM, Christian wrote:
>> I can see these three:
>> OpenAFS Start Pending. Version OpenAFS_1.7.1300.
>> OpenAFS Running. RDR interface
>> Security Level is Crypt.
>> All at system startup. Nothing else. BTW, the machine is configured to
>> use freelance and use DNS to look for dbservers. Thanks,
>> On 18.05.2012 07:25, Jeffrey Altman wrote:
>>> Are there any "AFS Client" messages in the Windows Application Event
>>> On Thursday, May 17, 2012 7:13:26 PM, Christian wrote:
>>>> we are seeing some weird "access denied" issues with windows clients
>>>> in our cell (iqo.uni-hannover.de). One example is openafs 1.7.13 64
>>>> bit. I have tokens, can access certain volumes using explorer, but
>>>> others give me "permission denied", although I can access them under
>>>> linux. Sometimes, I can access volumes under the RW tree, but not
>>>> under the RO tree. This is always different from machine to machine.
>>>> It does not only concern our cell, but also browsing other cells from
>>>> our machines (e. g. desy.de). What could be wrong here? How can I best
>>>> help debug this? Best,
>>>> OpenAFS-info mailing list