I can't fix bugs that were never reported. This e-mail includes two: 1. 64-bit MSI loopback installer doesn't work
2. Some cells can be accessed but not others. There is no EXE installer for 64-bit because the installer product is 32-bit only. After 1.6 I do not plan to support the EXE (Nullsoft) installer at all. The loopback adapter installer code is shared between both types. If it works for one, it should work for the other. If it isn't, then someone needs to file a bug report ([email protected]) with details of the failure cases. Jeffrey Altman On 4/23/2011 1:15 PM, John Tang Boyland wrote: > The student claimed that the "AFS" network > was indeed created by the AFS service, and was not pre-existing. > (This is the second time this has happened to one of > my students -- it could be that the newest Windows 7 x64 > just doesn't work with AFS. But on the other hand, another student > just got a new Windows 7 x64 computer and got a new set of > errors -- they can access some AFS cells but not others (ours!); > they claim to have disabled any firewall; > It's amazing how many different failure modes OpenAFS has on Windows.) > > He did not want to uninstall Loopback adapter. > > Instead he installed Ubuntu and now AFS works fine. > Since I never use Windows, I can't complain with this fix... > > Thanks for the hard work of all OpenAFS Windows people. > I'll keep posting problems that show up and any solutions we find. > (Currently the way that works for Windows 7x64 the best is to > - install the 32 bit version of OpenAFS contra warnings > just for the Loopback adapter > - install 64bit KfW from secure-endpoints (thanks!) > - install the 64 bit version of OpenAFS > But even this fails sometimes.) > > I suppose if there was an EXE installer for 64 bit, or > if the MSI installer came with a working Loopback Adapter -- we wouldn't > need to have the extra 32 bit step. > > Regards, > John Boyland > > ] Date: Thu, 21 Apr 2011 10:28:36 -0400 > ] From: Jeffrey Altman <[email protected]> > ] Organization: Secure Endpoints Inc. > ] To: [email protected] > ] Reply-To: [email protected] > ] Subject: Re: [OpenAFS] Yet another Windows 7 (64 bit) problem: "Listening" > ] > ] This is an OpenPGP/MIME signed message (RFC 2440 and 3156) > ] --------------enig1B20BA9EC8FBBF112EC99021 > ] Content-Type: text/plain; charset=UTF-8 > ] Content-Transfer-Encoding: quoted-printable > ] > ] On 4/20/2011 11:04 AM, John Tang Boyland wrote: > ] > <quote> > ] > nbtstat -s (shows all sessions in a table with destination IP) > ] >=20 > ] > Local Name State In/Out Remote Host Input Output > ] > ------------------------------------------------------------------- > ] > AFS Listening > ] >=20 > ] > nbtstat -n (shows all local netbios names) has AFS as a network connect= > ] ion > ] > (all together there is Local area connection 1,2 and AFS). > ] > </quote> > ] > ] The fact that the AFS Server is Listening and there are no connections > ] to it after performing a NET VIEW \\AFS is an indication that Windows 7 > ] is not connecting to the locally defined service. Since NET VIEW \\AFS > ] is returning successfully I suspect that the name "AFS <20>" is being > ] located as a valid name elsewhere on the network. > ] > ] What you should see is something similar to: > ] > ] AFS: > ] Node IpAddress: [10.254.254.253] Scope Id: [] > ] > ] NetBIOS Connection Table > ] > ] Local Name State In/Out Remote Host Input > ] Output > ] > ] -------------------------------------------------------------------------= > ] --- > ] AFS Connected In GALATEA <00> 8MB 13MB > ] AFS Listening > ] > ] Wired: > ] Node IpAddress: [172.16.16.10] Scope Id: [] > ] > ] NetBIOS Connection Table > ] > ] Local Name State In/Out Remote Host Input > ] Output > ] > ] -------------------------------------------------------------------------= > ] --- > ] GALATEA <00> Connected Out AFS <20> 13MB 8MB > ] > ] > ] > ] > ] > ] --------------enig1B20BA9EC8FBBF112EC99021 > ] Content-Type: application/pgp-signature; name="signature.asc" > ] Content-Description: OpenPGP digital signature > ] Content-Disposition: attachment; filename="signature.asc" > ] > ] -----BEGIN PGP SIGNATURE----- > ] Version: GnuPG v1.4.9 (MingW32) > ] > ] iQEcBAEBAgAGBQJNsD8WAAoJENxm1CNJffh4WtsH/2pOfj/bh16xaYARq0Nv5Ogo > ] 1diNTo2TeoCeoKI9nXvJ9bkj1PU55kMRkEWFgBGj+x1ZkiDZKHb+l/IgLTKGqVsM > ] Qe0Do6c44tROadWc/8Sn+qSKT6k6b+FIYgP3tERTYC6HrKnMtNiHeIb8iHHcgJzm > ] FRv+wohd+9jRHBPnVOzVyfbY/kZNBOi/qfAxNmVqZ4cN5t3ONTr97XxDHO6aGezv > ] w99dM4g5ocPU8iMvGyM66GwScMu6JLoN7SYL1yH26V9/NOnsc0KJrnedIvOnqqVw > ] JDoY0FHLwvJedZ5mAOfSD3j9TeapsO2/zHMkOz3bkE18jh9K17I5K02G9jAhanQ= > ] =rTAE > ] -----END PGP SIGNATURE----- > ] > ] --------------enig1B20BA9EC8FBBF112EC99021-- > ] > ] > ] > ] --__--__-- > ] > ] _______________________________________________ > ] OpenAFS-info mailing list > ] [email protected] > ] https://lists.openafs.org/mailman/listinfo/openafs-info > ] > ] > ] End of OpenAFS-info Digest > _______________________________________________ > OpenAFS-info mailing list > [email protected] > https://lists.openafs.org/mailman/listinfo/openafs-info >
signature.asc
Description: OpenPGP digital signature
