similar to: samba 3.0.24 works - samba 3.0.25 fails

Hi Folks, Recently (I believe since recent 3.0.x releases), I have been unable to login to a Samba instance using CIFS (Linux mount) or Windows 2003. If I change the smb.conf from: security = server to security = user I _can_ login again fine. The NT PDC always replies with NT_STATUS_LOGON_FAILURE. It's event viewer shows that the proper username is being used, but that the password is

Hi all, I had linux samba 3.0.10 running as PDC of my domain which does only authentication for other linux samba boxes which are providing access to shares. After upgrade of PDC to Debian Lenny + samba 3.2.5 I've lost guess access to the shares which are run by samba 3.0.x boxes, while it works on samba 3.2.5 samba box. the scheme is like following :

Hi, I am new to samba. I have configured password server to authenticate centos users. But i got the following errors and not authenticating. [2007/10/29 02:48:24, 1] auth/auth_server.c:check_smbserver_security(363) password server WINDOWS rejected the password following is my smb.conf [global] workgroup = WINDOWSAD server string = Samba Server security = SERVER password

We run Samba, but wish to authenticate against Windows DC. We do this using the "security = server" mode. We don't have the option of being part of the Windows setup directly. Although authentication is done against Windows DC (so users are not prompted for passwords) users do need a Unix account to use the service. We have users in multiple Windows domains, and the DCs we

I'm running 3.4.6 (was running 3.0.28a but upgraded in hopes to fix this issue). Clients running Windows 7 that are NOT joined to the AD domain (samba authenticates against it via "security = server") cannot authenticate to access the server. Clients running Windows 7 that are on the domain as well as Windows XP, Windows 2003 on and off the domain work as expected. Any help would

Just the beginning of a question to anyone who might have experienced the following issue with Samba 3.0.2[5-6] series. We currently have service accounts accessing Samba shares on AIX 5.3 servers ( from TL04 - TL06 ). Most of the processes access the shares via UNC rather than mapped drives. After completing the upgrade to Samba 3.0.26a on the production side, the service accounts started

Hi, I''m confused about managing field boosting ... I have set the :boost for the :name field in my docs to 10, via :boost => 10 Then I performed a search for ''keith'' over all fields via with *:(keith*), expecting a doc with Keith in the :name field to come out on top. But another doc with Keith mentioned in other fields (:comments, :address) scored higher. I

On 5/23/24 22:58, Andrew Bartlett wrote: > Can you post your smb.conf. Actually no, as I don't have *one* smb.conf. I'll add three of them (the last three were I had this problem) at the end of this email. As you can see they are not exactly identical. > Have you used any of our fallback VFS modules instead of xattrs? I'd say not, but see the smb.confs. > (This would

Folks: Having an issue with samba 3.0.24 on a Sun Sparc Solaris 10 box compiled with gcc version 3.4.6. On these systems I'm constantly getting the following two lines in the log.smbd file: [2007/04/16 10:20:19, 0] param/loadparm.c:map_parameter(2690) Unknown parameter encountered: "client code page" [2007/04/16 10:20:19, 0] param/loadparm.c:lp_do_parameter(3420) Ignoring

Hello list, I have trouble with a smb configuration that worked fine before I upgraded my samba to the latest stable release. I used samba 3.0.23c (Slackware11) and now I'm using samba 3.0.25b (Slackware12). The error/failure looks like this: I'm trying to connect to my HOME service and I fail. The log produces only this: [2007/08/13 10:29:33, 1]

Hi, I've some problems with one of our samba fileserver (debian stable 3.0.14a-3sarge1). Every few weeks, I get the following error messages for all users that want to access/mount a share: [2006/03/16 08:52:53, 2] auth/auth.c:check_ntlm_password(312) check_ntlm_password: Authentication for user [PID51C9] -> [PID51C9] FAILED with error NT_STATUS_LOGON_FAILURE [2006/03/16 08:52:57, 1]

Hi, periodically we are seeing the following error in our samba log. At this time nobody can connect to the shares of this server anymore. [2007/04/17 09:05:59, 2] auth/auth.c:check_ntlm_password(312) check_ntlm_password: Authentication for user [PID33C1] -> [PID33C1] FAILED with error NT_STATUS_LOGON_FAILURE [2007/04/17 09:06:03, 1] auth/auth_server.c:check_smbserver_security(263) the

Hi, I am new here on this list, and have a problem of which I hope that somebody here can help me with it. I have a Voipbuster account, with which I would like to make phone calls via my Asterisk PBX. If I let X-Lite register directly at voipbuster.com, everything is OK, but if I let Asterisk register there, it says "registration for XXXXXX@sip.voipbuster.com timed out, trying again",

Installed Samba 3.0.10 via 'pkgadd' on Solaris 2.6 workstation s080 (137.223.31.80) - previously running Samba 2.2.8 which has worked for a long time. Samba 3.0.10 smb.conf file - changed to security =DOMAIN from SERVER at 2.2.8 version password server = 137.223.33.45, 137.223.33.72 - these are DCs # Samba config file created using SWAT # from 127.0.0.1 (127.0.0.1) # Date:

Hi All, Fedora Core 26 # rpm -qa \*samba\* samba-common-4.6.7-0.fc26.noarch samba-common-libs-4.6.7-0.fc26.x86_64 samba-4.6.7-0.fc26.x86_64 samba-client-libs-4.6.7-0.fc26.x86_64 samba-winbind-modules-4.6.7-0.fc26.x86_64 samba-libs-4.6.7-0.fc26.x86_64 samba-client-4.6.7-0.fc26.x86_64 samba-common-tools-4.6.7-0.fc26.x86_64 samba-winbind-4.6.7-0.fc26.x86_64 I am replacing a CentOS 5 Samba Server

Hi All, since an upgrade from 3.0.24 to 3.0.25 on 2 separate sun solaris (v3.8,v3.9) boxes I have experienced an inability to authenticate. $ smbclient -L //serverbox -U username Password: session setup failed: NT_STATUS_LOGON_FAILURE My global config is as follows: workgroup = WORKGROUP server string = SERVERBOX Samba Server security = SERVER obey pam

I have some stuck channels that I think I'm going to have to bounce Asterisk to get rid of, but am curious to know what they are and how they've managed to accumulate. The show up with a channel identifier of '(None)' as in the output below, and do not show up in the soft hangup list, and so can't be cleared by that method. Here is the output from iax2 show channels:

On 08/19/2017 12:31 AM, Rowland Penny via samba wrote: > On Fri, 18 Aug 2017 19:53:26 -0700 > toddandmargo via samba <samba at lists.samba.org> wrote: > >> Hi All, >> >> Fedora Core 26 >> >> # rpm -qa \*samba\* >> samba-common-4.6.7-0.fc26.noarch >> samba-common-libs-4.6.7-0.fc26.x86_64 >> samba-4.6.7-0.fc26.x86_64 >>

I'm having a very annoying problem I can't figure out. I've been running Samba4 as our office AD/DC for several years. This is a recent problem. Whenever I Remote Desktop into a particular Windows workstation (192.168.0.4) I get the following message in /var/log/samba/log.samba: Auth: [Kerberos KDC,ENC-TS Pre-authentication] user [(null)]\[mark at HPRS] at [Thu, 17 Jan 2019

On Sat, 19 Jan 2019 19:03:58 +0000 Rowland Penny wrote: > > On Sat, 19 Jan 2019 13:37:18 -0500 > Mark Foley via samba <samba at lists.samba.org> wrote: > > > I sure could use some help on this. Perhaps this problem is due to a > > recent Windows update? > > > > I have determined that whenever I log into the Windows 7 host > > DBSERVER from any