[OpenAFS] Problems with Windows XP Home?

[Noel Burton-Krahn]

Yes, my users have had issues with OpenAFS on WinXP too:

1. The computer name is too long.  Make sure the computer name is at most 10
alpha chars.  Its a silly limitation, and OpenAFS should explicitly complain
about it.

2. AFS doesn't announce its netbios name.  It should announce <NAME>-AFS.
If it doesn't, UNC links to AFS documents will time out.  To fix,  add this
to c:/windows/system/drivers/etc:

    127.0.0.1 NAME-AFS #PRE

3. Integrated login always times out and fails, even when "disabled" in the
registry.


Hope that helps

Noel Burton-Krahn
www.bkbox.com





----- Original Message -----
From: "Kevin Coffman" <kwc@citi.umich.edu>
To: <openafs-info@openafs.org>
Sent: Tuesday, September 16, 2003 7:23 AM
Subject: [OpenAFS] Problems with Windows XP Home?


> We have heard reports that some of our users have had problems
> installing the Windows client on XP Home machines; perhaps only on Dell
> laptops.*  This is the OpenAFS 1.2.8 client that we put on our "Blue
> Disk".  Has anyone else experienced trouble with the windows client on
> XP Home?
>
> We recommend that our users use XP Pro, but these were machines
> purchased outside and brought on campus.
>
> * What I have heard is that the users have trouble with the Service
> startup, but XP Home lacks the tools to properly deal with services.
> Booting in safe mode doesn't allow fixing the services, so they face a
> re-install situation.  I don't know more details right now.
>
> Thanks,
> K.C.
>
> _______________________________________________
> OpenAFS-info mailing list
> OpenAFS-info@openafs.org
> https://lists.openafs.org/mailman/listinfo/openafs-info
>
>