similar to: [Announce] Samba 3.5.6 Available for Download

================================================================== "Each day provides its own gifts." Marcus Aurelius ================================================================== Release Announcements ===================== This is the latest stable release of Samba 3.4. Major enhancements in Samba 3.4.10 include: o Fix smbd coredump (bug #7617). o Fix Winbind

================================================================== "Each day provides its own gifts." Marcus Aurelius ================================================================== Release Announcements ===================== This is the latest stable release of Samba 3.4. Major enhancements in Samba 3.4.10 include: o Fix smbd coredump (bug #7617). o Fix Winbind

I know there is the command "wbinfo -t". But when it says that "could not check secret", how do I know it's the secret is bad, or something else wrong, like winbind went crazy maybe? Also, sometimes I saw problems like "wbinfo -t" just says "secret is bad", when all the daemons were running. It sure was good at some point before. So my

When I change file property - security from Windows, I can see both from packet sniffer and Samba code, that there are 4 types of "security information": Owner ID Reference Primary Group ID Reference Discretionary ACL Reference System ACL Reference So if I want to change the primary group name on a file, by right click on the file->property->security->advanced->select

Hello, all, I can not easily find an answer to this question: why do we need samba 3.0 to join an ADS, if samba 2.x can join the ADS domain just as well, even though the PDC is in native mode? What's the benefit for samba 3.0 to be a member of ADS? What restrictions I have if joining samba 2.x to the domain as an NT4 server? I bet people on this list should know better than me. Can

I need help to resolve this issue. I saw that Andrew put a patch by Antti to enable users without full admin access to join samba into an AD domain. I am playing with it and always get "Insufficient access". Using the same user, I can join a Windows box into the domain just fine. The user is a member of "domain users", but not "domain admins". I can use a

I can't make it work although both sign&seal and restrictanonymous are set to 0. My setup is: w2k sp2 as PDC, w2k sp3 as client, samba 3.0a21 joined into the PDC domain as an ADS member. The scenario is, from the w2k sp3 client, connect to a share hosted by samba, create a file, then use property->security->add tab to add an ACE, then the browsing user/group windows appears

SUBJECT: [samba]Error join NT domain when I join NT domain by the command :smbpasswd -j DTWX -slaver,Then the results show as followed [root@root] #smbpasswd -j DTWX -slaver cli_nt auth2 :Error NT_STATUS_NO_TRUST_SAM_ACCOUNT Failed to change passwd f or domain DTWX Unable to join domain DTWX [root@root] #

Hi, Has anyone met something like this ? dialor*CLI> sip show peers Name/username Host Dyn Nat ACL Port Status 7541/7541 (Unspecified) D 0 UNKNOWN 7540/7540 (Unspecified) D 0 UNKNOWN 7534/7534 (Unspecified) D 0 UNKNOWN 7533/7533 (Unspecified)

Hello, I'm trying to add a column to the following data frame. The new column will contain "black" when the 5th column(if_TE_related) is "TE_related", or "orange" when the 4th column is " " (space). "chromo" "MSU_locus" "end5" "end3" "if_TE_related" "chr04" "LOC_Os04g01006" 1032

Hi! I've setup Samba4alpha14 on a FreeBSD 8.2-RC2 box as a DC which just works serving network of a couple of dozens of Win7 clients. Then I installed Samba 3.5.6 on another of FreeBSD box and wanted to join it into the AD. I've run in the following set of issues: 1. Joining domain with "net ads join -U administrator" fails with the following error messages: "kinit

I have a client that recently upgraded from Win XP to Win 7. They were seeing odd slowdowns and poor performance, so we upgraded to Samba 3.5.6 and enabled win 7 support "max protocol = SMB2". They contacted me this morning with a report of more strange behavior, names the inability to access newly created folders with the message "file is too large for file system". There

Hello, I use Debian Squeeze with Samba 3.5.6. I do experience problems that might be related to those described in bug 7892 that can be found found here: https://bugzilla.samba.org/show_bug.cgi?id=7892 I could not find any information about this bug being fixed in Samba 3.5.x. In the realease notes of Samba 3.4.10 I found this: '* BUG 7892: Fix stale lock in open_file_fchmod().' As

Greetings, Still no progress trying to get Samba 3.5.6 built on Solaris 10, using gcc 3.4.6. Maybe fresh eyes will see something? Been having issues building samba since 3.4.9 (and anything greater than 3.2.15 on Solaris 9 where samba will build, but winbind will not work properly for user authentication.) techops$ make Using CFLAGS = -I/opt/local/kerberos5/include -O -I.

I have a script (below) which attempts to make an index out of all the man pages on my system. It takes a while, mostly because it runs man over and over... but anyway, as time goes on the memory usage goes up and up and never down. Eventually, it runs out of ram and just starts thrashing up the swap space, pretty much grinding to a halt. The workaround would seem to be to index documents in

Hello, I have a debian etch with (samba 3.5.6-27,) shares and windows 7 in the domain. This works ok. Since i installed the new version 3.6.16-31 I can not login with domain users in my windows client and the shares are inaccessible. I solved the problem with the login, removing the following line in my smb.conf: *ldapsam:trusted = yes* but why this line works with the version 3.5.6-27 and not

Hi all, We're testing 3.5.6 as an upgrade to our old 3.0.x instance. Our XP boxes can see our Samba 3.5.6 shares fine. Our Win7 boxes cannot. "The specified network name is no longer available." Relevant config portion is as follows: log level = 20 workgroup = OURCOMP security = ads encrypt passwords = yes realm = OURCOMP.ORG password server =

Guys, I have probably missed an announcement or overlooked something in a changelog, but I just want to confirm what I'm seeing is expected behavior. I run samba in standalone mode and I have always checked operation with smbclient -U% -Llocalhost Now the faithful command returns an error: Connection to localhost failed (Error NT_STATUS_BAD_NETWORK_NAME) Simply using the hostname

Hi. I'm using samba to authenticate squid users in Windows AD, and to provide 'em some statistics on the Internet usage. As this requires the existence of windows users in Unix environment, I use nsswitch.conf and nss_winbind.so to map users in Unix environment via samba as domain member (security = ads) and its winbindd daemon. As of samba 3.5.6 I'm expiriencing some major

Hello, I'm running a Samba 3.5.6 standalone server on FreeBSD 8.1, with XP and 7 clients. I can't get Samba to syncronize Windows & NIS passwords, in fact it's behaving strangely from what i think: Relevant (i think) parts of smb.conf: encrypt passwords = yes passdb backend = tdbsam pam password change = yes unix password sync = yes passwd program = /usr/bin/passwd