similar to: mdk 7.2 init.d script Mystery....

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

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

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"

Mates, In following chapter 35 "How to Compile Samba" I have looked at ./configure --help and I have a few questions. Originally I installed 2.0.9 via RPM, and of course there are no longer RPMs for mdk 7.2. On 7.2, smbd and nmbd are installed in /usr/sbin. The docs are in /usr/share/doc/samba-2.0.9. I don't know where the rest of the pieces of the puzzle were scattered by

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

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 have set up a backup scheme that uses rsync to backup shares from my mdk 7.2 box to an old ibm box that is running win95. Basically I use "smbmount //backup/d /mnt/backup -o password=" to mount the ibm's d:/ as /mnt/backup. How can I test to see if the drive is still mounted without using another smbmount call prior to starting the rsync backup. smbmount works for this,

Mates, I am at the point that I will have to update my trusty samba 2.0.9 to 3.0.6 or 2.2.11. (damn SP2) Problem is that my production machine is still running Mandrake 7.2 and, of course, there aren't any RPMs for the old distro. So, I guess my option is to install from source. Do I need to rpm -e the 2.0.9 before attempting to compile and install 2.2.11 or 3.0.6? My server is a simple

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

Mates, Just got done configuring and compiling 3.0.7-1 on my Mandrake 7.2 box. The process was as follows: ./configure --prefix=/usr --with-smbmount make The following is a listing of the ../bin directory. Does it look like all the pieces got built and are about the right size?? Any feedback before doing the 'make install' would be appreciated..... [root@Nemesis source]# ls -al

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]

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

<earlier, David Rankin wrote to no avail:> Mates, I have been watching a developing problem over the past few weeks. Most likely a M$ patch to XP that has caused problems. What happens is that XP clients try to open the standard "File" -> "Open" dialog (like in word, or whatever) and the file open dialog hangs and stops responding for 15 seconds or so. I have

Listmates, After wrangling with the voltage value on the CyberPower 1000AVRLCD and now having 2 of them working, I though it would be a simple matter to move my APC BP650 from apcupsd to nut so that all 3 servers would be monitored on the same web interface. The APC is attached to an older box running openSuSE 11.0 with nut-2.2.2-66.1. (nut-classic). The APC BP650 uses a serial connection

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

Mates, I'm trying to learn a little more. I have 3.0.7 running on Mandrake 7.2. I could see all the shares, but couldn't access the files "sendfile failed". I set use sendfile = No and all is well. I have a separate system Suse 9.0 pro with use sendfile = yes and I have no problems. What is the difference??? -- David C. Rankin, J.D., P.E. RANKIN * BERTIN, PLLC 510 Ochiltree

Guys, I think the answer to my question is to upgrade samba. However, since this is my production machine, I thought I would try and understand the problems I'm having a little better to insure that an upgrade will correct my issues. My setup - Mandrake 7.2, samba 2.09. Win98, ME and XP clients. The 98 and ME machines have no problems. The XP machine has some intermittent slowness

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

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