Trying to get ka-forwarder to -> fakeka working. Don't want
to run the k5 servers on the AFS db servers if I do not have to.
I am using the latest:
ka-forwarder from OpenAFS 1.4.1
fakeka from MIT KRB 1.4.3
The KRB 1.4.3 setup seems to be working fine. I configured a cell to
use the K5 serv
>My Kerberos REALM name and CELL name our DIFFERENT. I need to do this
>since our Windows group took over our the REALM name that is the same
>as the AFS cell name for their Kerberos system.
Unfortunately, this puts a bit of a crimp in things. But it may not be
your real problem.
You need to hav
If you cheat and tell the client the krb5 server running fakeka is a
dbserver, and kill ka-forwarder, does klog work?
___
OpenAFS-info mailing list
OpenAFS-info@openafs.org
https://lists.openafs.org/mailman/listinfo/openafs-info
On Thursday, June 29, 2006 06:33:29 PM -0400 Derrick J Brashear
<[EMAIL PROTECTED]> wrote:
If you cheat and tell the client the krb5 server running fakeka is a
dbserver, and kill ka-forwarder, does klog work?
For windows clients, the answer is indeed to cheat and tell them the KDC's
are a
>>My Kerberos REALM name and CELL name our DIFFERENT. I need to do this
>>since our Windows group took over our the REALM name that is the same
>>as the AFS cell name for their Kerberos system.
>Unfortunately, this puts a bit of a crimp in things. But it may not be
>your real problem.
>You need
On Thursday, June 29, 2006 03:46:48 PM -0400 Ken Hornstein
<[EMAIL PROTECTED]> wrote:
You're pretty hosed here. ka-forwarder only handles Rx connections. What
the Windows AFS client is doing is trying to talk to Kerberos 4 ports
on the database servers. I think your best bet here is to ge
On Thursday, June 29, 2006 08:08:14 PM -0400 "John W. Sopko Jr."
<[EMAIL PROTECTED]> wrote:
>>My Kerberos REALM name and CELL name our DIFFERENT. I need to do this
>>since our Windows group took over our the REALM name that is the same
>>as the AFS cell name for their Kerberos system.
>
Thanks for the info. I set my encryption type to:
kadmin: cpw -e des-cbc-crc:v4 sopko
which produces the output from kadmin as:
Key: vno 16, DES cbc mode with CRC-32, Version 4
I get a different error on the k5/fakeka server when
trying to do an AFS klog:
Jun 30 08:19:37 kfive fakeka[18668]:
