Figured it out. Was a hostname /host principal issue. On Tue, 2002-04-23 at 14:08, Austin Gonyou wrote: > I've recently setup kpropd through xinetd on a slave kdc. That works > fine, but is incorrect as far as the FS layout is concerned. > > I've opted to use kpropd in stand alone mode on 3 different ports, 754, > 755, 756 on the slave, and that part seems to be working fine. > > When I attempt to run kprop from the master KDC, I get the following: > <error> > Generic remote error: Wrong principal in request > </error> > > I'm currently running 1.2.2. I know the logging has changed in 1.2.3 and > up, but I must work with what I have for now to ensure it's completely > documented so I can document what it changes in our environment when we > go up to 1.2.4 or 1.2.5. > > TIA. > -- > Austin Gonyou > Systems Architect, CCNA > Coremetrics, Inc. > Phone: 512-698-7250 > email: [EMAIL PROTECTED] > > "It is the part of a good shepherd to shear his flock, not to skin it." > Latin Proverb -- Austin Gonyou Systems Architect, CCNA Coremetrics, Inc. Phone: 512-698-7250 email: [EMAIL PROTECTED]
"It is the part of a good shepherd to shear his flock, not to skin it." Latin Proverb
signature.asc
Description: This is a digitally signed message part
