On Mon, Jan 31, 2011 at 8:17 AM, Jeffrey Altman < [email protected]> 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
