From: Richard Smits <R.Smits@tudelft.nl>
To: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: gssd mounts not working
Date: Thu, 21 Apr 2011 08:58:57 +0200 [thread overview]
Message-ID: <4DAFD5B1.9060004@tudelft.nl> (raw)
Hello,
We are having problems with our gssd nfs mounts. I will explain our
situation.
Our clients are running SLED 11 SP1.
Our server is a Netapp filer with Ontap 7.3.3P4.
We provide NFS exported directory's with krb5 security.
Our KDC is a Windows 2003 and 2008 Active Directory.
If we use nfs-client-1.2.1-8.1 everything works as expected.
But if we upgrade to (any) newer client, all gssd mounts fail. Now there
is a bugreport on Novell Bugzilla about this :
https://bugzilla.novell.com/show_bug.cgi?id=614293#c7
Apperantly if the nfs client is compiled with --disable-tirpc , the
ticket size from the AD is to big ?
On our Redhat server we do not have these problems. There we are running
: nfs-utils-1.2.2-7
Is there an explanation for these problems ? How can i find out if a
client has been compiled with specific options. There is no nfs devel
package for suse.
Greetings .. Richard Smits
next reply other threads:[~2011-04-21 6:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-21 6:58 Richard Smits [this message]
2011-04-23 12:16 ` gssd mounts not working Steve Dickson
2011-04-23 17:00 ` Luk Claes
2011-04-23 17:47 ` Steve Dickson
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=4DAFD5B1.9060004@tudelft.nl \
--to=r.smits@tudelft.nl \
--cc=linux-nfs@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.