On 1/31/2011 10:29 AM, David Bear wrote:
> 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.
I
On Mon, Jan 31, 2011 at 8:17 AM, Jeffrey Altman <
jalt...@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 t
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 machin
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
Access Denied on \\AFS would imply that there is an actual machine
on the network called AFS
On 1/28/2011 3:32 PM, John Tang Boyland wrote:
> Another semester and more Windows 7 problems. These are all problems
> that happen even after a reboot. Today's flavor:
>
> Network Identity Manager can
Another semester and more Windows 7 problems. These are all problems
that happen even after a reboot. Today's flavor:
Network Identity Manager can get kerberos tickets but not AFS tickets.
There's a long pause and then it says it couldn't get tickets.
On the Network and Sharing Center Control P
