[OpenAFS] Re: Weird LAN/WAN login problem

[Andrew Deason]

On Mon, 25 Feb 2013 22:35:09 +0200 (EET)
jukka.tuominen@finndesign.fi wrote:

> Any particular log you have in mind?

No, I don't know if any log provides the error I was looking for. I
intended for you to run ls, which you did, so thanks!

> In Nautilus (file manager), it doesn't give any error message. It behaves
> as if the parent directory is empty. On command line,
> 
> $ls >> cannot access [directory name]. Connection timed out
> $cd [directory name] >> Connection timed out
> 
> The time out happends immediately, BTW.

Okay, good. One possibility here is that the fileserver for userB is not
accessible over the network from the WAN network. Do you see any
messages from 'afs: ' in kern.log or `dmesg`?

Do you know if the volume for the homedir of user B is on a different
fileserver than user A? You can check where they are with 'vos listvldb
<volume.name>'. If you don't happen to know the volume name, you can 'fs
lsmount /afs/cell/user/userA' (or whatever), or run 'fs lq /path/to/dir'
from a client that is able to access both directories.

If they are on different fileservers, you may want to see if you can
access the userB fileserver at all. You can list other volumes that are
on that fileserver with 'vos listvldb -server serverB', and try to
access those. Or you can try a basic connectivity test (analagous to a
'ping') to the fileserver by running 'rxdebug serverB -version' from the
client machine on the WAN.

-- 
Andrew Deason
adeason@sinenomine.net