Jeffrey Altman <jalt...@secure-endpoints.com> wrote: ] On 4/28/2011 1:20 PM, John Tang Boyland wrote: ] > Here is the problem I alluded to earlier: ] > I have a student who bought a new laptop with Windows Version 6.1.7600 and ] > installed NIM and OpenAFS 1.5.9904 and things ALMOST work. ] > ] > They can get tokens and can go to \\afs\openafs.org ] > and \\afs\cs.wisc.edu but not \\afs\cs.uwm.edu ] > When they try, they get the message: ] > "\\afs\cs.uwm.edu refers to a location that is unavailable. It could be ] > on a hard drive on this computer, or on a network. Check..." ] ] this means that the evaluation of the mount point "\\afs\all\cs.uwm.edu" ] is incorrect. This could be a bug introduced in 1.5.9904 which is fixed ] in the source tree waiting for 1.5.9905 (1.6.0pre5) to be released. ] ] "fs lsm \\afs\all\cs.uwm.edu" will report the mount point info. ] If its wrong, "fs rmm \\afs\all\cs.uwm.edu" and "fs mkm ] \\afs\all\cs.uwm.edu <correct-target>" ] ] Or it could be something else....
There was indeed a period in the mountpoint. Your instruction enabled us to fix the problem. Thanks, John Boyland _______________________________________________ OpenAFS-info mailing list OpenAFS-info@openafs.org https://lists.openafs.org/mailman/listinfo/openafs-info