similar to: [Announce] Samba 3.3.0 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 Release Announcements ===================== This is the second 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 second 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 ================================================================ "Always keep an open mind and a compassionate heart." Phil Jackson ================================================================ Release Announcements ===================== This is a bug fix release of the Samba 3.2 series. Major enhancements included in

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ================================================================ "Always keep an open mind and a compassionate heart." Phil Jackson ================================================================ Release Announcements ===================== This is a bug fix release of the Samba 3.2 series. Major enhancements included in

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

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

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

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]]

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

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ================================================================= "There are two ways to write error-free programs; only the third one works." Alan J. Perlis ================================================================= Release Announcements ===================== This is the latest bugfix release release of the Samba 3.3

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ================================================================= "There are two ways to write error-free programs; only the third one works." Alan J. Perlis ================================================================= Release Announcements ===================== This is the latest bugfix release release of the Samba 3.3

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

I'm using Fedora Core 6 which uses cifs.mount version 1.10. When mounting shares from a particular Windows 2003 R2 server, I cannot read certain directories. For example, when performing an 'ls' command as follows: [root@backup Admin]# ls /share/CORP-SERVER/C\$/Corp/User\ Files/xxx\ Finacial\ Shared/Admin/Freddie\ Mac/ ls: reading directory /share/CORP-SERVER/C$/Corp/User Files/xxx

================================================================== ?I found that dance was key to keeping depression out of my life. When you dance, things just go away, things don't seem so bad. There's no better way to take care of health than through something as joyous and beautiful as dance.? Patrick Swayze

================================================================== ?I found that dance was key to keeping depression out of my life. When you dance, things just go away, things don't seem so bad. There's no better way to take care of health than through something as joyous and beautiful as dance.? Patrick Swayze