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

[Holger Brückner]

Hello,

first thanks to all who replied. unfortunately 
rodneys afsk5log and christophers advice to set 
HKLM\SYSTEM\CurrentControlSet\Control\Lsa\Kerberos\Parameters\AllowTgtSessionKey = 1 (REG_DWORD) didn't help.

it seems to me that the root of the problem is an error in the client
configuration. as a user i didn't have a cell configuration. now after
adding this manualy the client isn't showing any file server/volume
server preferences in the configuration tab. it seems like it's not
trying to contact a fileserver at all. (it still works as administrator)

i'll have to dig into this a little bit further. if anybody knows what
to do please reply :)

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