similar to: Amanda 2.3.0.5-Samba 1.9.16p11 PC backups...

David Allan Finch wrote: > Has anyone considerd modify the Unix encypt to use > the same system as NT. IE the encypted pasword in the > /etc/passwd or NIS/NIS+ table is the same for both? Err. That would be a *really* bad idea. See the l0phtcrack source for details :-). Seriously, though. The password hashes used on NT are very poor. They don't use salt and people are now

I am trying to setup my Sun running samba 1.9.18p10 so that it can backup my dept's PCs. I can get it to work manually using the smbclient command with no problem. What I would like to do is have a script that is able to take a list of PCs, determine if a PC is online, backup that PC, then move on to the next one. If a PC is down, it can report an error to the admin to state that the

Ok.. Just for the record, I STAND CORRECTED! The problem does appear to be NT.. The thing that irritated me was that nobody was interested in giving any backup data! Everyone just wanted to blindly admit that it must be NT. Ok.. Enuf bitching.. On to the better stuff... Anyway, David Mansfield and I are trying to narrow down the machine configurations where this happens.. Currently, we've

Has anyone tried DFS Client SW on a Win 95 machine and then tried to mount the usual samba drives? All I get is a login request that gets refused even with known, correct, credentials. Its appears just the same as the problem we got after installing SP3 on an NT4 machine before changing the registry. The only way to fix it is, on the 95 machine, to remove the DFS client, remove ALL the network

My whole problem as far as samba was concerned was not compiling with DES support *and* that I did compile with FAST_SHARE_MODES. One clue was this in the samba.log. file. I then did a dejanews search for smb_shm_open and came up with that portion of the solution. ERROR smb_shm_open : mmap failed with code 11 The DES portion came from just reading the WinNT.txt file that came with Samba. I

I have a Win95 machine that I am trying to connect to a Samba share. When I log in as administrator, I can connect to any and all samba shares just fine. When I log onto the PC as a normal user, it asks for a password and rejects them all. The logs say "server xyz rejected password" for each of these attempts. This server has SP3 and I *do* have the encryption stuff compiled in. I

Ernie, Thanks for the great info.. Based on what you were seeing, would you suspect that part of the problem is with the combination of NT and the 3com card (3c595)? Currently, we are ONLY seeing this under NT Workstation (not server) and almost all of our machines have this same 3com 3c595 card (only if using 100BaseT).. -- Rick -----Original Message----- From: Ernie Oporto

> From: Gary Stainburn <gary.stainburn@ringways.co.uk> > To: "Samba Mailing List (E-mail)" <samba@samba.anu.edu.au> > Subject: smbtar multiple machines > Message-ID: <01BDDD6E.ABFF0580@garys.computer.leeds> > > Hi all, > > I'm just looking at using smbtar to backup the Win95 PC's on my network, and would like usability ideas please. >

I just installed Samba for the first time. Installed and setup like a dream. Unfortunately, I can't login to save my life. The server appears in the Net. Neighborhood, but when I double-click to login, the login window give the following message: Incorrect password or unknown username for \\SERVERNAME Entering a username and password (from /etc/passwd) returns: \\SERVERNAME is not

Yes!!!! You just solved a problem I've been having since 1.9.17p1!!!! I didn't realize that CIFS was limited to passthrough authentication for only its domain, so that listing multiple password servers from different domains would not work...the following did. Yeeeehhaaa! Hurm...excuse me. I added to the following in my config to make this work: netbios aliases = unix1 unix2 (not

I hate to suggest this, but we need to do what has been done on a few other lists that I'm on. We need to close the list off to only people that are members. It's a shame to see so much spam here after seeing it in my personal mailbox all day long. At 11:21 PM 7/24/97 +0000, you wrote: >Date: Thu, 24 Jul 1997 11:14:25 +0200 (MET) >From: Konstantin Eftaxias <kef@eeb.de>

Ronny Blomme <Ronny.Blomme@elis.rug.ac.be> writes: > The default configuration for smbclient in samba-1.9.18p8 is to send > verbose output to stdout. The output sent to tape is a mix of this > verbose output and the tar-file => corrupt tar file on tape The attached patch for SAMBA fixes this problem, preventing log messages from being printed to stdout if the tar-file is

One thing that needs to be mentioned is that for PC backups, the amanda patch that has to be applied to samba requires that you use level 3 logging to see the "Total" line. Also, does anyone know what this error means? smb: \> recurse directory recursion is now on smb: \> dir received 5 entries (eos=1 resume=0) . D 0 Thu Jun 5

When attempting to sync multiple sources to a single area, /fs/lib# ls ./ ../ bin/ founder/ skill/ var/ I want to combine these four rsyncs /usr/local/bin/rsync --exclude '.snapshot' --stats -v --bwlimit=1024 --delete -atz 'host::lib/bin' . /usr/local/bin/rsync --exclude '.snapshot' --stats -v --bwlimit=1024 --delete -atz 'host::lib/var' .

Is there a way to tell rsync that if it does not have contact with a certain rsync server to continue on to another for file requests? I imagine something like this, where you define two servers as the source... /usr/local/bin/rsync {serv1,serv2}::src dest ...proposing that 1. Should serv1 be down when the sync is originally started, that serv2 be contacted after a timeout. 2. Not so

Can anyone tell me what the error is with recursion here? It is keeping my smbclient from giving AMANDA a sice for the share. Without recursion, and stepping through the directories manually, I can do the dir and get no errors. smb: \> ls received 8 entries (eos=1 resume=0) . D 0 Thu Aug 15 09:19:58 1996 .. D

Has anyone noticed that there appears to be a few problems with regards to Samba and in particular the usage of smbclient, which can do one of the following : 1) Complete & udder death of the NT networking subsystem (which requires a reboot to cure) 2) smbclient appears to lose its connection with the host being contacted and eventually needs to be killed. I'm not too sure how

Hi Folks, I want to use samba and amanda to backup NT/win file system. I downloaded the latest version of Samba and trying to install on bsdi4.0 and it complains that the OS is a "trapdoor" OS and will not work propperly. I installed it anyway and I can connect to NT no problem but when I connect it back to the unix box, it complains about "Bad password - name/password in a Tree

smbstatus reports the following...that my NT users on this one samba server are connected as the guest user "nobody". All Win95 users are connected under their proper name. Anything I need to change? Samba version 1.9.16p11 Service uid gid pid machine ---------------------------------------------- gdl nobody nogroup 1555 gdl-dt (137.202.211.8) Wed

I am getting the following level 5 logging for a Win95 PC under user-level sharing that is sharing to the user "backup" with "full-access". Can anyone help me get logged in via smbclient? shokk:/#> smbclient \\\\EOPORTO-DT\\DEPOT -U BACKUP doing parameter os level = 5 doing parameter domain controller = 137.202.xxx.xxx doing parameter wins proxy = yes doing parameter wins