[OpenAFS] (Update) aklog/wake on Windows 2003 Terminal Server ?

Holger Brückner lists@net-labs.de
17 Dec 2003 14:50:17 +0100


first good news, today i got it working. i never would have found a
solution if the same symptom wouldn't have occured on my w2k
workstation. (client 1.2.10) 

i had to remove 

(this key was added using 
 addprinc -randkey -e des-cbc-crc:normal cifs/WTS-AFS@NET-LABS.LOCAL )

from the kdc. now i get "Server not found ind Kerberos database"
messages. but the client is working ok, and i can get afs tokens using
mit aklog.exe or wake.

if i add the key to the kdc and logon to windows the client won't show
any volume/fileservers in it's preferences tab under client

could someone explain this behaviour ?!?

thanks to anyone who helped

Holger Brueckner
net-labs Systemhaus GmbH

On Fri, 2003-12-05 at 17:04, Holger Brückner wrote:
> Hello,
> i'm trying to run the openafs 1.2.10 client under windows 2003 terminal
> server. i already read about serveral problems regarding tokens nad
> drive mappings ... but that is another problem.
> i can login with a trust on a mit server and succesfully get the krbtgt
> ticket for a user account. the ticket is copied to the mit cache via
> ms2mit/wake. unfortunately aklog won't work then. no debug output at
> all. it just does nothing. no request for the afs ticket in the kdc
> logs. it works with the administrator account though.
> any hints why aklog could behave like this ?
> thanks
> Holger Brueckner
> net-labs Systemhaus GmbH
> _______________________________________________
> OpenAFS-info mailing list
> OpenAFS-info@openafs.org
> https://lists.openafs.org/mailman/listinfo/openafs-info