Re: Windows 10 Pro and openafs client : cannot obtain token

Hi Andreas,

So I uninstalled everything and only installed the Auristor client 
OpenAFS 1.7.3301
As I can see in a cmd with klist I got the kerberos ticket.

aklog -d
outputs
aklog: couldn't determine realm of user: No creadentials cache found

aklog -d -k REALM
ouputs the aklog help message as if there was a error with arguments.

Seems I forgot something...

Another point : no tray icon or or configuration icon in the control 
panel with the auristor package so the only way to see if I have tickets 
is over cmd ?

Thanks
Laurent


Le 17/06/2019 à 12:11, Andreas Ladanyi a écrit :
> Hi Laurent,
>
> i had similar problems in the past.
>
> The "best practise" solutions was to only install the Auristor package
> which delivers also the Heimdal client.
>
> I didnt install the Network ID Manager.
>
>
> To avoid the AFS login failed message (if you will get one in the
> future) after windows restart have a look at this page:
>
> https://www.tenforums.com/tutorials/49963-use-sign-info-auto-finish-after-update-restart-windows-10-a.html
>
>
> Andreas
>
>
>> Hi,
>>
>> I'm facong problems to obtain AFS token on WIndows 10 Pro computer
>> integrated in a Windows Server 2016 domain.
>> Configuration :
>> Windows 10 Pro 1809,
>> Heimdal 7.4.040
>> Netwwork Identity Manager 2.5.0.106
>> OpenAFS 1.7.3301 from Auristor
>>
>>
>> Network Identity Manager obtains kerberos ticket well not the AFS one.
>>
>> aklog -d (in terminal) outputs
>>
>> Authenticating to cell CELLNAME
>> Getting v5 tickets: afs/CELLNAME@REALM
>> aklog: Couldn't get afs/CELLNAME@REALM ticket: Matching credential
>> (afs/CELLNAME@REALM) not found
>>
>> Credentials exists
>> It works perfectly under Windows 7 with both OpenAFS 1.7.3301 and
>> OpenAFS 1.5.99.06 client.
>>
>> Thanks in advance.
>> Laurent
>>


-- 
Laurent STECK Ingenieur systemes
FEMTO-ST (UMR 6174) / SCI
Universite de Franche-Comte - DISC
16 Route de Gray 25030 BESANCON CEDEX
Tel : (0)3 81 66 66 68 Fax : (0)3 81 66 64 50