On 3/8/2011 10:01 AM, Ezra Keshet wrote:
> Dear OpenAFS community,
>
> I returned yesterday from a week-and-a-half long trip to find that my AFS
> set-up
> no longer works. The AFS icon next to the NIM icon is now broken ("OpenAFS
> Service cannot be reached") and obtaining AFS tokens via NIM fails after a
> long
> wait. Kerberos credentials are obtained almost immediately. If I use the
> afscreds.exe program instead of the NIM, I receive the error 11862791.
> Inside
> the AFS control panel, everything looks fine -- it says that the Service is
> running. I restarted my computer several times, to no avail. I was never
> able
> to obtain AFS tokens.
>
> I did some research on this list about the 11862791 error and Windows 7 (I
> run
> Win7 Ultimate). It did not sound like I had the exact same problem, since
> most
> people reported losing AFS access after network changes, and mine actually
> did
> not work at all. However, I decide to try upgrading to the latest prerelease
> version of OpenAFS, which was supposed to help with the 11862791 problem. I
> am
> now running 1.5.9902, but the problem persists.
>
> Any suggestions or workarounds would be greatly appreciated, since I do a
> large
> part of my work over AFS. Also, please let me know if I can provide any
> further
> information. I do not know if AFS has log files, but given their location, I
> could certainly send that info along as well.
>
> Thanks!
> Ezra1.5.9902 (1.6.0pre2) corrects an error in OpenAFS that was aggravating a bug that Microsoft introduced in Windows 7 that has yet to be resolved. All of the open cases that were filed with Microsoft on the issue were closed because those organizations suffering from the Windows bug could no longer reproduce it after deploying 1.5.9902. Still the Microsoft bug remains. If you are in a position to request that Harvard open a support case with Microsoft on this issue, that would be the most helpful thing you can do. The location of the log files are documented in the troubleshooting section of the release notes which are installed on your system. You can access them via Start Menu->Programs->OpenAFS->Documentation. %windir%\temp\afsd_init.log would be the place to start. You do not mention if you are experiencing the problem with a wifi network or a wired network. If you are experiencing the problem with a wired network that and a static IP address, then your problem is not the aforementioned Microsoft bug. If afsd_init.log file indicates that a network change has occurred, then it is most likely the Microsoft bug. Jeffrey Altman
signature.asc
Description: OpenPGP digital signature
