similar to: [ANNOUNCE] Samba 3.3.0pre2 Available for Download

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Release Announcements ===================== This is the first release candidate of Samba 3.3.0. This is *not* intended for production environments and is designed for testing purposes only. Please report any defects via the Samba bug reporting system at https://bugzilla.samba.org/. Major enhancements in Samba 3.3.0 include:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Release Announcements ===================== This is the first release candidate of Samba 3.3.0. This is *not* intended for production environments and is designed for testing purposes only. Please report any defects via the Samba bug reporting system at https://bugzilla.samba.org/. Major enhancements in Samba 3.3.0 include:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Release Announcements ===================== This is the second release candidate of Samba 3.3.0. This is *not* intended for production environments and is designed for testing purposes only. Please report any defects via the Samba bug reporting system at https://bugzilla.samba.org/. Major enhancements in Samba 3.3.0 include:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Release Announcements ===================== This is the second release candidate of Samba 3.3.0. This is *not* intended for production environments and is designed for testing purposes only. Please report any defects via the Samba bug reporting system at https://bugzilla.samba.org/. Major enhancements in Samba 3.3.0 include:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ================================================================ "After all, computers crash, people die, relationships fall apart. The best we can do is breath and reboot." Sarah Jessica Parker ================================================================ Release Announcements ===================== This is the first

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ================================================================ "After all, computers crash, people die, relationships fall apart. The best we can do is breath and reboot." Sarah Jessica Parker ================================================================ Release Announcements ===================== This is the first

Hi Guys, I'm having problems getting the new idmap_adex module to work. When using the idmap_adex plugin I get the following: # wbinfo -n administrator S-1-5-21-XXXXXXXXX-XXXXXXXXXX-XXXXXXXXXX-500 User (1) # wbinfo -i administrator Could not get info for user administrator As expected attempting to lookup user & group info via commands which use libnss also fail. The

Hi, I'm trying to integrate an existing linux environment with a Windows AD environment. All my users are already in AD with valid rfc2307 attributes defined so I need a way to authenticate my users using username, uid, gid, shell and homedirectory from AD. I've been using Kerberos+LDAPs before but that requires a dummy AD user hardcoded with username and password in /etc/ldap.conf

We have Windows 2008R2 domain controllers running 2003 functional level with SFU (i think thats what its called, im not the windows admin :p ) . With Winbind 3.0.33 (on Redhat 5.5) I can get the UIDs/GIDs from AD without issue using: idmap config DOMAIN:backend = ad idmap config DOMAIN:default = yes idmap config DOMAIN:schema_mode = rfc2307 idmap config DOMAIN:range = 10000 - 30000

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 =============================================================== "It is only with one''s heart that one can see clearly. What is essential is invisible to the eye." Antoine de Saint-Exupéry =============================================================== Release Announcements ===================== This is a bug

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 =============================================================== "It is only with one''s heart that one can see clearly. What is essential is invisible to the eye." Antoine de Saint-Exupéry =============================================================== Release Announcements ===================== This is a bug

We are in an environment where several AD domains are being consolidated into one larger domain using sidhistory. The samba winbind configuration is using 'allow trusted domains = no' as we do not care about what is in the other domains (as well as the problem that many of them are unreachable from other locations meaning winbind will choke completely if we don't disallow them). The

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Release Announcements ===================== This is the first preview release of Samba 3.3.0. This is *not* intended for production environments and is designed for testing purposes only. Please report any defects via the Samba bug reporting system at https://bugzilla.samba.org/. Major enhancements in Samba 3.3.0 include:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Release Announcements ===================== This is the first preview release of Samba 3.3.0. This is *not* intended for production environments and is designed for testing purposes only. Please report any defects via the Samba bug reporting system at https://bugzilla.samba.org/. Major enhancements in Samba 3.3.0 include:

Hi Guys, I'm setting up a new file server in our domain environment and I'm having problems with the adex configuration/module. I have couple of working file servers using rfc2307/idmap_ad and they are working perfectly. What attracted me to the idmap_adex module is the domain trust/forrest authentication support. I have 2 domains not in the same forest with a 1-way trust setup. The

for example: > a$tic[1:10] [1] "AIR " "ABCB " "ABXA " "ACMR " "ADCT " "ADEX " [7] "ABM " "AFCE " "AG " "ATG " Can anyone please tell me how to strip the white spaces from a$tic? Thanks, Roger [[alternative HTML version deleted]]

I am testing samba 3.0's net rpc vampire tool and am getting strange results... after I import the account info, the samba usernames seem to be mapping to hardcoded unix uid #'s instead of account names. For example: # pdbedit -u jah000 idmap uid range missing or invalid idmap will be unable to map foreign SIDs idmap gid range missing or invalid idmap will be unable to map foreign SIDs

Hi Rowland, I followed your suggestions and changed the smb.conf file. Currently my smb.conf file looks like below. [global] workgroup = SAMDOM security = ADS realm = SAMDOM.LOCAL wins server = SAMDOM.LOCAL password server = SAMDOM.LOCAL domain master = no local master = no preferred master = no idmap backend = tdb idmap config *:range =

I've tried numerous times but cannot get Vampire to bring across all groups or add users to all groups that they belong to. Sometimes I get everygroup except 1, other times not so lucky. Vampire log is below with an example of what is going wrong. vampire.log Fetching DOMAIN database Creating unix group: 'skischool' Creating unix group: 'sales' Creating unix group:

I've followed the instructions at http://wiki.samba.org/index.php/Ldapsam_Editposix which concerns how to setup idmap correctly with Samba > 3.0.25. I have a trusted domain which has been successfully established. However, no SID entries populate beneath ou=idmap and any logon to the trusted domain will result in: netr_LogonSamLogon: user SANDBOX\Administrator has user sid