similar to: why auth3_check_password load smb.conf again

Hi, I set up samba on ubuntu 18.04 and join the windows AD (windows server 2016), it works fine. But when a windows client (windows server 2012R2) which only allows kerberos enctypt AES tries the access the samba server, windows AD report a kerberos error KRB5KDC_ERR_ETYPE_NOSUPP. The 'net ads enctypes list' command report the samba server support all the enctypes. 'dks4$' uses

Hello, Before all, in advance, I'm sorry for my bad english. I'm trying to automate the join of new computers (running Windows XP Pro) to my Samba (3.0.7) domain by using a unique ghost image and a windows sysprep "script" that retrieve the real name of the machine and try to join the domain with this name. It works well while trying to join a w2k domain, but with my Samba

I'm running FreeBSD 8 on a Sheevaplug (ARM5 processor) I compiled and installed Samba 3.3.9 from ports using defaults and defaults for dependencies. I left the smb.conf file untouched, ran testparm and immediately received the coredump. The same happens running smbd and nmbd. Can anyone help me resolve? http://old.nabble.com/file/p26879957/testparm.core.gz testparm.core.gz -- View this

> On 21 Dec 2018, at 09:54, David C. Rankin via samba <samba at lists.samba.org> wrote: > > Sambadevs, > > I don't know if this is a bug or just a spurious error message when using > smbclient (on a standalone config), but checking smbclient, I get: > > 02:47 2pi:~> smbclient -U% -Llocalhost > Unable to initialize messaging context > >

I'm trying to see what computer is accessing certain files through samba, and the SWAT status page is a useful tool for that. Problem is that for some computers, only the IP address shows, not the NetBIOS name. This is only a problem with certain computers. Since we're using DHCP on many computers I don't always know off the top of my head what computer has any given IP

Sambadevs, I don't know if this is a bug or just a spurious error message when using smbclient (on a standalone config), but checking smbclient, I get: 02:47 2pi:~> smbclient -U% -Llocalhost Unable to initialize messaging context Sharename Type Comment --------- ---- ------- samba Disk 2pi - Law IPC$ IPC

Vincent Le Toux <vincent.letoux at gmail.com> writes: > Typical example: > Here is some search & export for libsmbclient: > adiant at ubuntu:/usr/lib/x86_64-linux-gnu$ nm -D libsmbclient.so.0 |grep > cli_rpc_pipe_open_noauth_transport > <nothing> > adiant at ubuntu:/usr/lib/x86_64-linux-gnu$ nm -D libsmbclient.so.0 |grep > cli_rpc_pipe_open >

Dear Samba-experts: we migrated from Samba 3.6 to 4.18 and everything works well. But there are two problems where I need some expert-help: We are using a daemon that is running on our AD-server. It accepts connections from remote machines and changes the passwords of certain users. Calling system("smbpasswd") from within that daemon would be too slow so the daemon calls

Typical example: Here is some search & export for libsmbclient: adiant at ubuntu:/usr/lib/x86_64-linux-gnu$ nm -D libsmbclient.so.0 |grep cli_rpc_pipe_open_noauth_transport <nothing> adiant at ubuntu:/usr/lib/x86_64-linux-gnu$ nm -D libsmbclient.so.0 |grep cli_rpc_pipe_open U cli_rpc_pipe_open_noauth adiant at ubuntu:/usr/lib/x86_64-linux-gnu$ nm -D libsmbclient.so.0

OK, At a loss for what to try next. According to this page, it should be possible to make this work: http://www.hexblot.com/blog/centos-7-active-directory-and-samba However, I can't get AD users to authenticate when I run net use * \\cns-cryo-road1\my_share /user:austin\pgoetz Authenticating via ssh, su, or from the console using the same AD UserName is not a problem. It seems

Hi, I have added below lines in smb.conf idmap config CIFSDOM:backend = rid idmap config CIFSDOM:range = 10000-999999 But still i am getting same error. *I am also attaching logs * *winbind logs:-* userinfos: struct wbint_userinfo acct_name : * acct_name : 'gold'

Hey Guy's, When the user is 'joe at mds.xyz' login works fine on Win 10. Same user types on a Mac OS gives [ Mac OS - Fails ] [2020/02/21 00:03:16.960566, 5, pid=12382, effective(0, 0), real(0, 0), class=auth] ../source3/auth/auth_util.c:126(make_user_info_map) Mapping user [mds.xyz]\[joe] from workstation [SERVER-PBM] [ Win 10 - Works ] [2020/02/20 23:58:01.059514,

On Tue, 20 Dec 2016 22:33:56 +0530 Arjit Gupta <arjitk.gupta at gmail.com> wrote: > Hi, > > I have added below lines in smb.conf > > idmap config CIFSDOM:backend = rid > idmap config CIFSDOM:range = 10000-999999 > > But still i am getting same error. > > *I am also attaching logs * > > *winbind logs:-* > > userinfos: struct wbint_userinfo >

Mandi! Rowland penny via samba In chel di` si favelave... > You have 'allow trusted domains = No' in 'global' and from 'man smb.conf': I've had not noted that. I can confirm that my working setup had NOT 'allow trusted domains = No'. -- dott. Marco Gaiarin GNUPG Key ID: 240A3D66 Associazione ``La Nostra Famiglia''

On 2/21/2020 12:52 AM, TomK via samba wrote: > Hey Guy's, > > When the user is 'joe at mds.xyz' login works fine on Win 10.? Same user > types on a Mac OS gives > > [2020/02/21 00:03:17.050984, 4, pid=12382, effective(0, 0), real(0, 0)] ../source3/smbd/sec_ctx.c:438(pop_sec_ctx) pop_sec_ctx (0, 0) - sec_ctx_stack_ndx = 1 [2020/02/21 00:03:17.051095, 3,

Hi , Below is the content of smb.conf file for ADS member. [global] password server = WIN2008.CIFSDOM.COM client ldap sasl wrapping = plain security = ADS workgroup = CIFSDOM realm = CIFSDOM.COM guest account = smbnull log file = /var/log/samba/%m.log log level = 10 # Default idmap config used for BUILTIN and local accounts/groups

On Tue, 16 Jun 2020, Rowland penny via samba wrote: > On 16/06/2020 12:41, Harald Hannelius via samba wrote: >> I have Samba AD-domain with two fileservers and two Samba DS-servers. Most >> people can authenticate OK, but one user always gets "wrong password". > What versions of Samba ? All servers are 4.9.5-Debian. >> Auth: [SMB2,(null)] user [SAD]\[username]

Hi Rowland, *After stopping **pwgr daemon* we are able to access the domain user as expected. Below is the smb.conf file used. mach# ./testparm -s Load smb config files from /etc/opt/samba/smb.conf rlimit_max: increasing rlimit_max (2048) to minimum Windows limit (16384) Processing section "[tmp]" Loaded services file OK. Processing comments in /etc/opt/samba/smb.conf Server role:

On Mon, 24 Sep 2018 17:33:47 +0200 Marco Gaiarin via samba <samba at lists.samba.org> wrote: > Mandi! L.P.H. van Belle via samba > In chel di` si favelave... > > > I hope this helps you understanding your problem a bit more. > > See also: > > https://docs.microsoft.com/en-us/windows/security/identity-protection/access-control/local-accounts > > No,

I have a new CentOS 7 installation which I joined to my domain using 'realm join mydomain.com'. That worked great. I can get a ticket with 'kinit administrator at mydomain.com'. But my samba shares don't work. In fact, when I browse (from windows 7 domain member) to the host (lserver), it just times out. Similarly, when I try from another Linux server: smbclient