similar to: Endless Password Expiration in 3.0.25

Hi all! Im having a problem on my network when users try to logon. After trying to logon the follow error is generated on the log.user file. smb_password_ok: NT MD4 password check failed to correct this problem what I done was change the login password in smbpasswd for that user to the same password used on the station. (smbpasswd user ) But how to make any passwd change on the clients to

Hi. I have problems, when upgraded from samba sernet 3.0.24 to 3.0.25 (too early ?): 1) always must change password, when log in to windows XP professonall - samba 3.0.25 PDC - password expired 2) I can't browse widnows network on client machine - network broswer in WinXP don't respond - just hangs 3) I cann't priny any more to printers attached to another widnows machines

I have compiled Samba 3.0.25a from source on a Solaris 10 machine. I had previously been testing Samba 3.0.24 (from packages on www.sunfreeware.com) and have reused the smb.conf file. Otherwise this is a clean setup, not an upgrade. The server is configured as a PDC for my domain "SAMBADOMAIN" I created a samba password for the local root and administrator accounts. I joined the

Hello, I'm trying to use rpcclient to add a driver to a Samba 3.0.25 running on Gentoo. When I run the script below, rpcclient prints out the same message as if "--help" was submitted as the only switch. #!/bin/bash -x RPC="/usr/local/samba/bin/rpcclient" ARCH='Windows NT R4000' #ARCH='Windows NT x86' DRIVER='HP LaserJet 4Si/4Si MX

Hi, I'm currently using v3.0.24 in production and all works well. I'm testing 3.0.25 to see if I'm going to have any problems with it if I have to upgrade. I have a problem with the "force group" setting if it is set to a local Unix group. This same setting works fine in 3.0.24 but I'm denied access to the same share in 3.0.25. If I comment off the "force

Dear all, Hi. This is imacat from Taiwan. We have just upgraded from Samba 3.0.24 to Samba 3.0.25, as the samba-announce suggeseted ("... is the version that servers should be run for ..."). We are running Samba as our PDC and only server in our domain. My environment is: x86_64, Debian 4.0 r0 Etch, kernel 2.6.18, gcc 4.1.2, glibc 2.3.6. Before upgrade I have read the

I have am hitting a wall with pdbedit, as shown below. Any workarounds would be greatly appreciated. I am encountering the inability to change any users (profile) SID on Samba 3.x for Linux and BSD, which causes the accounts to no longer recognize their local Samba 2 profiles once they join Samba 3 domain. If I add a new user and pdbedit -a user -U SID it ignores the -U. The old profiles appear

Good morning, I have a working Offline Files setup w/Samba 3.0.24 (FreeBSD 6.2 host OS) and a Win XP SP2 client. Upon updating to Samba 3.0.25, the XP client's offline cache would show (as viewed via the Offline Files Folder) that synced files are write-only ('User W' in the Access column). When offline, theses files appeared to be available via Explorer and double clicking would

Dear all Off topic to some extent but Ted Harding has just called me to say he is (a) seeing large delays in the list messages when it is sent internally from hypatia.math.ethz.ch. I get only a delay of an hour which is reasonable in the scrap below but Ted reports delays of the order 24 hours, (b) messages he has sent to the list don't appear on it for a long time. Is anyone else

I have a Samba PDC in a one way trust relationship with a Windows Server 2003 DC such that Samba is the Trusting Domain. With Samba 3.0.23d I always used to leave winbindd running during a restart of smbd/nmbd. With 3.0.25, I have found that the domain "breaks" if I do this. Denote the Samba domain by SAMBA and the (trusted) Windows domain WINDOWS. When the domain "breaks",

we are migrating our standalone Samba sever (3.0.14a) on a Solaris 10 box to an RHEL 6.3 box. Testing shows that on Solaris 3.0.14a works with both the OpenLDAP server we are currently using and the IPA2.2 server as LDAP backend. But 3.5.10-125.el6 on a RHEL 6.3 box does not work with either. I can still map a share with 3.5 as owner of the shared directory, but secondary group ownership does

I have been working to get pdbedit to expire passwords. I have seen several bugs related to pdbedit (bugzilla bug 4630 for example) on 3.0.25 so I upgraded to 3.0.25a, the latest Samba version as of this writing. What I am trying to do is set a particular user's password to expire on a certain date. If that can't be done, the ability to set it to expire "now" would be my

Hello all, I've tried everything I can think of, I've gone through Google and the Samba website and I can't come up with a fix for this problem. I've been running Samba 3 for at least the past year with no problems. I run a small FreeBSD 6.2 box that I use as a storage area for the windows XP systems on my network. Things have been fine up until 3.0.25 and 3.0.25a. Now,

To anyone who uses the Match() function in the Matching library... How do you go about deciding how many matches you will use? With my data, my standard errors generally get smaller if I use more matches. Speaking of standard errors, when correcting for heteroscedasticity, how many matches do you use (this is the Var.cal option). It seems to me that it might make sense to use the same number

By mistake or by design membership in a Windows Primary Group seems to be mandatory! We are using printservers configured as member servers of Samba domains. with the following configuration security = DOMAIN password server = PDC encrypt passwords = yes map to guest = Bad Password The Samba PDCs use plain smbpasswd files. Since upgrading to 3.0.25 and

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Folks, I've cobbled together the svn commits for SAMBA_3_0_25 that address a few very visible bugs in 3.0.25: * The object picker error for "security = domain" * Supplementary group membership bug with "force group" * Premature password expiration on Samba DCs You can grab the patch file from

Hi everybody, I'm having a problem with winbind creating 2 entries for some of my users that really wrecking my head ;-/ . My situation is as follows : I have a typical Samba (3.0.14a)/LDAP setup. I have a trusted domain (another Samba/LDAP setup) and use winbind to map the users from the foreign domain, with the UID to SID mappings stored in LDAP . This works very well. The relevant part

Hi, I'm new to the list, I hope i'm posting at the right place ;) I'm having a hard time trying to update and to move my Samba 2.2 PDC to a new Debian server. Currently, the PDC is using Samba 2.2.8 on a Solaris Server. My goal is to move it to another computer, and to update it to a newer version (3.0.24) This must be fully transparent for the users, since I have no time to

This was dicovered in openssh-2.9p2 on BSDi 4.1. If you configure --with-ssl-dir and give a relative path (like ../openssl-0.9.6b), it will not compile because that path is no longer valid once it cds to openbsd-compat. In the CPPFLAGS variable in openbsd-compat/Makefile, you can put in another ../ (-I../openssl-0.9.6a/include becomes -I../../openssl-0.9.6a/include) and it works. Perhaps there

Hi, I can authenticate with the smbd from macos 10.12 using smb 3.6.25 inside a vm running on the same machine. smbclient -L 192.168.0.87 -U username --signing=off works. But when using the same command from a different PC i get NT_STATUS_LOGON_FAILURE. It is the same client setup. Any clues? Markus  <div style=\"border:0;border-bottom:1px solid black;width:100%;\">