[OpenAFS] strange issue with windows client
David Bear
iddwb@asu.edu
Mon, 7 Apr 2008 16:07:43 -0700
------=_Part_16740_23300851.1207609663099
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
no debug info yet, I'm hoping to avoid that...
Heres the system info.
Windows XP Pro
Openafs 1.5.34
Kerb for windows 3.2
user lisa can go most everyone in afs that she has access to except her home
directory. She can descend paths that are controlled by acls created by me.
User home directories are set at asu.edu/users/#/#/# where # is the first
char, second char, third char of their id. The standard acl on users/#/#/ is
system:anyuser l so this is strange that she is getting any access denial.
We can go to another computer with the same setup as above, and user lisa
can get to her home directory. So we are lead to believe its a cache manager
issue.
So I erase the afscache file, and restarted the client service. No joy, same
error.
So then I went into the control panel afs applet, and set a completely new
path for the afs cache file. Restart afs, no joy, same error.
I'm rather stumped. Any suggestions?
--
David Bear
College of Public Programs at ASU
602-464-0424
------=_Part_16740_23300851.1207609663099
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
no debug info yet, I'm hoping to avoid that...<br><br>Heres the system info.<br>Windows XP Pro<br>Openafs 1.5.34<br>Kerb for windows 3.2<br><br>user lisa can go most everyone in afs that she has access to except her home directory. She can descend paths that are controlled by acls created by me. User home directories are set at <a href="http://asu.edu/users/#/#/#">asu.edu/users/#/#/#</a> where # is the first char, second char, third char of their id. The standard acl on users/#/#/ is system:anyuser l so this is strange that she is getting any access denial.<br>
<br>We can go to another computer with the same setup as above, and user lisa can get to her home directory. So we are lead to believe its a cache manager issue.<br><br>So I erase the afscache file, and restarted the client service. No joy, same error.<br>
<br>So then I went into the control panel afs applet, and set a completely new path for the afs cache file. Restart afs, no joy, same error.<br><br>I'm rather stumped. Any suggestions?<br clear="all"><br>-- <br>David Bear<br>
College of Public Programs at ASU<br>602-464-0424
------=_Part_16740_23300851.1207609663099--