healthy installation on os x does not connect at some locations
Anton Grigoriev
tfsangr at fy.chalmers.se
Mon Oct 9 12:32:25 CEST 2006
Thank you for this info. Now I understand. However, this
functionality is not critical - I mostly need to read the data after
my calculations.
As for the situation with the error
/usr/arla/bin/rxdebug lise(anna,sculpin).pdc.kth.se 7000 -version
Trying 194.132.193.217 (port 7000):
get version call failed with code -1, errno 0
how the outward connection can be firewalled? I am sure now that the
laptops are still otside of the department firewall, but the
university firewall allows the afs traffic. It migh be not possible
to find the intermediate misconfigured link.
Is there any way to tunnel the afs connection? Like ssh tunnel.
I always get an error like
failed for listen port 7000
or
cannot listen to port: 7000
Sincerely
Anton
On Oct 4, 2006, at 10:27, Tomas Olsson wrote:
> Anton Grigoriev <tfsangr at fy.chalmers.se> writes:
>> Meanwhile, I found that the presence of the client connection from
>> pdc to my Mac:7001 does not affect the work of arla afs. I made a NAT
>> rule at home and opened OS X to listen on 7001, so that /usr/openafs/
>> sbin/rxdebug from pdc sees my Mac. I found that nothing changed in my
>> (working) afs connection.
>>
> 7001 is used by the server to notify the client about any changes
> made on
> other hosts. Do 'ls' on some directory from your client, add a
> file to it
> on some pdc host, and then do ls locally again. If the file is
> visible, you
> probably have working callbacks.
>
> For changes you do on your mac, you will always see them since your
> client
> already knows about them. And the pdc hosts do have full
> connectivity and
> working callbacks, so it will be visible there, too.
>
> /t
More information about the Arla-drinkers
mailing list