Has anyone managed to get krb5-1.4.3 to compile on Solaris 8?
My compile fails because it can't find freeifaddrs or getifaddrs, using gcc.
[]
making all in lib/rpc/unit-test...
gmake[3]: Entering directory
`/var/tmp/sambastuff/krb5-1.4.3/src/lib/rpc/unit-test'
gcc -L../../../lib
Worth noting: The 3.0.x recommendation regarding nscd is that you /do
not run it at all/. Though I think that might only apply when you're
using winbindd, you might want to take a look at your nscd process to
see if it's notably busy. It was on our server, taking up half of one
of the CPUs.
Michael Wray wrote:
Help,
wbinfo -t fails with the error in subject, and getting sids of groups that
aren't BUILTIN fail. Everything else seems to work. Note: I am not
converting my kerberos tickets to krb4, is this necessary? (It used to work
without it..but now it seems not to work.) I get
Alexander Lazarevich wrote:
Hi,
samba-3.0.9-1.3E.2 on RHEL3-AS.
Let's say we have a samba 3 PDC (workgroup = testdomain) on
linux.host.1, and the passwd backend is NIS ypbind that binds to
ypserv on liunx.host.2. Further, linux.host.2 also runs samba 3, not
as a PDC, but rather points it's
Samba 3.0.4 // Solaris 8
I saw this behavior as well, when doing wbinfo -u or -g, when I had
winbind default domain = yes in my smb.conf file. If you comment that
out, then restart winbind, you should see your domain in wbinfo -u and
-g. For me, getent still returns my NIS entries only, but I
I installed Samba recently on a ClearCase server (Solaris 8) to remove
the need for DiskAccess on the Windows clients. I'm having two problems
with it, actually. The important one that I'm asking the list about is
that Samba is hammering my NIS master with requests for DoMaiN+UseR (and
every
I'm seeing this problem as well, and while our Windows servers are using
Active Directory, my samba configuration is employing the server =
domain technique, and the password server is the one Windows AD DC
that's in NT emulation mode.
Authentications seem to work okay, and users can navigate
For historical reasons, the administrator is member in lots of groups. As
a result the ticket size is too big for UDB, so the W2k3-server sends an
KRB5KRB_ERR_RESPONSE_TOO_BIG (Response too big for UDP, retry with TCP)
error back to kinit.
Unfortunatly this case is not handled in
