similar to: Samba Encryption...

I tried and failed to get a W98 box to connect via ppp and become part of the network. In the course of debugging this I found what appears to be a weakness in the "interfaces" handling. Testing with : nmblookup -d 2 '*' and using different "interfaces" lines. The inbound ppp connection is 192.168.3.x. 1. interfaces = 200.01.01.233/29 192.168.3.1/24 added

I recently installed Samba-2.0.6 on my machine. I copied the smb.conf over from another, working machine that I just got rid of. Anyway, I can't seem to get things working. Here are some files: when I 'restart' nmb in SWAT ---(log.nmb): Netbios nameserver version 2.0.6 started. [2000/02/02 13:33:19, 1] nmbd/nmbd.c:main(747) Netbios nameserver version 2.0.6 started. Copyright

Hi all, Reading through ENCRYPTION.txt it says to do the following: cat /etc/passwd | mksmbpasswd.sh >/usr/local/samba/private/smbpasswd However, on my Samba-2.05a install (onto RH 6.0), /usr/local/samba doesn't exist. Instead, all the files listed in ENCRYPTION.txt and WinNT.txt are in the /usr/bin directory. Amongst other things, this means I can't set the recommended security

Hello, It appears that the FreeBSD port of Samba 3.0.x may be falling behind. The port maintainter does not use Winbind and thus has not kept up with the development of it. 3.0.1 will very shortly be ported to FreeBSD, currently it is still at 3.0.0. I know there have been some recent changes to Samba that help FreeBSD out, and I wanted to make sure that the port of Samba 3.0.x on FreeBSD stays

Although I've installed samba-common, -server, -doc version 2.2.7a (from the Mandrake 9 distribution), thr -doc RPM is broken since it actually didn't install any of the files it claimed it would. No problem, I thought, I'll just read it online. Except for some reason, in his/her infinite wisdom, your webmaster has apparently decided not to put most of your documentation on your

I 'm currently running a SUN SparcStation with Solaris 2.7 and Samba 2.0.3 Samba runs as domain master and i got security=user and i enabled plain text password on PCs but those Win98 boxes are unable to change their password ( password fail) So i want to try with encrypted password but i can't find mksmbpasswd.sh. Can anyone tell me where to find it ( NOT in source please, i tried

I've attached a perl script that I wrote to build smbpasswd from /etc/passwd. Please note that this writes a samba-2.0 format smbpasswd file. This script will: # - create accounts that exist in /etc/passwd and not in smbpasswd # - remove accounts that exist in smbpasswd and not in /etc/passwd # - preserve existing password, flags and LCT fields in smbpasswd # - sets new account passwords to

Hi all, I apologize if this question has been answered before. I'm very new to setting up samba server in RedHat linux 6.0 and accessing it from windows NT 4.0 SP3. I set up samba server (2.0.3) with encryption so that when I access it from NT, the NT box won't complain about sending password in a clear text over the wire. I created /etc/smbpasswd using mksmbpasswd.sh utility --snip of

Hi listmembers, due to a few very short but good tips from you guys and to much hassle with my firewall (ipchains) I finally got samba running as a server and client (I even made an update from source, just with normal ./configure, make, make install after uninstalling the previous version of course). With "encrypted passwords = no" everything is working fine (except for some minor

Hi, I have samba installed on my Linux system (Red Hat 7.2), and Windows 98 on another PC as a Samba client. Samba works great if PlainTextPassword is enabled. However, if PlainTextPassword is disabled on Windows client, connection to the Samba shares no longer accepted. I believe I've done everything in order to make encrypt passwd working: * I converted /etc/passwd to

The Samba Team is pleased to announce Samba 2.0.6. This is the latest stable release of Samba. This is the version that all production Samba servers should be running for all current bug-fixes. It may be fetched via ftp from : ftp://ftp.samba.org/pub/samba/samba-2.0.6.tar.gz Or just follow the link on the main page of your nearest http://samba.org mirror. Binary packages for supported systems

works with plaintext passwords (as fallback) NT4.0 incl. servicepack refuses to work (you may recognize this behaviour by repeating entering the login and the password a couple of times. Then you will be able to mount a share). (more on this topic in /usr/doc/packages/samba/ ENCRYPTION.txt). Solution: Well, either you may convince NT via its Windows registry to use plaintext passwords There is

works with plaintext passwords (as fallback) NT4.0 incl. servicepack refuses to work (you may recognize this behaviour by repeating entering the login and the password a couple of times. Then you will be able to mount a share). (more on this topic in /usr/doc/packages/samba/ ENCRYPTION.txt). Solution: Well, either you may convince NT via its Windows registry to use plaintext passwords There is

Hi all, Quick question, is it possible to take an existing /etc/passwd file and run it through mksmbpasswd.sh (or some other script) to update a smbpasswd file? I am asking this because everytime we change a password or add or delete usernames on a machine, it would seem we have to do the same thing to change th samba password file, and I'm hopeing there is an easier way..... thanks, jeff

I see that mksmbpasswd.sh (plus a little editing) would be a good way to set up users with "NO PASSWORD" in bulk. But suppose I don't want the risk of the "NO PASSWORD" approach. Now somebody with root access must run smbpasswd for each user they want to activate. But can't I just do this anyway (with the -a 'add user' option), without ever having run

Hallo, i installed samba V2.0.3 on a linux server in a company. for better security i will use encypted passwords. for synchronisation of the unix password file and the samba password file i tried out the script mksmbpasswd script. my security settings at the server are easy and i set the permissions of the unix passwd file at 774 and also my smbpasswd file at 744. starting the script with the

Never mind, I figured this one out (I think!). Here is what I ran [System: RedHat 7.0/Samba 2.0.7ssl on P-90] cat /etc/passwd | /usr/bin/mksmbpasswd.sh >> smbpasswd (After backing-up the current 'smbpasswd', of course) This seemed to do the trick, however, all of the accounts where disabled by default. I figured this to be the intended behavior (for security with system

Hi, Samba guru; I need your help. I am using samba 2.0.6. security = server and password server = NT PDC; nt acl support = yes. I am trying to change permission using the NT security dialogs but failed. In the log file I found that apparently when I connect to the samba directory, I get authenticate correctly. But when try to change permission, samba does not try to authenticate through password

Hi, I'm using samba-3.0.28-0.fc8. I'm trying to build a file server for 100 users. I created a perl script that automatically adds the 100 users plus their passwords with success. Now I'm having difficulty creating a script using the smbpasswd command because passwords must be entered in stdin. I also tried smbpasswd -s option but it asks passwd in stdin. Is there a way that I can use

David Kleppinger wrote: > > I've just installed samba 2.0.6 on our HPUX 11.0 system and am having > problems getting it to work. Any help would be appreciated. > > I'm trying to use "security = DOMAIN". Our PDC/BDC are NT 4.0 SP6. The > workstation I'm trying to connect from is NT 4.0 SP4. > The HP machine shows up in the network neighborhood but