Harald Barth wrote:

>>I will try to answer the easy questions first.  To obtain the UUID of a
>>client you can use:
>>
>>[\\afs\asanka\Public\khimaira\bin]cmdebug localhost -addr
>>UUID: 736f2aae-419b-4174-8472-8ecc530b52d3
>>Host interfaces:
>>192.168.1.11, netmask 255.255.255.0, MTU 1260
>>192.168.182.1, netmask 255.255.255.0, MTU 1260
>>192.168.23.1, netmask 255.255.255.0, MTU 1260
>>Capabilities:
>>Error Translation
> 
> 
> First I was puzzled:
> 
> habarber:~$ /usr/openafs/bin/cmdebug localhost 7001 -addr       
> Host interfaces:
> 130.237.234.196, netmask 255.255.255.0, MTU 1500
> 
> No UUID here ... seems the WIN edition has some extra
> features. Is it neccessary to have different cmdebugs
> for WIN and the rest?

There is no specific reason.   Windows has its own version of many of
the utility functions.

> I still see
> 
> Mon Oct 24 10:17:15 2005 ProbeUuid failed for host 130.237.237.21:7001
> Mon Oct 24 11:17:08 2005 CB: WhoAreYou failed for 130.237.237.21:7001, error 
> -01
> 
> in the log. 

Which indicates that either the client is not on the network or behind a
firewall/NAT.

Jeffrey Altman


Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Reply via email to