Bug 168105 - Bad: Authentication against Active Directory doesnt work
Summary: Bad: Authentication against Active Directory doesnt work
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: samba
Version: 4.0
Hardware: powerpc
OS: Linux
Target Milestone: ---
: ---
Assignee: Simo Sorce
QA Contact: David Lawrence
Keywords: EasyFix
Depends On:
TreeView+ depends on / blocked
Reported: 2005-09-12 14:28 UTC by Michael Lang
Modified: 2007-11-30 22:07 UTC (History)
1 user (show)

Clone Of:
Last Closed: 2007-11-21 23:58:55 UTC

Attachments (Terms of Use)

Description Michael Lang 2005-09-12 14:28:21 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6) Gecko/20050317 Firefox/1.0.1

Description of problem:
Authentication against Active Directory doesnt work as expected.
using wbinfo -u lists all Users from the Domain where getent passwd 
just returns one Accout (usualy Administrator) and nothing else except :0::::
The winbindd Logs reports problems with the uid/gid numbers 
 "idmap Fatal Error: UID range full!! (max: 20000)"

I did first blame M$ as it seems to be the License of the SBS Server
i was trying to authenticate against, since authentication against AD on
x86 on another Site/AD worked fine with samba*-3.0.10-1.4E.

My colleague setup authentication using SUSE EL9 which work fine without
any problems. If then tryed to recompile samba-*3.0.14a-2 on the PPC System
and after upgrading it worked fine.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.Install EL4 on PPC samba Version samba*-3.0.10-1.4E.
2.Setup AD Authentication for Samba
3.try wbinfo -u and getent passwd

Actual Results:  \uffffPPERICOM+administrator::0:100000:::

Expected Results:  PERICOM+administrator:*:10000:10000:Administrator:/home/PERICOM/administrator:/bin/false

Additional info:

fixed by upgrading samba to version samba-3.0.14a-2

Comment 1 Simo Sorce 2007-11-21 23:58:55 UTC
I am closing this as we released 3.0.25 and that should cover this issue as well.
Reopen if not.

Note You need to log in before you can comment on or make changes to this bug.