This is a known problem with Windows 7, any version >From http://openafs.org/windows.html
"Windows 7 and Server 2008 R2 Specific Issues * There is a bug in Windows that will prevent access to \\AFS<file:///\\AFS> after an IP address has been removed or assigned after boot. When the bug is triggered, all attempts to connect to \\AFS<file:///\\AFS> will result in a "Bad Network Name" error. Please reproduce this issue locally and submit bug reports to Microsoft." Something you can try: In Network and Sharing Center, Change adapter settings, AFS loopback properties, Check "Link-layer Topology.." boxes (2) Save & reboot Repeat your experiment and when AFS fails, wait 3-5 minutes to see if it recovers. On two different systems, this has worked when adding a Microsoft VPN. It has not worked in other situations. Mickey. From: [email protected] [mailto:[email protected]] On Behalf Of Matt Renzelmann Sent: Thursday, July 08, 2010 9:32 AM To: [email protected] Subject: [OpenAFS] OpenAFS / Explorer hang when disabling/enabling NIC Hello, I've observed the following issue with OpenAFS. Platform is Windows 7 x64 "Ultimate" with all the latest Windows Update patches. The behavior occurs with the last three stable releases of OpenAFS recommended for Windows: 1.5.75, 1.5.74, and 1.5.73. Using Network Identity Manager 2.0.0.304 per Help -> About - the latest. Details of the behavior: - If I disable and then reenable the main network adapter--the one that AFS is ultimately using to access my AFS data--I observe that windows Explorer gets "stuck." It appears to be stuck in some kind of busy live-lock state. - I suspect that if I lose my Internet connection on the same adapter for any reason, I get a similar symptom, but I've not confirmed this. - Attempting to terminate the explorer process once it's in this state fails. It will not terminate. Task Manager and Process Explorer + administrative escalation is not sufficient. - All applications that use Explorer functionality, e.g. file open/save windows, will hang as soon as they invoke said functionality. - Rebooting resolves the problem, though I often have some difficulty rebooting cleanly in this scenario. More background: - I'm using the DEBUG version of AFS currently in an effort to resolve this. I've had the problem with 1.5.74/73 using the standard "release" version. - I have Process Explorer setup with symbols for AFS and Windows enabled so I can see full stack traces with all function names. Let me know if you want anything. - The tail of the afsd_init.log when the problem occurs: 7/8/2010 6:54:15 AM: Mountpoint[0] = openafs.org#openafs.org:root.cell. 7/8/2010 6:54:15 AM: Mountpoint[1] = .openafs.org%openafs.org:root.cell. 7/8/2010 6:54:15 AM: Mountpoint[2] = .root%openafs.org:root.afs. 7/8/2010 6:54:15 AM: Mountpoint[3] = cs.wisc.edu#cs.wisc.edu:root.cell. 7/8/2010 7:35:15 AM: smb_LanAdapterChange 7/8/2010 7:35:15 AM: NCBLISTEN lana=4 failed with NRC_BRIDGE, retrying ... 7/8/2010 7:35:15 AM: NCBLISTEN lana=4 failed with NRC_NOWILD, retrying ... 7/8/2010 7:35:35 AM: smb_LanAdapterChange 7/8/2010 7:35:35 AM: NCBLISTEN lana=4 failed with NRC_BRIDGE, retrying ... 7/8/2010 7:35:35 AM: NCBLISTEN lana=4 failed with NRC_NOWILD, retrying ... 7/8/2010 7:35:35 AM: smb_LanAdapterChange 7/8/2010 7:35:38 AM: NCBLISTEN lana=4 failed with NRC_BRIDGE, retrying ... 7/8/2010 7:35:38 AM: NCBLISTEN lana=4 failed with NRC_NOWILD, retrying ... 7/8/2010 7:35:58 AM: smb_LanAdapterChange 7/8/2010 7:35:58 AM: NCBLISTEN lana=4 failed with NRC_BRIDGE, retrying ... 7/8/2010 7:35:58 AM: NCBLISTEN lana=4 failed with NRC_NOWILD, retrying ... 7/8/2010 7:36:03 AM: smb_LanAdapterChange 7/8/2010 7:36:03 AM: NCBLISTEN lana=4 failed with NRC_BRIDGE, retrying ... 7/8/2010 7:36:03 AM: NCBLISTEN lana=4 failed with NRC_NOWILD, retrying ... - The log clearly shows me disabling/enabling the main network adapter. Note that I disabled it once, then re-enabled it once a few seconds later. - Let me know if you'd like more of the log--I've saved a copy. - Example of the Explorer process after I've attempted to terminate it: http://www.renzelmann.com/temp/explorer.png It hangs with these threads running indefinitely. Note that they are doing something as they are consuming CPU, but they will not terminate. Explorer normally contains many additional threads--these have exited cleanly in this screenshot. - System configuration includes: * A wireless adapter. The Wireless adapter is enabled but not in use or connected. * A wired adapter. The wired adapter is used for network/Internet. * Several VMware Workstation 7 Virtual NICs. * A virtual Hamachi VPN NIC. The VPN adapter is in use, but I doubt is the cause as I've had this issue before I installed Hamachi. * The OpenAFS Loopback adapter. - I can reproduce the problem easily by disabling the wired adapter and then reenabling it, and also attempt to access a mapped AFS drive in Windows Explorer. - I never have any problems if I leave the OpenAFS service disabled and have no drives mapped, so I am certain that an important part of the problem is something OpenAFS is doing--perhaps it's conflicting with something else? Does anyone have any recommendations on how to proceed to get OpenAFS working reliably with this setup? Do you need any additional information? Thanks and regards, Matt
