Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 107718 - samba-3.0.14a strange behvaiour
Summary: samba-3.0.14a strange behvaiour
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Gentoo Linux bug wranglers
Depends on:
Reported: 2005-09-30 09:22 UTC by barthek
Modified: 2005-10-04 04:37 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Note You need to log in before you can comment on or make changes to this bug.
Description barthek 2005-09-30 09:22:03 UTC
i have this strange behaviour of samba 3.0.14
i can set it to either of two:

1. 'wbinfo -u' and user authentication to domain works
flawlessly BUT authentication of domain users locally mapped does not
2. 'wbinfo -u' does not work, auth of domain users does not work, but auth of
domain users who are mapped locally works

if i do a 'reset account' on PDC, then condition 2 occurs.
if i then do net join - condition 1 occurs.

is just samba a piece of crap or am i doing something wrong? :)

my smb.conf:

        dos charset = 852
        unix charset = ISO8859-2
        display charset = ISO8859-2
        workgroup = PWDNT
        security = DOMAIN
        map to guest = Bad User
        password server = PWDNTPRIMARY
        username map = /etc/samba/smbusers
        log level = 2
        log file = /var/log/samba/log.%m
        max log size = 50
        max open files = 1000
        socket options = TCP_NODELAY SO_RCVBUF=32768 SO_SNDBUF=32768
        load printers = No
        idmap uid = 45000-60000
        idmap gid = 45000-60000
        comment = Linux Samba server
        hosts allow = XXX
        case sensitive = No
Comment 1 Jakub Moc (RETIRED) gentoo-dev 2005-09-30 09:41:05 UTC
This is not a bug but a help request; that's not what bugzilla is for. Use to ask questions. 
Comment 2 barthek 2005-10-04 04:37:42 UTC
a help request???

this is a bug in samba itself
and i guess samba developers thought so - they fixed it.

samba 3.0.20a works flawlessly