Steve, et al -
I'm using OpenAFS client version 1.5.16 on a number of systems with no
problems whatever accessing my MSU AFS network volume. FWIW...
Regards,
John Fishbeck
MSU Physical Plant Computer Systems and Networking Group
-----Original Message-----
From: MSU Network Administrators Group [mailto:[log in to unmask]] On
Behalf Of STeve Andre'
Sent: Wednesday, August 06, 2008 3:39 PM
To: [log in to unmask]
Subject: Re: [MSUNAG] AFS client on WinXP
Thank you, Jeff!
I have a slew of older versions, which I will attempt to play with when
the user gets here.
Thanks again.
--STeve Andre'
On Wednesday 06 August 2008 15:12:10 Jeff Quinn wrote:
> Other people are reporting similar problems. According to Jeff
Altman:
> > This is a known bug that was fixed within 24 hours of a bug report
> > arriving in the OpenAFS RT.
> >
> > The fix will appear in 1.5.52.
> >
> > We do recommend that drives be mapped using the Explorer Shell and
> > the \\AFS unc path.
>
> -Jeff
>
> -----Original Message-----
> From: MSU Network Administrators Group [mailto:[log in to unmask]] On
> Behalf Of STeve Andre'
> Sent: Wednesday, August 06, 2008 2:24 PM
> To: [log in to unmask]
> Subject: [MSUNAG] AFS client on WinXP
>
> I have a user who wants to use AFS. They used it before, and I set
> things up for them and left it alone. That was easy. This time, I
> seem to be dealing with a sick machine. When I get tokens that works,
> but mapping a drive results in the mapped drive being a single
> character, usually a control char. I made the attempt to install the
> AFS client on the persons laptop, but it too is weird.
>
> So then, besides my fighting the problems on the two machines, does
> anyone have experience with version 1.5.51 on XP? If it turns out
> that 1.5.51 doesn't work, whats the latest one that does?
>
> Thanks.......
>
> --STeve Andre'
> Political Science
|