Followup:
- it seems that "Windows 7 Enterprise" is not affected by this bug, or at 
least not always.

- "Windows 7 Professional" _is_ affected, and this is the version 
'pre-installed' on many machines.

We expect that the home editions are buggy too, but that "Ultimate" 
probably isn't, although we've not been able to test these.
Dartmouth recommends "Enterprise" and that is the version which our 
Consulting Group have been installing on faculty systems when needed.

Feedback to corroborate or destroy this hypothesis is welcome from any 
Windows 7 users.


Richard


On Thu, 29 Jul 2010, Richard Brittain wrote:

> There are known problems with windows 7, particularly on laptops, and openafs 
> client.
>
> Windows 7 has a bug which may prevent the OpenAFS client from functioning if 
> the system has changed IP address for any reason (sleep/hibernate and change 
> location, switch from wired to wireless, or run VPN).  The system must be 
> rebooted to be able to access AFS again.
>
> A laptop booted with no network, and then connecting to wireless, may count 
> as an address change and therefore the OpenAFS client can hang. This is 
> commonly the case on a laptop using Dartmouth Secure wireless. Not all 
> Windows7 systems show this effect -- some continue to work, after a delay of 
> a few minutes following a network change.
>
> With windows 7, the latest OpenAFS client (1.5.75 as of 7/29) is recommended, 
> for other reasons.
>
> This bug is discussed in more detail at 
> <http://docs.openafs.org/ReleaseNotesWindows/ch03s43.html>

-- 
Richard Brittain,  Research Computing Group,
                    Kiewit Computing Services, 6224 Baker/Berry Library
                    Dartmouth College, Hanover NH 03755
[log in to unmask] 6-2085