[OpenAFS] AFS access at home

Brian Cashman bsc@merit.edu
Thu, 03 Apr 2003 09:01:34 -0500


No, I'm not on dialup but on a cable modem so it's an Ethernet NIC.

I've turned off my firewall and I don't use NAT. I don't believe the 
connection is unstable because as I mention below it works fine under a 
different set of circumstances.

If this just plain didn't work then I'd resign myself to a fundamental 
issue of it not working when I'm technically not on the domain. But, it 
works for me at home when I login to my workstation directly (and not 
into the domain). Same NIC, etc. When it works it even works with my 
firewall turned on.

I'm guessing that there seems to be something about logging into the 
domain remotely that leaves AFS in some sort of incomplete state. When I 
login to the domain at home I believe I don't really log in but I'm 
allowed to login due to caching of my previously successful login. At 
home I get the following event:

No Windows NT or Windows 2000 Domain Controller is available for domain 
MERIT. The following error occurred:
There are currently no logon servers available to service the logon 
request.

Something about this (I believe) makes me unable later to acquire 
tokens. But, as I said, if I login to the workstation directly I am able 
to get tokens. It seems to me that if the local direct login works then 
so should the domain login.

Lastly, I should repeat that at work, on my local network, AFS works 
just fine with no other changes.

Thanks for your response.

      Brian Cashman

Rubino Geiß wrote:
> Hi,
> 
> 
>>The AFS client was unable to obtain tokens as bsc in cell.merit.net.
>>Error: 11862791 (AFS service may not have started)
> 
> 
> How do you connect to the internet (at home)? I suspect that you are using
> dialup? This won’t work on most occasions, because AFS seems only to be able
> to use (bind to) "real" network interfaces. Our solution for people seeing
> this is to use a dummy network interface connecting to localhost...
> 
> You should also consider: NAT, Firewalling and unstable connection issues.
> 
> Bye, Ruby
>