On 4/22/2010 5:49 PM, Jason D. McCormick wrote: > We're trying to deploy new workstations based on Windows 7 using OpenAFS > (1.5.73) and Kerberos for Windows. I was curious how/if people are getting a > working configuration for this setup. We're encountering two major problems > that I was hoping someone on the list had already encountered and could help > out with. > > #1 - \\AFS UNC name doesn't function when making network transitions, notably > when using the Cisco VPN client but it also appears to die at other random > unrepeatable intervals (although this is during testing work). It appears > that while on certain network configurations (e.g. wired physically to the > network) the \\AFS appears to work and is bound to the AFS loopback adapter > (10.254.254.254). However unplugging the network and/or opening the VPN > appear to cause some sort of network state transition that kills off the > mappings. I found a reference to a similar problem > (<http://mailman.mit.edu/pipermail/kerberos/2009-October/015364.html>) where > Jeff said the bug is in Windows. Does anyone know if there's a workaround or > hotfix since then?
There is no work around. Microsoft has known about this bug since September 2009. More sites need to file bug reports on this issue with Microsoft. Until Microsoft is convinced that this is a serious problem they are not going to make it a priority. SP1 betas have already been cut and if this bug is going to be fixed and added to SP1, they need to hear from a broad range of OpenAFS using sites. There really is nothing more that I can do until Microsoft decides the problem is a serious problem for *their* customers. > #2 - The Windows team is using folder redirection within profiles, but only > selectively (e.g. Documents, Desktop, AppData). However something within the > synchronization service seems to think that \\AFS should somehow be available > offline. We keep seeing explorer.exe routinely consume 50% or more of the CPU > and it appears to be continuously trying to open > C:\Windows\CSC\v2.0.6\namespace\afs even though we don't have the filesystem > marked as being available offline. Am I correct in understanding from the > thread above > (<http://mailman.mit.edu/pipermail/kerberos/2009-October/015364.html>) > that this is also part of the SMB bug? This is the AFS Explorer Shell extension attempting to perform AFS if operations which are spinning due to the fact that the Netbios name resolution is failing. Its the same bug as above. > If there's an implementation guide for Win7 I'm missing, please point > it out. Thanks. There isn't one. There is nothing different about installing on Windows 7. Microsoft has a bug and it must get fixed by Microsoft. It won't get fixed until enough end user sites report it. Jeffrey Altman
smime.p7s
Description: S/MIME Cryptographic Signature
