SOLVED: Re: Can not mount AD share with Kerberos ticket: mount error 126 = Required key not available
Robert Euhus <[email protected]>
| Newsgroups | gmane.linux.file-systems.cifs |
|---|---|
| Message-ID | <[email protected]> |
Jeff Layton schrieb: > On Fri, 11 Sep 2009 14:49:04 +0200 > Robert Euhus <[email protected]> wrote: > Hello, >> >> [..] > > ...nope, according to the above info, cifs.upcall is going to attempt > to get a service principal of: > > host/[email protected] > > ...before connecting to the server. That's failing for some reason. In > general with krb5 you'll want to use the canonical hostname of the > server when mounting as that's the name most likely to be used in > service principals. This brought me on the right track: doing a klist on a Windows client showed me that the KDC only has a service principal for host/[email protected] not for host/[email protected] which doesn't look right to me. But using /sbin/mount.cifs //dc1.workgroup.intern/homes .workgroup/homes/ -o sec=krb5i,guest works now. Thank you very much! Cheers, Robert.