Submitted report for the integrated client. SMB client:
C:\Users\rcc2>net use e: \\AFS\afsdemo.cit.cornell.edu The command completed successfully. C:\Users\rcc2>net use f: \\AFS System error 67 has occurred. The network name cannot be found. C:\Users\rcc2> The Internet Explorer "Map network drive" method also works (as long as I specify a particular cell). My problem with drive mapping appears to be that I was attempting to map \\AFS instead of a particular cell. And I don't have any trouble getting tokens in this NATed Win7 32-bit Vbox instance with the SMB client. -----Original Message----- From: openafs-info-ad...@openafs.org [mailto:openafs-info-ad...@openafs.org] On Behalf Of Jeffrey Altman Sent: Monday, May 17, 2010 5:02 PM To: openafs-info@openafs.org Subject: Re: [OpenAFS] AFS evaluation I am almost 99.9% sure that your problem is the Microsoft bug. If the service is running and "nbtstat -n" reports "AFS <20>" registered on the loopback adapter and "nbtstat -S" reports "AFS" listening but there are no connections to it, then you are experiencing the Microsoft bug. As for the "openafs.org" being reported in Network->AFS and nothing else I would like to see a dump of the HKLM\SOFTWARE\CurrentControlSet\Services\TransarcAFSDaemon\Parameters key and the %windir%\temp\afsd_init.log file. Please open a ticket for the issue at openafs-b...@openafs.org and provide a path to the data. It can be somewhere in an afs cell. Jeffrey Altman On 5/17/2010 4:10 PM, Rick Cochran wrote: >>> >>> * Windows 7 client (1.5.74) has authentication issues >> >> Please clarify what your authentication issue is. Since your realm and >> cell do not have the same name I suspect you have configuration data >> that you have not specified. > > We have had good results with 32-bit Win7 with both 1.5.74 and 1.5.7401. > > With 64-bit Win7, 1.5.7401 works fine, but 1.5.74 gets > > aklog: ktc 7 (11862791) while obtaining tokens for cell > afsdemo.cit.cornell.edu > > which translates to > > 11862791 (ktc).7 = Cache Manager is not initialized / afsd is not running > > which I am pretty sure is not true. > > One limitation I have is that I don't personally have a machine running > 64-bit Win7, and the people who do are exceedingly busy. I will attempt > to crank up a Vbox instance for myself. > >>> * Windows 7 client (1.5.74) running in a NATed VirtualBox instance >>> cannot map a drive letter to "\\AFS". >> >> Please clarify how you are attempting to map a drive letter? >> Are you using "NET USE<d:> \\AFS\.... or the Explorer Shell drive >> mapping dialog? > > The latter. Since I have since installed 1.5.7401, I can't try the > former. But see next section. > >>> * Windows 7 client (1.5.7401) running in a NATed VirtualBox >>> instance >>> cannot access any cell other than openafs.org. >> >> Do you mean that you installed it with the local cell set to its default >> at "openafs.org" and no other cells are listed in the Explorer Shell >> under \\AFS by default? Freelance mode (aka Unix dynroot) is >> on by default and when it is used cell names are added to the local >> root.afs volume as they are accessed. >> >> Or do you mean something else? > > The default cell is set to afsdemo.cit.cornell.edu (our demo cell), and > the db server is added to the CellServDB. > > Interestingly, this problem also occurs with 1.5.7401 - nothing but > ".openafs.org", ".root", and "openafs.org" appear in the "AFS" folder > under "Network". > > Again, this happens in a 32-bit Win7 NATed VirtualBox instance. > >>> * Windows 7 client works OK in 32-bit "bridged" VirtualBox >>> instance. >> >> I will of course assume that you have read the Windows release notes >> and in particular 3.43, Known Issues with Microsoft Windows Vista, >> Windows 7, and Server 2008 [R2] >> >> http://docs.openafs.org/ReleaseNotesWindows/ch03s43.html > > This doesn't sound like the problem since it _never_ works no matter how > long I wait. > > This description from http://openafs.org/windows.html may be relevant: > > -------------- > Windows 7 and Server 2008 R2 Specific Issues > > * 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. > -------------- > > I will reinstall 1.5.74 and see what happens when I "NET USE ...". > > -Rick > _______________________________________________ > OpenAFS-info mailing list > OpenAFS-info@openafs.org > https://lists.openafs.org/mailman/listinfo/openafs-info >
