similar to: Samba 3.0.23c Available for Download

Mates, The saga continues, but THANK GOD 'make revert' WORKS. Here is my problem. I am trying to compile 3.0.7 from source and install it on my Mandrake 7.2 box. The gcc compiler is 2.95.3. Here is what I have done: [stop samba] # ./configure --prefix=/usr --with-smbmount # make # make install # /etc/rc.d/init.d/smb start Here is what I get: [root@Nemesis david]# tail

Mates, What would cause smbclient not to list my printer share?? (mandrake 7.2, 2.2.19 kernel) [david@Nemesis david]$ smbclient -U% -L localhost Domain=[RB_LAW] OS=[Unix] Server=[Samba 3.0.7] Sharename Type Comment --------- ---- ------- guillory Disk David Guillory Bertin Disk Darren Bertin Rankin

I never thought it would happen to me, but it did... I have read threads about slow copies from WinXX to Linux/Samba on the list in the past, but I don't recall a concise answer regarding what the cause was. THE PROBLEM: Trying to copy an 8 meg file from Win95 to my Linux/Samba box (named "Nemesis" - for good reason), the transfer speed slows to a crawl. The Win95 copy dialog box

Mates, I dunno if nobody else is using the samba binaries to put 3.0.20-1 on SuSE 9.3 -- or -- if I'm just doing something stupid, but there seem to be library problems. Specifically, we are getting library errors for the *.so.2 libraries, regardless of whether we try via YAST or RPM. david@nemesis:~/Documents/linux/rpms/samba320> ll total 19970 -rw-r--r-- 1 david users 60998

Listmates, I have had a few boxes where the 'matchname' message is filling my syslog with one new message ever ~40 seconds or so. No performance problems, just the log annoyance. An example of the messages are: Jan 11 13:43:03 nemesis smbd[2246]: [2010/01/11 13:43:03, 0] lib/util_sock.c:1685(get_peer_name) Jan 11 13:43:03 nemesis smbd[2246]: Matchname failed on Adrienne-PC.rbpllc.com

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 =============================================================== Chef: Bon app?tit! Donkey: Oh, Mexican food! My favorite. -- Shrek 2 =============================================================== Release Announcements =====================

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Folks, I've uploaded the *final* 3.0.23c roll up patch to http://samba.org/~jerry/patches/patch-3.0.23b-3.0.23c-gwc-2.diffs.gz. I've already cut the 3.0.23c tarballs so unless there is a major problem, this will be the final change set. Please report *any* bugs that you find. I'd like to wrap this one up and do the public 3.0.23c

Cross-posting scares me, but... Have you looked at the latest RPMs for SuSE, from ftp://ftp.suse.com/pub/projects/samba/ ? They've worked like a charm for me, thus far (revision after revision, a simple rpm -U * seems to work...) -----Original Message----- From: david rankin [mailto:drankin@cox-internet.com] Sent: Mon 9/12/2005 5:30 PM To: samba; Suse Linux Subject: [SLE] SuSE 9.3 and

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 =============================================================== Happy Birthday, Deryck. =============================================================== Release Announcements ===================== This is the latest stable release of Samba. This is the version that production Samba servers should be running for all

Mates, Still can't get the latest samba binaries to inatall on SuSE 9.3. I've downloaded them from the samba site and from ftp://ftp.primastasys.com/pub/Samba-Packages/ still no joy. The problem is library related: nemesis:/home/david/Documents/linux/rpms/samba320 # rpm -Uvh * warning: cifs-mount-3.0.20-0.1.i586.rpm: V3 DSA signature: NOKEY, key ID 414a57c3 error: Failed

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================== "I hate 'winbind use default domain'" -- attributed to numerous Samba developers ============================================================== Release Announcements ===================== This is the latest stable release of Samba.

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================== It was during the jra vs. vl code reformatting wars. Somewhere around the time of the 80 column massacre. -- coffeedude ============================================================== Release Announcements ===================== This is

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 =============================================================== Done with Fish. -- John Laroche (Adaptation) =============================================================== Release Announcements ===================== This is the latest stable release of Samba. This is the version

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 =============================================================== Done with Fish. -- John Laroche (Adaptation) =============================================================== Release Announcements ===================== This is the latest stable release of Samba. This is the version

Samba errors with smb QUERY_PATH_INFO, Error: STATUS_OBJECT_NAME_NOT_FOUNDFrom: Timothy D Newcomb Subject: Samba errors with smb QUERY_PATH_INFO, Error: STATUS_OBJECT_NAME_NOT_FOUND > Did you get an answer for this ? I am seeing it on an XP box and I have > the same problem..slow load time...in "my computer" Tim, No I didn't, thanks for the reply. I just figured that

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================== You are standing in an open field west of a white house, with a board front door. There is a small mailbox here. ============================================================== Release Announcements

Jerry, Jeremy, et. al. Last night's upgrade from cifs-mount-3.2.0-24.1.121 to cifs-mount-3.2.0-24.1.122 on a openSuSE 10.3 x86_64 machine broke mount -t cifs. Now attempting to mount shares results in the following: 11:10 alchemy/home/david/bin] # mount.cifs -v //nirvana/david /mnt/nirvana-david -o username=david,uid=1000,password=notmypass parsing options:

Hi all We are currently looking to implement a scenario where our AIX Unix Server and Windows Server can communicate with each other using a version of Samba. We currently scan images which are stored on our Unix system and ideally we would like our Windows Server to have access to these files. The software we use for our daily business is Unix based so the the scanned images have to be

Hi all, We have an old 3.0.7 samba running as PDC. As we have problems with XP64 clients accessing the domain, I compiled a 3.0.23c and copied the smb.conf. Some of the client work well with the new Samba, but most of them do not. Was there any relevant change in the smb.conf part between the two versions? Thanks Bgs

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================== A revolution without dancing... is a revolution not worth having! -- V ============================================================== Release Announcements ===================== This is