similar to: XP error code 1326 on share (but smbclient works)

On Fri, 09 Jun 2017 19:35:08 +0200 Andrea Vai via samba <samba at lists.samba.org> wrote: > Hi all, > I am new to this list and I am not an expert, so please be patient > with me :-) > > I am trying to make a samba share working, between a samba standalone > server v.4.5.10 (Fedora 25) and a winXP SP3 client. > > The share should be writable by an authenticated

Hi Rowland, I followed your suggestions and changed the smb.conf file. Currently my smb.conf file looks like below. [global] workgroup = SAMDOM security = ADS realm = SAMDOM.LOCAL wins server = SAMDOM.LOCAL password server = SAMDOM.LOCAL domain master = no local master = no preferred master = no idmap backend = tdb idmap config *:range =

Hello list - I am not sure my messages are getting out to the list, so I will attempt in this message to summarize the problems I am having that have been the subject of a few other posts. I recently upgraded from a command-line Slackware installation to Debian Jessie. As part of that exercise, Samba was upgraded from 3.5.x to 4.1.17. My upgrade method was probably not idea: I recursively

Hai, Have you seen : https://wiki.samba.org/index.php/Authenticating_Freeradius_against_Active_Directory Test with : ntlm_auth --allow-mschapv2 --request-nt-key --domain=COMPANY --username=domainuser --password=userpassword Greetz, Louis > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens Oleg > Blyahher via samba > Verzonden:

Hi Daryl, > I recently migrated our samba PDC to an LDAP backend on a test machine. > Testing my account policies, I found out that the password lockout did not > work. bad password lockout works fine in Samba AD mode. Is there a technical reason for you to keep on using PDC NT4 mode? In AD mode, you'll also get a LDAP, and it will be much easier to setup and manage! By the way,

Hi there, I'm trying to get FreeRADIUS to authenticate against my Samba DC. It's Samba 4.7.6-ubuntu running on Ubuntu 18 (kernel version 4.15.0-66-generic). It came nicely packaged with Zentyal, which provides a nice GUI for managing a domain, as well as a CA and lots of cool small features. That same Zentyal also includes support for FreeRADIUS (3.0.16). This is my smb.conf:

I found out the answer to why the bad password count was failing by following the stack trace If anyone has the same problem, this was caused by my access rights being too restrictive. source/passdb/Init_sam_from_ldap.c:1064 => There is a "goto fn_exit;" in case ldapsam_get_entry_timestamp() fails before the cache is read via login_cache_read. This function will fail if it cannot

Hi Denis, Thanks for your suggestion When I looked into Samba4 AD, I figured it would take too much effort to port our infrastructure to it, seemingly without benefits We already have a quite extensive network architecture with OpenLDAP acting as a LDAP server. Samba4 AD seems to require its own LDAP implementation (and some more quirks IIRC). There's also the additional DNS configuration

Hi, - OpenSuse 42.2 - Samba Version 4.4.2-11.3.1-3752-SUSE-SLE_12-x86_64 I'm using samba for file sharing, where users have some control of the shares. This is a standalone server All works fine, the user was created and added on the samba host with smbpasswd -a <user> *The problem is*, when the samba password is changed using smbpasswd <user> , the Windows machines no

I recently migrated our samba PDC to an LDAP backend on a test machine. Testing my account policies, I found out that the password lockout did not work. When authentication fail, samba seems to call init_ldap_from_sam asking to update the bad password count. When I set the lockout threshold to 1, the account is locked after a failed attempt and the badPasswordCount attribute is updated correctly

On Tue, 23 May 2017 16:34:29 +0200 Asbjorn Taugbol via samba <samba at lists.samba.org> wrote: > Yes, the users exist as both Linux and Samba users. My question was > if the Windows client user "Admin" also needs to be Linux and Samba > user. > There is no windows user called 'Admin', there is one called 'Administrator', if it is the later, then it

I am thankful for all support received so far and I feel I'm getting closer to a solution. To get back to basics and a more transparent setup I have made a clean Ubuntu 16.04 installation and followed this guide https://wiki.samba.org/index.php/Setting_up_Samba_as_a_Standalone_Server Windows clients users are logged in with username Admin (local account, administrator). The samba share is

I upped 1.0.4 of the script.. I added checks if no DC's are found, error message and exits script, so no python errors anymore, if i did it right. ;-) on both DC's do the following. and whats the output of : cat /etc/hosts cat /etc/resolv.conf and kinit Administrator SETDNSDOMAIN=`hostname -d` SETHOSTNAME=`hostname -s` SERVER_IP_ADRESS=`hostname -i` echo "Test domainname:

Hello, I'm trying to change my passwod when an user in log on his session XP. But at the closure of the session I see this in the log : ntlm_password_check: Checking NTLMv2 password with domain [TEST] ntlm_password_check: Checking NTLMv2 password with uppercased version of domain [TEST] ntlm_password_check: Checking NTLMv2 password without a domain ntlm_password_check: NTLMv2

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

Hai Bob. SETDNSDOMAIN='hostname -d' needs to be: SETDNSDOMAIN=`hostname -d` .. so change them all . SETDNSDOMAIN=`hostname -d` SETHOSTNAME=`hostname -s` SERVER_IP_ADDRESS=`hostname -i` and you can ignore : >[....] Stopping domain name service...: bind9rndc: connect failed: >127.0.0.1#953: connection refused > >. ok > >[ ok ] Starting domain name service...:

I have some old boxes called Auditron that use an ancient version of Windows CE. These clients worked fine on Fedora 19 with Samba 3. I have now upgraded to Fedora 22 and Samba 4, and now these old boxes no longer connect. This is the config file I am using that was working fine: # Global parameters [global] netbios name = MEDIA server string = %v Samba on %h

On Fri, 2 Jun 2017 17:25:43 +0530 Srikar Somineni <srikars at vedams.com> wrote: > Hi Rowland, > I followed your suggestions and changed the smb.conf file. > Currently my smb.conf file looks like below. > [global] > workgroup = SAMDOM > security = ADS > realm = SAMDOM.LOCAL > wins server = SAMDOM.LOCAL > password server =

Vista32 3.0.25pre2 (I understand vista patches for "share level" are already in) security = share (with "valid users" on share definition) host msdfs = no user/pass in smbpasswd file. If I use "connect network drive..." method with "connect as another user", then it will always work. If I use start, search , \\server\share and then type user/pass in

Hello all, I recently purchased a Cisco 7940 IP phone to do some testing with (to validate a migration to asterisk for our internal PBX needs). I understand that I need to update the phone for it to support SIP, so I configured the phone with an IP address and pointed it at my tftp server. When I reboot the phone I am currently getting "TFTP File Not Found SEPDefault.cnf" in the