similar to: Lockouts caused by Samba

I am noticing a problem with Samba not dropping/removing file locks. Here's what I've got: Samba 2.0.6 on a Sun E450 running Solaris 2.6 PC running Win95 and WordPerfect 8 smb.conf is pretty much standard, with oplocks enabled. Here's what happens: A user will open a file, the lock will be set, and even when the file is closed, the lock remains (as confirmed by smbstatus). The

Hello all, We are troubleshooting an issue that when SAMBA is joined to a Windows domain controller as a member server that has password failure lockouts configured, the Windows security auditing does not show the "Caller Computer Name" in the event ID generated (4740). We are using Samba 4.6.2 from CentOS 7. We posted a Bugzilla at Red Hat here:

Greetings! I have the following configuration: Two PDCs with Fedora Core 4: PDC1 and PDC2. PDC1 trusts PDC2, respectively PDC2 is trusted to PDC1. I join an XP workstation to PDC2. After restart i can see both domains in the login screen domain combo box. I can logon to PDC2 , but not to PDC1, since the PDC2's /etc/passwd

Hi guys I setup my samba4 server with provision. (pdc1) Then I setup a DC using net vampire after rolling back to commit 62e0a74 to bypass mdw updates that broke net vampire. (pdc2) I had to manually add to the zone in pdc1 the follwoing records to get replication to work: I made all the modifications in named.txt to bind pdc2 IN A 192.168.48.236 <PDC2-GUID>._msdsc IN CNAME pdc2

Greetings! I have the following configuration: Two PDCs (Samba 3.0.21b) with Fedora Core 4: PDC1 and PDC2. PDC1 trusts PDC2, respectively PDC2 is trusted to PDC1. I join an XP workstation to PDC2. After restart i can see both domains in the login screen domain combo box. I can logon to PDC2 , but not to PDC1, since the

Hi, We've tried to set two servers PDC Samba 3 + OpenLDAP as following below: Network_1 192.168.42.0/24 Network_2 192.168.43.0/24 PDC1(PRJLINUX1) - 192.168.42.2 - NETBIOS NAME = PRJARQ6 PDC2(PRJLINUX2) - 192.168.43.251 - NETBIOS NAME = PRJARQ5 OpenLDAP 2.2.24 Samba 3.0.14a Backports Deban 3 Woody OpenLDAP: The servers are using the same DataBase and the PRJARQ6 is a Slave from PRJARQ5.

So finally I got the net vampire to work. I had to roll back to commit 62e0a74 bypassing all the updates done by mdw at samba.org for now. Now the replication PDC1 is the first domain controller created by provision PDC2 is the second is the second domain controller created by net vampire on PDC1 I added user using "net newuser testuser1" in few seconds it appeared on PDC2 using the

Hi there, we are pretty sure to have our Samba version 1.9.18p10 configured for running a logon.bat which mounts a SMB filesystem on Win95 client logon. Funnily enough we see the message "Win NT logon script: Executing logon script" but obviously this is not actually true, as the filesystem is not mounted after this message box (a DOS box flashes up briefly as well)... Excerpts from

According to the documentation, Samba 3 supports account lockouts (ie: bad password attempt 5 times will result in the PDC returning an NT_STATUS_ACCOUNT_LOCKED_OUT message, until the account is manually reset with pdbedit). This syntax I'm using appears to be correct, but I'm not actually getting actual account lockouts: pdbedit -P "bad lockout attempt" -C 5 - and - pdbedit -P

The release notes indicate support for bad password lockout policy starting with version 3.0.3 but I can't figure out how to enable it. I didn't see anything in the docs about turning it on. I also tried looking through all the options by using swat in advanced mode. How do I enable bad password lockout policy?

Using Samba 3.0.14a with multiple domain controllers across WAN links I discovered that account lockout policies are broke. My testing show's that account lockout policies are not stored in LDAP as one would think but in a local TDB file on that particular BDC or PDC. The result is I'm seeing errors in my logs and users are getting locked out. There appears to be no replication setup

Hi, I'm trying to track random account lockouts on the domain. Is there any recommendations for log level or log handling that let me see what machines/servers are locking the account? I'm using samba 4.5.5. as a DC (3 DCs). My current logging settings are: logging = syslog log level = 1 auth:5 passdb:5 winbind:5 Att, Vinicius

On 3/23/2018 12:49 PM, Vinicius Bones Silva via samba wrote: > Hi, > > I'm trying to track random account lockouts on the domain. Is there > any recommendations for log level or log handling that let me see what > machines/servers are locking the account? > > I'm using samba 4.5.5. as a DC (3 DCs). > > My current logging settings are: > > logging = syslog

Hi ! If someone could help me.. I'm trying to ask my server to validate password on a first pdc in domainA and on a second PDC in domainB. However, when I set password server in smb.conf like this : password server= PDC1, PDC2 It only validating from PDC1.. I think that samba suppose that PDC2 is a bdc of PDC1. Any suggestion ? Excuse my poor english, it's not my native language.

I have four domains in my LAN. I set up trust relationships for the domains, having each PDC working as wins server for each domain but I hd not set up winbind. I have samba3-3.3.12 + ldap (openldap 2.4.21) as users backend. I mean, I have wins support = yes for each PDC, and I can access to the shared folders of each PDC from any windows computer from my LAN. The problem is accessing to

I have the following scenario: PSTN gateway (202.180.nnn.nnn) -> OpenSER 1.0.1 (147.202.nnn.nnn) -> Asterisk 1.2.16 (203.89.nnn.nnn) When an incoming call is received, often (but not always) Asterisk repeatedly sends a SIP 200 OK message and eventually hangs up the call. sip.conf [general] port = 5060 ; Port to bind to (SIP is 5060) bindaddr = 0.0.0.0 ; Address to bind to (all

Hi, We are having some replication issues between the our PDC and BDC LDAP servers. Here are the details Servers: Name: LIN-PDC1.LIN Role: PDC SLAPD: openldap-2.4.28 Samba: 3.6.25 Name: LIN-PDC2.LIN Role: BDC SLAPD: 2.4.31 Samba: 4.3.11 LDAP Method: cn=config with smbldap tools Database: HDB Management: PHPLAMDIN Replication Method: refreshAndPersist Replication: After importing the LDIFs

I'm running tinc 1.1pre11 with AutoConnect set to 'yes' and I recently started seeing lots of these messages on my VPN and cannot connect to various hosts from other hosts: (I have obscured the hostnames and vpn name, but otherwise this is a direct paste from syslog) Aug 19 14:51:51 AAA tinc.nnn[2217]: Got REQ_KEY from XXX while we already started a SPTPS session! Aug 19 14:51:54 AAA

Hi Jayson, I forward your request to the right place. Carlos (or some other) will have an answer, or at least some questions for you. -- Arnaud 2008/6/27 Jayson Anderson <jayson.anderson at gmail.com>: > Greetings Arnaud, > > I wrote you some time ago about whether NUT would support the Belkin > F6H550-UPS device in the future. > > You had replied and mentioned to send

Hello ... I am trying to run winbindd on my SuSE LINUX V8 system. When I start windbindd I eventually get the following message: 'winbind uid range missing or invalid' then winbindd ends. I noticed that I am not the only person getting this message. When I search "google.com" for this message, many others are getting this message. However I have not found any answers