similar to: Pam support

On 2020-09-03 20:59, Rowland penny via samba wrote: > On 03/09/2020 19:09, freebsd--- via samba wrote: >> I having the same issue like: >> >> https://forge.univention.org/bugzilla/show_bug.cgi?id=47314 >> >> I have 2 samba servers running with nearly identical configs: >> >> ii? samba???????????????????????????????? 2:3.6.6-6+deb7u15 >> ii?

I have Samba Version 3.5.8-74.fc13 (Fedora 13) set up as the PDC for an NT domain. I have several Windows XP Pro and Windows 7 Ultimate workstations as domain members and everything is working fine. Domain users can log-in at the workstations, access shares on the Samba server and the other workstations, etc. I am in the process of adding Samba Version 3.5.8-76.fc14 (Fedora 14) as an additional

Hi, I have a simple setup with pam modules to use kerberos authentication (heimdal kdc) for various services, i.e. ssh/scp/sftp, ftp and others. I would like to connect my standalone smbd (no AD membership) to this system, but have problems to force smbd to use pam. local smbpasswd works spnego + kerberos works with a ticket but pam modules are not accessed at all In my test setup, local samba

On 17/03/15 10:13, Sense Zeng wrote: > And use ntlm_auth fail too: > > ntlm_auth --username=testuser > password: > NT_STATUS_LOGON_FAILURE: Logon failure (0xc000006d) > > > 2015-03-17 7:30 GMT+00:00 Sense Zeng <opaperjam at gmail.com>: > >> My AD server is Win2003. And my linux server is ubuntu. Samba version is >> 2:3.6.3-2ubuntu2.12 and

Hello, After an almost 19 year gap, I need to ask this list for help again :-) I have somewhat specific circumstances, where I think I can tolerate plaintext passwords on the wire as long as I get samba to authenticate against the system /etc/shadow (using PAM) in exchange. 0) I'm using Debian 8.4 (jessie), samba packages 2:4.2.10+dfsg-0+deb8u3. 1) I have created user smbtest with password

My AD server is Win2003. And my linux server is ubuntu. Samba version is 2:3.6.3-2ubuntu2.12 and 2:4.1.6+dfsg-1ubuntu2.14.04.7. They are join into the Win2003 AD as normal smb servers (not DC). After Win2003 DC autoupdate last week, I can't use smbclient access all samba server with NTLMv2: ~$ smbclient //172.16.3.13/share -U testuser Enter DOMAIN\testuser's password: session setup

And use ntlm_auth fail too: ntlm_auth --username=testuser password: NT_STATUS_LOGON_FAILURE: Logon failure (0xc000006d) 2015-03-17 7:30 GMT+00:00 Sense Zeng <opaperjam at gmail.com>: > My AD server is Win2003. And my linux server is ubuntu. Samba version is > 2:3.6.3-2ubuntu2.12 and 2:4.1.6+dfsg-1ubuntu2.14.04.7. They are join into > the Win2003 AD as normal smb servers (not

Release Announcements ===================== This is the third release condidate of Samba 4.13. This is *not* intended for production environments and is designed for testing purposes only. Please report any defects via the Samba bug reporting system at https://bugzilla.samba.org/. Samba 4.13 will be the next version of the Samba suite. UPGRADING ========= NEW FEATURES/CHANGES

Release Announcements ===================== This is the third release condidate of Samba 4.13. This is *not* intended for production environments and is designed for testing purposes only. Please report any defects via the Samba bug reporting system at https://bugzilla.samba.org/. Samba 4.13 will be the next version of the Samba suite. UPGRADING ========= NEW FEATURES/CHANGES

Release Announcements ===================== This is the fourth release condidate of Samba 4.13. This is *not* intended for production environments and is designed for testing purposes only. Please report any defects via the Samba bug reporting system at https://bugzilla.samba.org/. Samba 4.13 will be the next version of the Samba suite. UPGRADING ========= NEW FEATURES/CHANGES

Release Announcements ===================== This is the fourth release condidate of Samba 4.13. This is *not* intended for production environments and is designed for testing purposes only. Please report any defects via the Samba bug reporting system at https://bugzilla.samba.org/. Samba 4.13 will be the next version of the Samba suite. UPGRADING ========= NEW FEATURES/CHANGES

Take advantage of the fact that we can now detect the type of client during --tls=on in order to provide safe dummy content for plaintext clients without having to rewrite plugins to do so. Signed-off-by: Eric Blake <eblake@redhat.com> --- docs/nbdkit-plugin.pod | 4 +- docs/nbdkit-tls.pod | 5 +- filters/tlsdummy/nbdkit-tlsdummy-filter.pod

I may have a deficiency in understanding the procedure for ADS authentication with samba, but most of the server setup works so far. I have bound a Red Hat Enterprise 5 server to our windows domain, it shows up in DNS and ADS, I can ping it, but I can't get samba shares to be accessible to users, or even get the smbclient to return shares properly. wbinfo -g returns the domain groups

Once again: Samba always comes with its own users database. You have Samba so you have Samba users in addition of systems users. You have to use smbpasswd -a username. And telling that, I'm not asking you anything, I'm telling you what you have to do to solve your issue. 2015-11-04 11:28 GMT+01:00 Roger Wu <wu1004 at gmail.com>: > 2015-11-04 17:11 GMT+08:00 Rowland Penny

On 04/11/15 06:24, Roger Wu wrote: > Hi, Rowland, > > Thanks for your advise. I've been updated the version to 4.2.5, the > rpm query is as below, > but it still didn't work. > > [root at testcad16 samba]# rpm -qa | grep samba > sernet-samba-4.2.5-19.el6.x86_64 > sernet-samba-libs-4.2.5-19.el6.x86_64 > sernet-samba-libsmbclient0-4.2.5-19.el6.x86_64 >

[3000] type=friend dtmfmode=INFO insecure=yes canreinvite=no auth=plaintext host=dynamic allow=ulaw [2000] type=friend dtmfmode=INFO insecure=yes canreinvite=no auth=plaintext host=dynamic allow=ulaw i have declared these two users 3000 and 2000. they are registering successfully. problem is that

Release Announcements ===================== This is the fifth release condidate of Samba 4.13. This is *not* intended for production environments and is designed for testing purposes only. Please report any defects via the Samba bug reporting system at https://bugzilla.samba.org/. Samba 4.13 will be the next version of the Samba suite. UPGRADING ========= NEW FEATURES/CHANGES

Release Announcements ===================== This is the fifth release condidate of Samba 4.13. This is *not* intended for production environments and is designed for testing purposes only. Please report any defects via the Samba bug reporting system at https://bugzilla.samba.org/. Samba 4.13 will be the next version of the Samba suite. UPGRADING ========= NEW FEATURES/CHANGES

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

On 8/7/20 5:00 PM, Eric Blake wrote: > Take advantage of the fact that we can now detect the type of client > during --tls=on in order to provide safe dummy content for plaintext > clients without having to rewrite plugins to do so. > > Signed-off-by: Eric Blake <eblake@redhat.com> > --- I got a test working (although it still shows that we are bit awkward until nbdkit