similar to: Building libsmbclient independent of Samba

Hi All, Yesterday, I've upgraded my Samba server from 3.021c to 3.023 through yum upgrade samba*. I'm running Fedora Core 4 Kernel 2.6.17-1.2142 on this server. After upgrade has been completed, I lost the attributes of ownership and groups. I noticed that the uids/gids have changed for all AD accounts. This means that users can't have total access for their files and no access

I am trying to build samba 3.0.22 on an older Slackware system. gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release) The error I'm getting is smbd/statvfs.c: In function `linux_statvfs': smbd/statvfs.c:40: incompatible types in assignment Anyone have any clues?

Hi All, I am working on a product(running on Linux with Kernel 2.4) in which print-server is one of the functionalities. For that I have integrated Samba and CUPS which will let me give print-commands from a Windows PC and the commands are communicated to the cups via Samba and finally the prints are done by the printer which is connected to the product. I have both CUPS(1.2.1) and Samba(3.0.22)

I currently have in my slapd.conf: index sambaSID eq the release notes for 3.0.23 say I need index sambaSID sub can I use index sambaSID eq,sub TIA

I want to eliminate the Samba version information that appears when mapping a share on a samba server from windows explorer (winxp). As an example after mapping a drive in windows, say drive t:, explorer shows drive t: mapped as: 'homes on 'Samba 3.0.20b-3.4-SUSE (servername)' How can I eliminate the samba version info, 'Samba 3.0.20b-3.4-SUSE' from windows explorer. I have

Since upgrading to 3.0.23 I have encountered several problems. (latest Debian Sarge with deb's from samba.org and security = ADS). All was working flawlessly before. *1.* getent passwd no longer lists machine accounts. *2.* On the Win2K pdc, the samba system's "DNS name" on the general tab is now listed as localhost.localdomain, and the operating system is still listed as

During some recent testing of winbindd (3.0.22) in a multi-domain, multi-DC AD context, the AD expert I was working with was very interested in winbindd's choice of domain controller (it apparently was not choosing the one(s) AD-expert expected). I understand that Windows domain members have an algorithm based on DNS SRV records and IP address comparison, and I've seen some code posted in

I have a samba PDC running 2.0.20c I installed Samba 2.0.23 on a client joined to the domain. With this combination, when I attempt to connect to a share on this client from any host even the localhost results in the following: $ smbclient //localhost/atest -U auser Password: Domain=[DOMAIN] OS=[Unix] Server=[Samba 3.0.23-SerNet-RedHat] tree connect failed: NT_STATUS_ACCESS_DENIED Windows

I'm curious if anyone has suggestions about a problem we have encountered. We have recently upgraded a 2.2.8a server to 3.0.23. The server in question is running Solaris 8 with NIS+. Storage is from our SAN. Since the migration, we have found that we no longer have access to several shares. They are connected, but we are unable to get to them. Samba will indicate that we are connected to

hello i cant manage groups with usrmgr and the configuration below debian sarge, samba 3.0.22, openldap 2.2.23, smbldap-tools 0.8.7. usrmgr reports he cant find the groups. is it solved by samba 3.0.23a ? does anybody report enhancement after upgrading to 3.0.23a ? Regards ELH -- ?ric LE H?NAFF ?cole normale sup?rieure - Centre de ressources informatiques Informaticien, Ing?nieur d?veloppements

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ========================================================== == == Subject: Memory exhaustion DoS against smbd == CVE ID#: CAN-2006-1059 == == Versions: Samba Samba 3.0.1 - 3.0.22 (inclusive) == == Summary: smbd may allow internal structures == maintaining state for share connections == to grow unbounded. ==

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ========================================================== == == Subject: Memory exhaustion DoS against smbd == CVE ID#: CAN-2006-1059 == == Versions: Samba Samba 3.0.1 - 3.0.22 (inclusive) == == Summary: smbd may allow internal structures == maintaining state for share connections == to grow unbounded. ==

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Just attempted to build 3.0.23pre1 on HP-UX 11.11 today, preparing for a planned move to a later version of 3.0.x (we're currently down at 3.0.11). Configure ran fine, but make eventually failed here: Compiling lib/sysacls.c cc: warning 422: Unknown option "fPIE" ignored. cc: "lib/sysacls.c", line 1277: warning 611: Type

Inn the error: Cannot read or set the permissions for file \\server\share\folder: initializing the SD failed Does SD stand for Security Descriptor? I have a server that doesn't want to make new folders without giving this error. This only applies to folders!! Files don't give this message. I downgraded from 3.0.23c-1 to 3.0.21b-1 but that didn't solve it. It did solve the

Previously had samba-3.0.22 on RedHat Enterprise 4 functioning happily, using pam_winbind to authenticate against our campus active directory (currently only doing password authentication, account info is still retrieved via NIS). /etc/pam.d/system-auth attached After upgrading to 3.0.23 * I needed to add idmap options (I used idmap backend = rid), else winbind would only start in "netlogon

snip from make.log: Compiling libsmb/libsmbclient.c with -KPIC "libsmb/libsmbclient.c", line 3249: warning: argument #3 is incompatible with prototype: prototype: pointer to char : "libsmb/libsmbclient.c", line 1167 argument : pointer to const char "libsmb/libsmbclient.c", line 3843: warning: argument #5 is incompatible with prototype:

Building Samba 4.1.4 on Solaris 10 with command line: CC=gcc LDFLAGS='-R /opt/local/samba/lib:/opt/local/samba/lib/private' \ ./configure --prefix=/opt/local/samba make fails linking 'default/examples/libsmbclient/teststatvfs': [3505/3811] Linking default/examples/libsmbclient/teststatvfs ld: warning: symbol 'dyn_LIBDIR' has differing sizes: (file

Hello List, In regards to RPM packages, what is the difference in the prebuilt ones for example the FC5 RPM's directly from samba.org or obtaining the latest .tar.gz and running ./makerpms.sh for the desired distribution. Does this way optimize for example - x86-64 or SMP ? Cheers, Adrian Sender. -----Original Message----- From: Gerald (Jerry) Carter [mailto:jerry@samba.org] Sent:

Ok, I have been doing a lot of reading and saw many references to samba 2.2.8a and libsmbclient.so and I thought that I would just go ahead and download, compile and install it. After going through configure, the make and make install, I still don't have a libsmbclient.so file to link my program to. I have never come across this before, there has always been a .so file created from any of

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Here's a short list of parameters I'd like to remove from smb.conf. hosts equiv read bmpx wins partners ldap server ldap port homedir map nis homedir magic script magic output Comments? jerry -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org