similar to: samba 3.5.6 - ''smbclient -U% -Llocalhost' results in error - using hostname works fine, new feature?

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

Sambadevs, I don't know if this is a bug or just a spurious error message when using smbclient (on a standalone config), but checking smbclient, I get: 02:47 2pi:~> smbclient -U% -Llocalhost Unable to initialize messaging context Sharename Type Comment --------- ---- ------- samba Disk 2pi - Law IPC$ IPC

Mates, I have configured samba 100 times, but this time, I'm doing something increadibly stupid that I just cannot see. Please HELP! I'm about to jump...... Background, Old samba sever (nemesis) being replaced with new one (bonza). Both are up and operating. All networking is OK, Name resolution is fine, etc. The problem is that all users can see all the shares on the

POSTED TO THE LIST W/O ATTACHMENTS -------- Jerry, I am sending this to you directly because it contains the tcpdump information in addition to the samba logs just in case there is sensitive information contained in the files. What is happening is that samba 3.0.25c, after first running smoothly, is becoming very "chatty" across our LAN. I don't know why, but with no files or

Not sure if this got through the 1st time, so I am trying a repost. I appologize if you get this twice, but I need help! -- David C. Rankin, J.D., P.E. Rankin * Bertin, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 (936) 715-9333 (936) 715-9339 fax www.rankin-bertin.com -- ----- Original Message ----- From: "David Rankin" <drankin@cox-internet.com> To: "samba"

James, I have sent this to you directly and cc:ed the list for reasons that should become apparent below. THE SITUATION OS: mdk 7.2, 2.2.19 kernel - basically bone stock Latest addtions: samba 3.0.7-1 compiled from source (working fine); cups-1.1.18-1 from mdk rpm Reasons for additions: XP SP2 fun and games THE MYSTERY As any normal person does, I use

Andrew, Jerry and the rest of the team: Hello again! It has been quite some time since I was here and waded the waters to set up bind8 and samba 2.07 on my trust mdk 7.2 box. (by the way, it is still working like a champ) over 400 days uptime before the last extended power outage. Well, obviously a lot has changed since the 2.07 days and I am now working on a SuSE 8.2 box with samba 2.2.7a

Greetings, I have tried a few days on an off to get samba to work, but need some help. Samba version Samba 3.0.23a-1.FC5.1 Linux Fedora 5 (localhost) User: dsmith 192.168.1.104 Windows XP SP2 with lastest updates (T2385) User: dan 192.168.1.100 Linksys 8 port router I found a couple problems with the checklist and fixed them. A couple problems I wasn't able to solve. Here are the

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

Gerry, all: HELP! On mandriva, I compiled samba from source and got it running, but I cannot connect from windows. (see my post from earlier "[Samba] Compiling and Configuring Samba for Mandrival") I think this relates to the group/SID changes discussed in the release notes. However, I'm not smart enough to figure it out. The tarball compiled and installed fine. It

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================== "I think we just hit thread level Orange." -- anonymous ============================================================== Release Announcements ===================== This is the latest stable release of Samba. This is

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

Mates, Maybe I'm missing something very, very basic! I cannot see the share on my XP boxes. smbclient gives the following: skyline:/home/david # smbclient -U% -L ripper added interface ip=192.168.6.14 bcast=192.168.6.255 nmask=255.255.255.0 Got a positive name query response from 127.0.0.1 ( 192.168.6.100 ) Domain=[RB_LAW] OS=[Windows 5.1] Server=[Windows 2000 LAN Manager]

Hi, I'm trying to setup samba 3.0.14a as domain member on AIX 5.3. My test environment is: - PDC and ldap master on RH8.0 (samba 3.0.14a, openldap 2.1.29) - Ldap slave on FC3 (openldap 2.2.13) - Samba domain member on FC4 (samba 3.0.14a) - XP clients - and Samba domain member on AIX 5.3 (samba 3.0.14a) This is what I did: - Compiled samba ./configure --with-fhs --with-quotas

Listmates, Samba has been trouble free for some time, but I have a very strange error related to one machine on my network that is filling my logs with smb errors. The box in question "ripper" is a normal WinXP box that is dual-boot with SuSE 10.3. The errors are received every 30 minutes or so: Aug 21 17:04:03 archangel smbd[3116]: [2009/08/21 17:04:03, 0]

Listmates, On my Archlinux server with samba 3.3.4-1, I am getting a smbd error that is filling my logs and I'm not sure why. The box 'ripper.3111skyline.com' shown below is a dual boot box and spends most of its life and mom's XP box and masquerades as an openSuSE 10.3 box the rest of the time. There are seven other boxes on this lan with 5 others being dual boot XP/openSuSE

Guys, After upgrade to samba 3.3.4 on openSuSE 10.3, I'm getting: Jul 10 02:05:14 bonza smbd[31942]: [2009/07/10 02:05:14, 0] lib/util_sock.c:write_data(1136) Jul 10 02:05:14 bonza smbd[31942]: [2009/07/10 02:05:14, 0] lib/util_sock.c:get_peer_addr_internal(1676) Jul 10 02:05:14 bonza smbd[31942]: getpeername failed. Error was Transport endpoint is not connected Jul 10 02:05:14 bonza

> On 21 Dec 2018, at 09:54, David C. Rankin via samba <samba at lists.samba.org> wrote: > > Sambadevs, > > I don't know if this is a bug or just a spurious error message when using > smbclient (on a standalone config), but checking smbclient, I get: > > 02:47 2pi:~> smbclient -U% -Llocalhost > Unable to initialize messaging context > >

Listmates, In 8 years, since 2.02 (I think), I have never seen this behavior out of samba. I run a stand-alone server with WinXP clients. Somehow a legal assistant created (not intentionally mind you) files and directories with ACL attributes set: -rwxrwx---+ 1 cyndy ochiltree 21504 2008-10-28 16:48 AUTHORIZATION - employment.doc* -rwxrwx---+ 1 cyndy ochiltree 12804 2008-10-28 16:48