I've run into a situation with DECathena where I cannot attach filesystems
on my master server because of an authentication problem. If for example,
I type
attach huhman
I get back the message
attach: Authentication failed to host WDEE1.EE.DEERE.COM for filesystem huhman
if I turn on the debug swirch as follows
attach -d huhman
I get back
huhman resolves to:
NFS /lockers/huhman WDEE1.EE.DEERE.COM. w /lockers/huhman
Locking attachtab....Setting lock on /tmp/attach_huhman: 5
Unlocking attachtab
Processing line NFS /lockers/huhman WDEE1.EE.DEERE.COM. w /lockers/huhman
Mountpoint canonicalized as: /lockers/huhman
nfsid operation on 192.43.12.251, op = 7
nfsid operation requiring authentication...op = 7
krb_mk_req for instance wdee1, realm EE.DEERE.COM
Getting RPC handle for 192.43.12.251
Adding cache entry with FD = 4
attach: Authentication failed to host WDEE1.EE.DEERE.COM for filesystem huhman
RPC return status: RPC: Authentication error; why = Client credential too weak
Locking attachtn
nfsid operation on 192.43.12.251, op = 7
nfsid operation requiring authentication...op = 7
krb_mk_req for instance wdee1, realm EE.DEERE.COM
Getting RPC handle for 192.43.12.251
Adding cache entry with FD = 4
attach: Authentication failed to host WDEE1.EE.DEERE.COM for filesystem huhman
RPC return status: RPC: Authentication error; why = Client credential too weak
Locking attachtab....Removing lock on /tmp/attach_huhman
Unlocking attachtab
If anyone knows what a client credentials too weak message means, I would
surely appreciate an assist. I've attempted numerous fixes, including
paring down my name serving scheme, rebuilding the credentials database
(/etc/srvtab), shutting down the secondary kerberos server I had, shutting down
and rebooting the entire kerberos installation, and even the ritual chants I
reserve for times suxch as these.
Thanks in advance
Stan Huhman
John Deere Engine Works
Waterloo, Iowa 50701
319 292 8687
Received on Sun Oct 01 1995 - 14:31:16 NZDT