Bug 167735

Summary:	net-fs/samba-3.0.24 fails to authenticate via PDC
Product:	Gentoo Linux	Reporter:	Richard Scott <gentoo.bugs>
Component:	New packages	Assignee:	Gentoo's SAMBA Team <samba>
Status:	RESOLVED INVALID
Severity:	major	CC:	chris
Priority:	High
Version:	unspecified
Hardware:	x86
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

Description Richard Scott 2007-02-20 11:42:54 UTC

I have a samba server that is a member of an NT domain. 

With 3.0.22-r3 I can provide authentication via the PDC, but with 3.0.24 this *always* fails. 



Reproducible: Always

Steps to Reproduce:
1.install samba, add it to the NT domain.
2.setup a share
3.try to access the share

Actual Results:  
the share requires authentication and no matter what details you provide it will always fail.

Expected Results:  
authenticated access to the share in question.

If you downgrade to v3.0.22-r3 using the exact same config files etc it all works ok.

# emerge --info
Portage 2.1.2-r9 (hardened/x86/2.6, gcc-3.4.6, glibc-2.3.6-r5, 2.6.18-hardened i686)
=================================================================
System uname: 2.6.18-hardened i686 VIA Nehemiah
Gentoo Base System release 1.12.9
Timestamp of tree: Tue, 20 Feb 2007 00:50:01 +0000
distcc 2.18.3 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [disabled]
ccache version 2.4 [disabled]
dev-java/java-config: 1.3.7, 2.0.31
dev-lang/python:     2.3.5-r3, 2.4.3-r4
dev-python/pycrypto: 2.0.1-r5
dev-util/ccache:     2.4-r6
sys-apps/sandbox:    1.2.17
sys-devel/autoconf:  2.13, 2.60
sys-devel/automake:  1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 1.10
sys-devel/binutils:  2.16.1-r3
sys-devel/gcc-config: 1.3.14
sys-devel/libtool:   1.5.22
virtual/os-headers:  2.6.17-r2
ACCEPT_KEYWORDS="x86"
AUTOCLEAN="yes"
CBUILD="i686-pc-linux-gnu"
CFLAGS="-mtune=i686 -O -pipe -fomit-frame-pointer"
CHOST="i686-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/bind /var/service"
CONFIG_PROTECT_MASK="/etc/env.d /etc/env.d/java/ /etc/gconf /etc/java-config/vms/ /etc/revdep-rebuild /etc/terminfo"
CXXFLAGS="-mtune=i686 -O -pipe -fomit-frame-pointer"
DISTDIR="/usr/portage/distfiles"
EMERGE_DEFAULT_OPTS="--alphabetical"
FEATURES="autoconfig distlocks metadata-transfer parallel-fetch sandbox sfperms strict"
GENTOO_MIRRORS="http://adelie.polymtl.ca/"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --delete-after --stats --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/opt/portage"
SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage"
USE="acl apache2 berkdb bzip2 crypt curl dlloader gdbm gmp hardened idn jpeg midi mysql ncurses nls nptl nptlonly pam perl php pic python readline samba snmp ssl tcpd usb x86 xorg zlib" ALSA_PCM_PLUGINS="adpcm alaw asym copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa lfloat linear meter mulaw multi null plug rate route share shm softvol" ELIBC="glibc" INPUT_DEVICES="keyboard mouse" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" USERLAND="GNU" VIDEO_CARDS="via s3 vesa"
Unset:  CTARGET, INSTALL_MASK, LANG, LC_ALL, LDFLAGS, LINGUAS, PORTAGE_RSYNC_EXTRA_OPTS

Comment 1 Chris Smith 2007-02-22 16:13:56 UTC

No bug, user configuration error.
RTFM
Hint: Release Notes for Samba (somewhere between 3.0.24 and 2.0.23 you will find the answer - "the exact same config files" are a problem).

Comment 2 Richard Scott 2007-02-22 18:32:14 UTC

ok, I've been reading this:

http://www.samba.org/samba/history/samba-3.0.23.html

If it was something to do with the User and Group changes then I didn't understand a word of it...or what to do to fix my problem :-(

Any chance of another hint? ;-)

Comment 3 Chris Smith 2007-02-22 18:56:54 UTC

(In reply to comment #2)
> ok, I've been reading this:
> 
> http://www.samba.org/samba/history/samba-3.0.23.html

You should really make this a forum post (or just read the Samba mailling list archives) for help, since this is not a bug.

But I have to wonder why you think the answer might be in the above document? You're seeing the issue with 3.0.24, not 3.0.23. And the area where the answer lies has already been pointed out to be post 3.0.23.