similar to: Login from XP problem

Hello I can do wbinfo -u and wbinfo -g to see users and groups from our domain. But if I do getent passwd I only see local passwords (and acessing the shares from a winxp machine failes with incorrect name/password). What can be wrong? Thanks, Jonas

Hello. As I can see this post: https://jira.it.su.se/jira/browse/HEIMDAL-241, at least? Samba 4.0.0alpha5 supported Smart Card logon for Windows XP workstations. Current version (Version 4.0.0alpha14-GIT-77d959f+) does not support smart card logon on Windows XP workstation (but Windows 7 works well). I tried to compare Kerberos traffic examples from genuine domain controller and Samba's

Hello Everybody First I want to said thanks for the great job you've been done with samba4. I'm french and I live in Reunion Island near South Africa. Sorry if i'm english is wrong lol. Here my trouble. I follow the how to on the wiki samba. I successfully join the domain I create. But when I try to log a user on windows xp ( create via swat and configure in 2003 active

Am Mittwoch, 24. April 2019, 16:13:11 CEST schrieb Rowland Penny via samba: > On Wed, 24 Apr 2019 11:37:11 +0000 > > Rogerio Bettini <rogeriobettini at hotmail.com> wrote: > > Rowland, it was a typo. Sorry, I paste the smb.conf twice. > > I changed the smb.conf as you proposed, so: dns forwarder removed - > > yes it's in named.conf, and ntlm auth / lanman auth

Hi, I am unable to login to a samba system that uses kerberos to authenticate to ADS if the users password has expired on the ADS system or if "User must change password at next login" is checked on the ADS.. I get a "login incorrect" message on the linux system and the log file gives the following error: pam_winbind[3647]: request failed: Must change password, PAM error

Waiting Ubuntu 18.04. No extra compiling for MIT Kerberos need. There are all dependencies you need: # apt-get install acl attr autoconf bind9utils bison build-essential debhelper dnsutils docbook-xml docbook-xsl flex gdb libjansson-dev krb5-user libacl1-dev libaio-dev libarchive-dev libattr1-dev libblkid-dev libbsd-dev libcap-dev libcups2-dev libgnutls28-dev libgpgme-dev libjson-perl

On Mon, 2 Oct 2017 10:37:34 -0400 Gaiseric Vandal via samba <samba at lists.samba.org> wrote: > The auto enrollment messages seems to be indicate that the client > machine thinks it is connecting to an AD domain. > > The profile messages is indicative of a domain membership problem, > whether or not you are using roaming profiles. > > Workgroup method is probably

Hello, We are having some problems with logging on to several Windows XP Pro SP2 clients at several different sites running Samba 3.0.10 as domain server. The situation is that the "User name" and "Password" fields in the "Log On to Windows" window are greyed out on the Windows XP clients. The third field, "Log on to", where you can choose between the

I went back and re-installed on a clean VM of Ubuntu Server 16.04.3 and built Samba 4.7.4 with default configuration and it works just fine to change expired passwords at login. I should have tested this default configuration a while back. I was trying to use MIT Kerberos instead of Hemidal and had followed all the directions on this link:

The auto enrollment messages seems to be indicate that the client machine thinks it is connecting to an AD domain. The profile messages is indicative of a domain membership problem, whether or not you are using roaming profiles. Workgroup method is probably simplest-  although my past experience was that even at 5 machines managing multiple users on multiple machines gets tricky.     In

I am attempting to setup Samba 3.0.10 on a Windows 2000 Active Directory domain. The problem I'm having is getting Samba to configure correctly to get the Kerberos library. I've gone through previous posts and have tried doing what others suggested but I still keep getting the error of: "configure: error: libkrb5 is needed for Active Directory support" The current configure

Release Announcements ===================== This is the fourth release candidate of Samba 4.19.? 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.19 will be the next version of the Samba suite. UPGRADING ========= NEW FEATURES/CHANGES

Release Announcements ===================== This is the fourth release candidate of Samba 4.19.? 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.19 will be the next version of the Samba suite. UPGRADING ========= NEW FEATURES/CHANGES

Release Announcements --------------------- This is the first stable release of the Samba 4.19 release series. Please read the release notes carefully before upgrading. NEW FEATURES/CHANGES ==================== Migrated smbget to use common command line parser ------------------------------------------------- The smbget utility implemented its own command line parsing logic. After discovering

Release Announcements --------------------- This is the first stable release of the Samba 4.19 release series. Please read the release notes carefully before upgrading. NEW FEATURES/CHANGES ==================== Migrated smbget to use common command line parser ------------------------------------------------- The smbget utility implemented its own command line parsing logic. After discovering

Thank you Rowland for your answer . I reply inline. > > On Wed, 6 Feb 2019 15:20:56 +0400 > henri transfert via samba <samba at lists.samba.org> wrote: > > > Hello all, > > > > I've planned to upgrade a Samba DC from 4.6.7 to 4.9.4 . > > STOP! > > Do not do this directly, reports on here have shown that this will not work. > > You

Hi! I have been reading for about two weeks (maybe I'm reading on the wrong places). I have found as many documents as one could expect describind how to build a LDAPv3 server, or how to build samba with ldap. This far, I have failed, and have a BIG confution in the order in wich the things should go: In one document, they recommend this: samba -> ldap -> sasl -> kerberos

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================================= FreeBSD-SA-04:08.heimdal Security Advisory The FreeBSD Project Topic: heimdal cross-realm trust vulnerability Category: core Module: crypto_heimdal

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================================= FreeBSD-SA-04:08.heimdal Security Advisory The FreeBSD Project Topic: heimdal cross-realm trust vulnerability Category: core Module: crypto_heimdal

As we wanted to test last Samba version we had to compile Samba manually once 4.3.0 went out. As we wanted to continue to deploy Samba using system's package manager, we decided to built our own RPM. As I hate RPM, I had to learn. As I'm lazy, I tried to not waste too much time learning RPM. So I downloaded .spec from Sernet's package 4.2.x, I modified that .spec to match new Samba