[OpenAFS] Win XP afsd_service crashes

Thu, 22 Apr 2004 12:43:53 -0400

This is a multi-part message in MIME format.
--------------050504090704000001090808
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Examine the %WINDIR%\TEMP\afsd_init.log file to see which adapter
the afsd_service.exe is binding to.  If it is not the MS Loopback
adapter, fix the configuration to use "auto" instead of a fixed
adapter number.

Failing to specify a static address to the loopback adapter
may very well be the problem if the wireless adapter is assigned
an address by DHCP faster than it takes the loopback adapter to
timeout and choose 169.x.y.z address.

Jeffrey Altman

Joe Buehler wrote:

> I have a user who has several adapters on his laptop.
> The only active one is a wireless adapter.  It comes up
> when he logs in.  The April 17 build of the windows client
> crashes, I assume because of the network adapter configuration.
>
> I added the microsoft loopback adapter to give afsd_service.exe
> something more stable to bind to, but this didn't help.  One thing
> I have not tried yet is a static address on the loopback.
>
> Any suggestions?

--------------050504090704000001090808
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
 <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
 <title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Examine the %WINDIR%\TEMP\afsd_init.log file to see which adapter 
the afsd_service.exe is binding to.&nbsp; If it is not the MS Loopback 
adapter, fix the configuration to use "auto" instead of a fixed 
adapter number. 
 
Failing to specify a static address to the loopback adapter 
may very well be the problem if the wireless adapter is assigned 
an address by DHCP faster than it takes the loopback adapter to 
timeout and choose 169.x.y.z address. 
 
Jeffrey Altman 
 
 
Joe Buehler wrote:
<blockquote cite="midc662g8$mq0$1@sea.gmane.org" type="cite">I have a user who has several adapters on
his laptop.
 
The only active one is a wireless adapter.&nbsp; It comes up
 
when he logs in.&nbsp; The April 17 build of the windows client
 
crashes, I assume because of the network adapter configuration.
 
 
I added the microsoft loopback adapter to give afsd_service.exe
 
something more stable to bind to, but this didn't help.&nbsp; One thing
 
I have not tried yet is a static address on the loopback.
 
 
Any suggestions?
 
 
</blockquote>
</body>
</html>

--------------050504090704000001090808--