"""
* If a *beta* AFS plug-in for Network Identity
Manager ........................................... no
* The AFS plug-in for Network Identity Manager
provided as part of OpenAFS 1.5.74 requires MIT
Kerberos for Windows 3.1 or above. ................ using 3.2.2
* Directory and File Change Notifications are
ignored when accessing AFS via UNC paths .......... noted
* The help files provided with OpenAFS are
in .HLP format. .................................. noted
* There is a bug in Windows that will prevent
access to \\AFS after an IP address has
been removed or assigned after boot. When
the bug is triggered, all attempts to connect
to \\AFS will result in a "Bad Network Name"
error. Please reproduce this issue locally
and submit bug reports to Microsoft. .............. below
"""
I'm still confused then. I'm not at the point where I am even
trying to access \\AFS. I'm still trying to get a token.
On 6/23/2010 2:12 PM, Jeffrey Altman wrote:
On 6/23/2010 12:32 PM, Jeff Blaine wrote:
On 6/23/2010 12:06 PM, Jeffrey Altman wrote:
Which operating system version?
If the service is running but it cannot be reached, it is probably an
Microsoft SMB redirector issue. If the OS is Windows 7, please read
the OpenAFS for Windows release notes.
Windows 7
I'm not able to find anything in the release notes
other than the UAC "Run As Administrator" info. Is this
what you're referring to? What should I "Run As
Administrator"?
I meant this which needs to be merged into the release notes:
http://www.openafs.org/pages/windows.html#1_5_issues
_______________________________________________
OpenAFS-info mailing list
OpenAFS-info@openafs.org
https://lists.openafs.org/mailman/listinfo/openafs-info
