[OpenAFS] OpenAFS 1.5.78 on Windows 7 (64 bit), system error 5

David Bear David.Bear@asu.edu
Mon, 31 Jan 2011 08:29:49 -0700


--0016e65a0d5c26d6c0049b26162b
Content-Type: text/plain; charset=UTF-8

On Mon, Jan 31, 2011 at 8:17 AM, Jeffrey Altman <
jaltman@secure-endpoints.com> wrote:

> On 1/31/2011 10:13 AM, David Bear wrote:
> > Just to echo what Jeff Altman has already mentioned, check to make sure
> > that the afs loopback adapter has been installed and that the afs name
> > is bound to that interface. This loopback adapter should have the
> > address of 10.254.254.252. If your machine is finding another machine on
> > the network named \\afs -- that machine also should be checked to make
> > sure the loopback adapter is installed and configured.
>
> An OpenAFS client will not publish the name "AFS" on a non-loopback
> adapter.  If there is a machine on the network with the name "AFS" that
> will be either the configured short name of the machine or the name of a
> machine registered in DNS with a domain matching one of the domains in
> the DNS domain search list.
>
> Thanks. This is good to know. Is this new behavior? (relatively new) On
older clients we did see AFS registering this name on a public interface. In
our highly segmented/subnetted network, it was very difficult to track down
the offender sometime.



> Jeffrey Altman
>
>


-- 
David Bear
College of Public Programs at ASU
602-494-0424

--0016e65a0d5c26d6c0049b26162b
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div class=3D"gmail_quote">On Mon, Jan 31, 2011 at 8:17 AM, Jeffrey Altman =
<span dir=3D"ltr">&lt;<a href=3D"mailto:jaltman@secure-endpoints.com">jaltm=
an@secure-endpoints.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail=
_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:=
1ex;">
<div class=3D"im">On 1/31/2011 10:13 AM, David Bear wrote:<br>
&gt; Just to echo what Jeff Altman has already mentioned, check to make sur=
e<br>
&gt; that the afs loopback adapter has been installed and that the afs name=
<br>
&gt; is bound to that interface. This loopback adapter should have the<br>
&gt; address of 10.254.254.252. If your machine is finding another machine =
on<br>
&gt; the network named \\afs -- that machine also should be checked to make=
<br>
&gt; sure the loopback adapter is installed and configured.<br>
<br>
</div>An OpenAFS client will not publish the name &quot;AFS&quot; on a non-=
loopback<br>
adapter. =C2=A0If there is a machine on the network with the name &quot;AFS=
&quot; that<br>
will be either the configured short name of the machine or the name of a<br=
>
machine registered in DNS with a domain matching one of the domains in<br>
the DNS domain search list.<br>
<font color=3D"#888888"><br></font></blockquote><div>Thanks. This is good t=
o know. Is this new behavior? (relatively new) On older clients we did see =
AFS registering this name on a public interface. In our highly segmented/su=
bnetted network, it was very difficult to track down the offender sometime.=
</div>
<div><br></div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"=
margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><font color=
=3D"#888888">
Jeffrey Altman<br>
<br>
</font></blockquote></div><br><br clear=3D"all"><br>-- <br>David Bear<br>Co=
llege of Public Programs at ASU<br>602-494-0424<br>

--0016e65a0d5c26d6c0049b26162b--