Re: [OpenAFS] OpenAFS for Windows vs XP SP2

[Jeffrey Altman]

Tim C. wrote: The behavior I was expiriencing was just like someone else already posted. I am running XP sp1. I haven't tried the latest daily build, but someone said that was showing the same behavior. I will attempt to try that version at some point and let you know if it works for me. Tim The behavior which has been described simply means that one or more of the functions which are called during the process of populating the drive list are blocking. I have installed XP SP2 Beta on a machine and been able to demonstrate at least one system in which this problem does not occur.  Therefore, we are still at square one when it comes to figuring out which aspect of the system configuration is producing this problem.  There must be something common to the systems which are experiencing the problem.  Perhaps it is a class of network drivers from a particular vendor; or a particular network configuration (network bridge plus loopback); or a firewall product; or a VPN client; or something else. In the latest build which has been uploaded but not tested by anyone, I have reduced the number of times and under which conditions the network configuration is probed in an attempt to determine the proper Netbios Name.  Hopefully this will have a positive impact. If not, I would like to know if the problem is caused by some tricky code which is being used to probe each network interface to determine the display name assigned to the adapter.  please try adding the following value to the registry:   [HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\Parameters]       "NoFindLanaByName" (DWORD) = 0x1 Jeffrey Altman