similar to: Samba 3.0.2a + Win2K clients: unreliable share access

> hi all, > > my working samba-4.1.7 member of a samba3 domain (samba-3.5.3) failed > while updating to samba-4.2.0. Users were no longer able to access > shares because the trust account was broken. > > According to release notes (Winbindd/Netlogon improvements): > > For the client side we have the following new options: > "require strong key" (yes by

I have a RHEL 4.6 server with the Red Hat supplied Samba 3.0.25b-1.el4_6.4 packages (samba, samba-client, samba-common) installed. I was able to bind this server to our Active Directory forest but when I run "groups username" all I get is "username : domain users" despite the fact our users are members of multiple groups in our AD domain. However I can chgrp files/directories

hello I'm using Samba 3.0.21b-2 on RHEL4.1. All the machines are logging to a windows 2003 ADS domain server. The samba server is a ADS member of this windows 2k3 server and user's access log is recorded by using the audit module. I recently came into this trouble, when I connect to samba server from client, the smbd_audit suddenly got panic. Please advise me how to solve this

Hi, I just upgraded one of our samba BDC's (with LDAP back end on solaris 10) from 3.0.23c to 3.0.26a and can no longer mount shares. The error message I'm seeing in the samba logs is [2007/11/15 14:15:26, 1] auth/auth_sam.c:sam_account_ok(172) sam_account_ok: Account for user 'dbb' password must change!. [2007/11/15 14:15:26, 3]

On 30/04/2020 15:11, Edouard Guign? wrote: > > Hello Rowland, > > I had a look on message log, when the winbind stopped. > I found that an system update occured during the night, and then > Winbind did not restart properly. > > ... > /Apr 28 04:33:08 [localhost] yum[1232]: Mis ? jour?: > samba-winbind-clients.x86_64 4.10.4-10.el7// > //Apr 28 04:33:08 [localhost]

Hello Rowland, I had a look on message log, when the winbind stopped. I found that an system update occured during the night, and then Winbind did not restart properly. ... /Apr 28 04:33:08 [localhost] yum[1232]: Mis ? jour?: samba-winbind-clients.x86_64 4.10.4-10.el7// //Apr 28 04:33:08 [localhost] yum[1232]: Mis ? jour?: samba-winbind-krb5-locator.x86_64 4.10.4-10.el7// //Apr 28 04:33:09

Hi folks, Host - Debian Etch Workstation Guest01 - mail server for routing Guest02 - mail server, hostname01. localIP01, domain01 Guest03 - mail server, hostname02, localIP02, domain02 Guest04 - mail server, hostname03, localIP02, domain03 etc. all mail servers running postfix as MTA on Debian Etch. single (one) external IP with all ports forwarded to Guest01 except port 53 which is forwarded

Hi, After upgrading one of my samba servers from ubuntu jaunty (3.3.2) to karmic (3.4.0) I cannot access the shares any more. The server (FINTLEWOODLEWIX) is set up to check authentication via a PDC (IO), which is also running 3.4.0 (and has been before). Guest access is allowed so that any users without a local unix account will be granted read access. Valid users are allowed read/write. After

Hi, we have a very strange behaviour today. On of our clustered (by heartbeat) samba server don't want provide shares anymore. Every user is blocked with message "access denied". So I thought there is a problem with mapping of users/groups. But wbinfo / id / getent are working fine. Do I move the share to another node everything works fine - the shared folders and the smb.conf

No takers thus far. These are the Samba 4.2 changes to which I previously referred (https://www.samba.org/samba/history/samba-4.2.0.html) : For the client side we have the following new options: "require strong key" (yes by default), "reject md5 servers" (no by default). E.g. for Samba 3.0.37 you need "require strong key = no" and for NT4 DCs

I have two SAMBA PDC's with an OpenLDAP backend. My goal is to establish an interdomain trust between the two domains so that users from each backend can login to Windows systems by specifying accounts from either domain. I've followed the steps to establish the trusts and I can see accounts and groups using wbinfo and getent. I can access resources/shares from each domain but I'm

On Thu, 3 Jan 2019 19:15:48 +0530 VigneshDhanraj G via samba <samba at lists.samba.org> wrote: > Hi team, > > Upgraded samba from 4.7.x to 4.9.3, when i tried to connect my public > share using smb://ip/ through guest login in MAC my shares are not > listed if i am connected to AD. > > 2019/01/03 18:56:31.351985, 3, pid=1114, effective(0, 0), real(0, 0), >

I have my Mandrake 9.2 box running as a domain member for a W2K AD domain. This is a new problem or I'm missing something really obvious. Possible bug? Setup: Samba Server 3.0.1 = ANC-GENTOO Windows Domain = LABOR windows xp client = ANC-07-14927xp tim = Windows Active Directory Domain Acccount Getting this "check_winbind_security" error when trying to connect to Samba vai

Dear, on my debian system I upgraded samba from 4.5.16 to 4.9.5. My samba server is configured as domain controller. Now happens a strange thing. From a windows 10 client I'm able to login with a domain user without problem. But if I logout and try to enter the password for the same user, Windows tells me that the password is incorrect. To be able to loing, I've to select Other User,

> I just upgraded one of our samba BDC's (with LDAP back end on > solaris 10) from 3.0.23c to > 3.0.26a and can no longer mount shares. > > The error message I'm seeing in the samba logs is > > [2007/11/15 14:15:26, 1] auth/auth_sam.c:sam_account_ok(172) > sam_account_ok: Account for user 'dbb' password must change!. > [2007/11/15 14:15:26, 3]

Hi team, Upgraded samba from 4.7.x to 4.9.3, when i tried to connect my public share using smb://ip/ through guest login in MAC my shares are not listed if i am connected to AD. 2019/01/03 18:56:31.351985, 3, pid=1114, effective(0, 0), real(0, 0), class=auth] ../source3/auth/auth.c:192(auth_check_ntlm_password) check_ntlm_password: mapped user is: []\[GUEST]@[HS-MBP-3] [2019/01/03

Hello all :-) I have a Solaris 2.5.1 1.9.18p7 Samba server. I want to use an NT 4.0 SP3 server to do all username and password authentication. I have the following entries in the global section of the smb.conf file: [global] # workgroup = <Windows NT Domain Name> workgroup = DOMAIN01 # The NetBIOS name by which the Solaris Samba server is known. netbios name = SMBSRV

Hi all. We have big problem with adding new machine to our domain. 2 weeks ago we upgrade our machine to Debian 4 (etch). Than we automatic update our samba to version 3.0.24 (from debian package). We use LDAP backend for samba. When we try add Windows XP or Windows 2000 to our domain, we got this error message on client: Security database is corrupted. On server we have in log file log.smbd

Hi all, I have a domain member server 3.6.6 running on debian7, authenticating against another debian7 + samba 3.6.6 in DC-mode. Both servers have user-accounts and groups on LDAP and resolve posix users using libnss-ldap. The groupmap is living on LDAP as well. The domain member server serves a share with ACL enabled. I got the upgrade to 3.6.X and idmap-updates working, but the old

You may have included this in another email however I will ask anyway, did you set DNS to your server in the Linux and Windows clients? Can you check if a Windows Server can join? Can you use DNS management to check the DNS on you samba server? On Mar 28, 2016 2:15 PM, "Dale Schroeder" <dale at briannassaladdressing.com> wrote: > No takers thus far. These are the Samba 4.2