[OpenAFS] Error 11862791

Ezra Keshet Ezra Keshet <keshet@post.harvard.edu>
Tue, 8 Mar 2011 09:22:19 -0800 (PST)


Great.  I will try to get University of Michigan on it.  One more question, 
though, just to double-check: if the Microsoft bug occurs after a network 
change, then why can I not even connect to AFS once, say after I start up the 
computer but before it suspends and disconnects the network?

Best, Ezra


----- Original Message ----
From: Jeffrey Altman <jaltman@secure-endpoints.com>
To: Ezra Keshet <keshet@post.harvard.edu>
Cc: Ezra Keshet <ezrakeshet@yahoo.com>; openafs-info@openafs.org
Sent: Tue, March 8, 2011 12:15:08 PM
Subject: Re: [OpenAFS] Error 11862791

On 3/8/2011 11:11 AM, Ezra Keshet wrote:
>  However, I do not see any obvious network changes in the log file.

I do.

> 3/8/2011 9:09:13 AM: LAN adapter number 4
> 3/8/2011 9:09:13 AM: Using >AFS< as SMB server name
> 3/8/2011 9:09:13 AM: smb_localNamep is >AFS<
> 3/8/2011 9:09:13 AM: Netbios NCBRESET lana 4 succeeded
> 3/8/2011 9:09:13 AM: lana_list.length 1
> 3/8/2011 9:09:16 AM: Netbios NCBADDNAME lana=4 code=0 retcode=0 complete=0
> 3/8/2011 9:09:16 AM: Netbios NCBADDNAME added new name >AFS             <
> 3/8/2011 9:09:16 AM: Netbios NCBADDNAME succeeded on lana 4
> 3/8/2011 9:09:16 AM: smb_NetbiosInit smb_LANadapter=4

Netbios configuration at 9:09:16am and then you shutdown the network at
10:52:57 by suspending the machine.  [Network Change 1]

> 3/8/2011 10:52:57 AM: SERVICE_CONTROL_APMSUSPEND
> 3/8/2011 10:52:57 AM: smb_StopListeners
> 3/8/2011 10:52:57 AM: StopListener: Netbios NCBDELNAME lana=4 code=0 retcode=0 

> complete=0
> 3/8/2011 10:52:57 AM: NCBLISTEN lana=4 failed with NRC_NAMERR.
> 3/8/2011 10:52:57 AM: StopListener: Netbios NCBRESET lana 4 succeeded

Resumed at 11:01:38 which restarts the network [Network Change 2]

> 3/8/2011 11:01:38 AM: SERVICE_CONTROL_APMRESUMEAUTOMATIC
> 3/8/2011 11:01:51 AM: SERVICE_CONTROL_APMRESUMESUSPEND
> 3/8/2011 11:01:52 AM: LAN adapter number 4
> 3/8/2011 11:01:52 AM: Using >AFS< as SMB server name
> 3/8/2011 11:01:52 AM: smb_localNamep is >AFS<
> 3/8/2011 11:01:52 AM: Netbios NCBRESET lana 4 succeeded
> 3/8/2011 11:01:52 AM: lana_list.length 1
> 3/8/2011 11:01:55 AM: Netbios NCBADDNAME lana=4 code=0 retcode=0 complete=0
> 3/8/2011 11:01:55 AM: Netbios NCBADDNAME added new name >AFS             <
> 3/8/2011 11:01:55 AM: Netbios NCBADDNAME succeeded on lana 4
> 
> 3/8/2011 11:01:55 AM: smb_NetbiosInit smb_LANadapter=4
> 3/8/2011 11:01:55 AM: smb_StartListeners
> 3/8/2011 11:01:55 AM: Microsoft SMB Redirector supports Extended Timeouts

Then at 11:02:05 Windows reports another network change [#3]

> 3/8/2011 11:02:05 AM: smb_LanAdapterChange

Followed by another [#4]

> 3/8/2011 11:02:21 AM: smb_LanAdapterChange

at which point the name "AFS" is registered but Microsoft can't find it.
Hence, no access to \\AFS

This is the Microsoft bug.

Jeffrey Altman