AFS-USERS Archives

July 2010

AFS-USERS@LISTSERV.DARTMOUTH.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Richard Brittain <[log in to unmask]>
Reply To:
AFS users at Dartmouth <[log in to unmask]>
Date:
Thu, 29 Jul 2010 17:41:39 -0400
Content-Type:
TEXT/PLAIN
Parts/Attachments:
TEXT/PLAIN (26 lines)
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

ATOM RSS1 RSS2