From: Martijn de Gouw <martijn.de.gouw@prodrive-technologies.com>
To: "linux-cifs@vger.kernel.org" <linux-cifs@vger.kernel.org>
Subject: cifs.upcall requests ticket for wrong host when using dfs
Date: Fri, 3 Jan 2020 14:11:23 +0000 [thread overview]
Message-ID: <39643d7d-2abb-14d3-ced6-c394fab9a777@prodrive-technologies.com> (raw)
Hi,
I'm trying to switch from ntlpssp to kerbebos for mounting our dfs
shares. It seems to work, but only for 'older' kernel versions. Since we
are running debian 9 and 10, I'm testing this for both version. The
thing is that is seems to work when I run kernel 4.19.67, but not when
I'm running kernel 5.3.9.
What I'm trying to do:
mount -t cifs //domain.com/common /mnt/common -o
rw,vers=3.0,sec=krb5,cruid=10003,username=mdg,uid=10003,gid=10276,addr=10.1.1.14,file_mode=0600,dir_mode=0700,nobrl,nohandlecache,user=mdg
So far it works fine on 4.19, but not on 5.3. Because when I try to
travel into the directories (which are actually dfs pointers to the NAS
shares) I get permission denied.
So far, I was able to track this down to cifs.upcall, because on kernel
4.19 I see it tries to get a service ticket for the nas (cifs.upcall:
handle_krb5_mech: getting service ticket for nas01.domain.com). But on
kernel 5.3 it tries to get a ticket for the dc again: cifs.upcall:
handle_krb5_mech: getting service ticket for dc01.domain.com.
What could be wrong here?
--
Martijn de Gouw
Designer
Prodrive Technologies
Mobile: +31 63 17 76 161
Phone: +31 40 26 76 200
next reply other threads:[~2020-01-03 14:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-03 14:11 Martijn de Gouw [this message]
[not found] ` <87png0boej.fsf@cjr.nz>
2020-01-03 16:30 ` cifs.upcall requests ticket for wrong host when using dfs Martijn de Gouw
2020-01-03 20:14 ` Paulo Alcantara
2020-01-06 15:07 ` Martijn de Gouw
2020-01-06 23:30 ` Paulo Alcantara
2020-01-07 16:13 ` Martijn de Gouw
2020-01-08 17:46 ` Paulo Alcantara
2020-01-09 12:27 ` Martijn de Gouw
2020-01-09 13:06 ` Paulo Alcantara
2020-01-30 17:46 ` Jacob Shivers
2020-01-30 18:55 ` Steve French
2020-01-30 19:06 ` Jacob Shivers
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=39643d7d-2abb-14d3-ced6-c394fab9a777@prodrive-technologies.com \
--to=martijn.de.gouw@prodrive-technologies.com \
--cc=linux-cifs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).