similar to: File locking in NFS on Solaris

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

Hello, I try to use Samba as a PDC. I have a old Windows 4.0 PDC and I want to get the users and the groups from the PDC. I joined the domain and get the users and groups with "net rpc vampire". The users and the groups were written in local user- and group-database, but the relation between the users and groups were lost, in the groups were no users. A short message from the

Ive just discovered that my previous email is wrong - the password sync does in fact work under Solaris fine. What is happening however is that when I create a new account, and call smbpasswd $user as root, it only updates the SMB password and not the Unix password as well. I though I could change my call to /bin/passwd in my new user creation scrip with /usr/local/samba/bin/smbpasswd -a, but as

I have been using (actually inheareted the system) a file for the Samba password database using since something during the 2.0 erra. New accounts have been successfully added and users are apparently logging in ok. After installing 3.0.6 I am seeing these things in my log (log level=3). mod_smbfilepwd_entry: Using old smbpasswd format. This is no longer supported.! 1. What is the

I have a Sparc Ultra-2 running Solaris 2.7 and Samba version 2.0.5 Most of the time everything works fine, Win95 & WinNT users connect to Samba shares and work. Occasionally, users report not being able to view the Samba server in which case I have them map a drive manually or do a "find computer". There are times when this does not work. I take a look at the logs

On Fri, 2019-05-31 at 11:40 -0700, Jeremy Allison via samba wrote: > On Fri, May 31, 2019 at 07:09:44PM +0200, Andreas Reichel wrote: > > > > When adding me as the user with 'smbpasswd -a andreas', and entering a password, > > > > no LANMAN hash is generated. The generated smbpasswd entry always contains 32 X as the first hash. > > > > > > >

Hi there, I'm having some strange behaviour from OpenSSH It presents itself when using the "ssh -t" / pseudo terminal. We are using this feature to update the wtmp and it is working fine on SuSE and RH, but our AIX hosts are getting hung. The first attempt is usually successful, but eventually, the session is hung and the CRTL-Z does not put the process into

Dear list subscribers, Recently I upgraded my samba version from 2.0.5 to 3.0.8-2. The setup I use is basically very simple: a W 98 box should be able to access some disk-shares and a printed, connected to a Linux box, running Debian's sarge distribution. Accessing the disks is no problem, but the printer can't be accessed any more. My log.smbd logfile shows lines suggesting

I've been looking throught the archives for a set of things to be done to migrate a install with samba 3.2.5 (lenny) to another server (wheezy) I can cope with the name change, that's no problem, but I'd like to avoid having to recreate the users on the new server, so far I tried this, without much success - scp the smb.conf to the new server - make hot backups cd /var/lib/samba

On 31.05.19 22:07, Andrew Bartlett wrote: > On Fri, 2019-05-31 at 11:40 -0700, Jeremy Allison via samba wrote: >> On Fri, May 31, 2019 at 07:09:44PM +0200, Andreas Reichel wrote: >>>>> When adding me as the user with 'smbpasswd -a andreas', and entering a password, >>>>> no LANMAN hash is generated. The generated smbpasswd entry always contains 32 X

Hello, I try to use Samba as a PDC. I have a old Windows 4.0 PDC and I want to get the users and the groups from the PDC. I joined the domain and get the users and groups with "net rpc vampire". The users and the groups were written in local user- and group-database, but the relation between the users and groups were lost, in the groups were no users. A short message from the

Hi list, My case : Local UNIX user : ZTEST domain : uuq.ork domain user : UUQ\ztest smb.conf for standalone samba : /home/hywu/smb.conf [/home/hywu] # cat /home/hywu/smb.conf [global] passdb backend = smbpasswd workgroup = WORKGROUP security=user Smbpasswd fail to change local UNIX user password (ZTEST) when samba role is DC. I want to change password of local UNIX user "ZTEST" but

On Thu, 25 Jan 2024 18:27:48 +0800 hhyy ww via samba <samba at lists.samba.org> wrote: > Hi list, > > My case : > Local UNIX user : ZTEST > domain : uuq.ork > domain user : UUQ\ztest > smb.conf for standalone samba : /home/hywu/smb.conf > > [/home/hywu] # cat /home/hywu/smb.conf > [global] > passdb backend = smbpasswd > workgroup = WORKGROUP >

Rowland Penny via samba <samba at lists.samba.org> ? 2024?1?25? ?? ??6:42??? > On Thu, 25 Jan 2024 18:27:48 +0800 > hhyy ww via samba <samba at lists.samba.org> wrote: > > > Hi list, > > > > My case : > > Local UNIX user : ZTEST > > domain : uuq.ork > > domain user : UUQ\ztest > > smb.conf for standalone samba : /home/hywu/smb.conf

On Thu, 25 Jan 2024 20:54:07 +0800 hhyy ww via samba <samba at lists.samba.org> wrote: > Rowland Penny via samba <samba at lists.samba.org> ? 2024?1?25? ?? > ??6:42??? > > > On Thu, 25 Jan 2024 18:27:48 +0800 > > hhyy ww via samba <samba at lists.samba.org> wrote: > > > > > Hi list, > > > > > > My case : > > > Local

more specific on what your problem is? cheers, jerry --------------------------------------------------------------------- http://www.valinux.com/ VA Linux Systems gcarter@valinux.com http://www.samba.org/ SAMBA Team jerry@samba.org http://www.plainjoe.org/ jerry@plainjoe.org --"I never saved anything for the swim back."

... (port 138, setting options)... [2001/07/10 20:11:23, 3] nmbd/nmbd.c:(541) open_sockets: Broadcast sockets opened. [2001/07/10 20:11:23, 2] lib/interface.c:(85) added interface ip=141.43.132.161 bcast=141.43.132.191 nmask=255.255.255.192 [2001/07/10 20:11:23, 3] lib/util_sock.c:(832) bind succeeded on port 137 ... (port 138, setting options)... [2001/07/10 20:11:23, 2]