[OpenAFS] Re: RPC service unavailable, windows client, udebug works

[Christian]

Am 05.11.2014 22:24, schrieb Jeffrey Altman:
> On 11/5/2014 4:10 PM, Christian wrote:
>> This is the result of
>> udebug 130.75.103.223 7000
>> on the client, which fails with
>> "return code -2 from VOTE_debug"
>>
> 
> udebug will not work against port 7000 since the File Server is not a
> UBIK service.
> 
> The UBIK services are VL (7003), PT (7002), ...

Sorry. Noticed that just after the email went out. rxdebug
130.75.103.223 works just fine from the client. So now I am trying

tcpdump -n host 130.75.103.223 and host 130.75.102.221 and udp

both on the client or on the server. When I click on one of the
directories which reside on volumes on 130.75.103.223, I get the "RPC..
message " again, but I do not capture any traffic on the client. If I do
a "fs checkservers" on the client, I capture on the client:

22:43:40.811047 IP 130.75.102.221.7001 > 130.75.103.223.7003:  rx data
vldb call probe (32)
22:43:40.817684 IP 130.75.103.223.7003 > 130.75.102.221.7001:  rx data
vldb reply probe (28)
22:43:40.817808 IP 130.75.102.221.7001 > 130.75.103.223.7003:  rx ack
first 2 serial 0 reason delay (65)

and on the server:
22:43:40.895858 IP 130.75.102.221.7001 > 130.75.103.223.7003:  rx data
vldb call probe (32)
22:43:40.896015 IP 130.75.103.223.7003 > 130.75.102.221.7001:  rx data
vldb reply probe (28)
22:43:40.900661 IP 130.75.102.221.7001 > 130.75.103.223.7003:  rx ack
first 2 serial 0 reason delay (65)

Thanks,

Christian