similar to: Samba 3.5 w/ Active Directory Share Authentication

I'm running CentOS 4.3 with the most recent samba-client and samba-common rpms. I've managed to configure samba/winbind to allow me to join the box to the AD, create the UID and GID mappings, etc. However, when I try to connect via ssh, the account cannot log in. /var/log/messages says the following: Sep 5 17:15:25 kdcdmz sshd[6263]: error: Could not get shadow information for

Hi, I have a case where I only want to restrict access to SMB shares via filesystem permissions (and POSIX ACLs). Therefore, I do not want Samba to verify security in any way at the SMB level. If the filesystem/ACL permissions allow access to the shared directory, so should Samba. If the filesystem does not allow access to the filesystem, Samba should deny as well. I thought I had this

Hi, My apologies for the newbie question/dumb-question-of-the-day but when searching the archives I couldn't see the wood for the trees :-/ Are there any good walkthroughs/RTFMs out there for troubleshooting getting samba to register DNS entries to an AD controller that requires secure updates? I have a CentOS 6 server that seems to be set up correctly. Initially it worked fine, but then

ok here's the situation; i've done this on 7 servers same either SLES 9 or 10, and all those work. i have a problem server though which is SLES v9 (same versions of all daemons/services that would be used) and this one just wont allow AD auth to work i can restart all smb, nmb, winbind, and ssh servers with no errors *Note: all the needed configuratoin file snippets are at the end of

I have started tinkering with samba 4. I have a Windows 2008 active directory domain controller. It is also the main DNS server but is not the wins server. The DNS server does NOT allow DNS registration by client machines. I have a fedora core 19 linux machine with samba 4.1.13 (bundled with Fedora.) smb.conf includes security = ads realm = MYDOMAIN.COM

W dniu 2019-09-16 o?16:30, Rowland penny via samba pisze: > On 16/09/2019 15:04, L.P.H. van Belle via samba wrote: >> Well it was worth checking.. We just dont know what you already >> checked.. now I setup the Ubuntu Server 18.04.3 LTS + http://apt.van-belle.nl/ + https://github.com/thctlo/samba4/blob/master/full-howto-Ubuntu18.04-samba-AD_DC.txt#L268 + i changed krb (default

I'm trying to join a RHEL 5 client to a Windows 2008 R2 AD, I've tried both Samba 3.6.6 and 4.0.2. When pointing the client to a RWDC(wegsfes19123) I'm able to successfully join the client: [root at vm-ae67a ~]# net ads join -U Administrator -d1 -Swegsfes19123 ... libnet_Join: libnet_JoinCtx: struct libnet_JoinCtx out: struct libnet_JoinCtx account_name

W dniu 2019-09-15 o?20:38, Rowland penny via samba pisze: > On 15/09/2019 19:08, Bart?omiej Solarz-Nies?uchowski wrote: >> W dniu 2019-09-15 o?18:32, Rowland penny via samba pisze: >>> On 15/09/2019 16:44, Bart?omiej Solarz-Nies?uchowski wrote: >>>> I have some questions: >>>> >>>> I not currently understood - bind9 connected to AD server must

Just saw that, as well. After running the commands to enable SMB2 & SMB3 and rebooting...no luck. Will keep searching for other registry settings. On Tue, Apr 19, 2016 at 3:27 PM, lingpanda101 at gmail.com < lingpanda101 at gmail.com> wrote: > On 4/19/2016 3:24 PM, Bill Baird wrote: > > When I search for "smb2", I get nothing in my log file for the NT1 limited >

I'm seeing the exact same behavior in my environment (NT4 PDC, not AD). I had to downgrade samba get systems working again. The full error message is: "The trust relationship between this workstation and the primary domain failed". Did you have any luck finding a solution?

On 16/09/2019 17:26, Bart?omiej Solarz-Nies?uchowski wrote: > W dniu 2019-09-16 o?16:30, Rowland penny via samba pisze: >> On 16/09/2019 15:04, L.P.H. van Belle via samba wrote: >>> Well it was worth checking.. We just dont know what you already >>> checked.. > > now I setup the Ubuntu Server 18.04.3 LTS + > > http://apt.van-belle.nl/ + >

On Sun, 16 Sep 2018 10:51:25 -0400 Bill Baird via samba <samba at lists.samba.org> wrote: > I ran the same thing with 4.8.5 and it work without any issues: > > Adding groups > Importing groups > Committing 'add groups' transaction to disk > Adding users > Importing users > Committing 'add users' transaction to disk > Adding users to groups >

*testparm -v | grep "client min protocol"* client min protocol = CORE On Tue, Apr 19, 2016 at 2:50 PM, lingpanda101 at gmail.com < lingpanda101 at gmail.com> wrote: > On 4/19/2016 2:43 PM, Bill Baird wrote: > > I am accessing the new member server. All my other servers are still on > 3.6.x. > > Both settings are set to "default". > > Will look at

On Sun, 16 Sep 2018 11:28:56 -0400 Bill Baird <Bill.Baird at phoenixmi.com> wrote: > Python is 2.6, but why wouldn't it throw an error during > configure/make? No, the python code isn't compiled. > > I'm using Amazon Linux. Would you like to raise a bug report ? Here: https://bugzilla.samba.org/ Rowland > > On Sun, Sep 16, 2018 at 11:22 AM Rowland Penny

When I search for "smb2", I get nothing in my log file for the NT1 limited system. If it is a workstation issue, that would be great. I'll search around for what settings to change. Maybe SMB2 was inadvertently disabled. Thanks for all of your help on this! On Tue, Apr 19, 2016 at 3:20 PM, lingpanda101 at gmail.com < lingpanda101 at gmail.com> wrote: > On 4/19/2016 3:11

Just to follow up, the fix for us was to add "client ipc signing = auto" to our smb.conf configuration file. On Wed, Apr 13, 2016 at 1:17 PM, Bill Baird <bill.baird at phoenixmi.com> wrote: > FYI: https://lists.samba.org/archive/samba/2016-April/199013.html > > On Wed, Apr 13, 2016 at 12:53 PM, Bill Baird <bill.baird at phoenixmi.com> > wrote: > >>

I tried disabling SMB1 and enabling SMB2/3 and after reboot, I can't connect to any of my Samba servers...so looks to definitely be a workstation issue. On Tue, Apr 19, 2016 at 3:32 PM, Bill Baird <bill.baird at phoenixmi.com> wrote: > Just saw that, as well. > > After running the commands to enable SMB2 & SMB3 and rebooting...no luck. > Will keep searching for other

I am accessing the new member server. All my other servers are still on 3.6.x. Both settings are set to "default". Will look at logs now. Thanks! On Tue, Apr 19, 2016 at 2:39 PM, lingpanda101 at gmail.com < lingpanda101 at gmail.com> wrote: > On 4/19/2016 2:08 PM, Bill Baird wrote: > >> Hi All, >> >> I just setup a new server and added it to my domain

That does indeed show "default". For logs, I tested with my system and a system that gets SMB2. Any tips for what I might be looking for? Early on in the logs, I see this for the NT1 system (no mentions of smb2 anywhere) [2016/04/19 14:48:37.738460, 3, pid=21479, effective(0, 0), real(0, 0)] ../source3/smbd/negprot.c:395(reply_nt1) using SPNEGO [2016/04/19 14:48:37.738476, 3,

Hi All, Attempting to do a classicupgrade and getting this error: *Adding groups* *Importing groups* *Committing 'add groups' transaction to disk* *Adding users* *Importing users* *Adding users to groups* *Committing 'add users to groups' transaction to disk* *ERROR(<type 'exceptions.ValueError'>): uncaught exception - zero length field name in format* * File