similar to: Samba 3.0.33, security = domain and Windows 2008 R2

I'm trying to configure a Fedora 7 machine to authenticate access to shares via AD. This works fine on other RHEL machines, but the same configuration on Fedora maddeningly does not. I've tried oodles of different configurations, and am currently using something based on: http://wiki.samba.org/index.php/Samba_&_Active_Directory Here is my krb5.conf file: [logging] default =

I'm trying to join my FC6 box to our Active Directory domain. For the most part the setup was pretty straightforward, but it just doesn't seem like winbind separator is being honored. When I do a 'getent passwd' I get the following: AVWORLD\johnXXXX:*:16782801:16777216:XXXXXXXX:/home/AVWORLD/johnXXXX:/bin/bash

My Question: ------------ Is it possible to get 2-way Interdomain Trust relationships working between a Samba domain and an NT4 SP6a domain, while restricting all password hashes to NTLMv2 only? Everything works except the inter-domain trust I'm able to get the NT4 domain to trust the Samba domain, but not the other way around. My System: ---------- I have a perfectly running Samba domain

Hello, I'm running Mandrake 9.2 and Samba-3.0.2a I'm connecting a Samba Server as a Domain member to an 2003 ADS, called TEST2. I've been able to create the computer account. I've also tested successfully, from Chapter 7 of ' Samba HOWTO Collection' with a W2K client logon/mount a share from the samba server using Kerberos. The testing of the smbclient was also

Running Samba mostly on Redhat 5 with version 3.5.4-0.83 Also failed on Debian 3.5.6 and Solaris with a 3.5 version. Logging details here are from Redhat case. We have a similar problem on all Unix/Linux systems using ADS as the backend authentication for samba shares on Unix/Linux. It was working before today and we didn't change anything. Today, any time we try smbclient or a Windows drive

I have an NT domain on Debian Stretch. It's been upgraded numerous times, but has been running for almost a decade. Since upgrading from 4.1.17 to 4.3.3 (huge Debian jump), then to 4.3.6, clients cannot connect to shares. Prior to upgrading, I found the changes mentioned for 4.2 regarding NT domains and applied them. Even so, I still cannot connect to network shares nor print to

Hi folks, we have a problem with a win2003 DC and Samba. The authentification of users from the dc works fine, but when we added users from a forest trust in a active directory localgroup, samba don't find the users... I post this problem here: https://bugzilla.samba.org/show_bug.cgi?id=5245 Maybe you can help. Cheers Paul -- Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu

Hi, I have deployed a new file server (Samba version 4.6.2, CentOS 7) which is running as a member of an AD domain (The DCs are both Windows server 2012, forest and domain level is 2012 as well). I'm using the AD backend to store SID/UID mappings. So everything is working fine except for one specific user on one specific workstation (Windows 10) who can only access the file server with

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'

You may have included this in another email however I will ask anyway, did you set DNS to your server in the Linux and Windows clients? Can you check if a Windows Server can join? Can you use DNS management to check the DNS on you samba server? On Mar 28, 2016 2:15 PM, "Dale Schroeder" <dale at briannassaladdressing.com> wrote: > No takers thus far. These are the Samba 4.2

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

Hi I have several Samba servers which have been running for almost two years without any problem. Recently I rebooted one of those servers and have the following problem: the join to the domain is OK but all user authentications fail. I mean nobody can "connect" a share. The system I rebooted is half of a two node cluster, the other node with exactly the same configuration, up 230 days,

Hi all, i have a samba-server in domain named "WW300" and a user from domain "WW002" tries to connect to one of my shares but fail. so i switched on logging and looked what happens: [2006/12/06 10:51:38, 5, pid=14054, effective(0, 0), real(0, 0)] auth/auth_util.c:make_user_info_map(225) make_user_info_map: Mapping user [WW002]\[E0420300] from workstation [E042017C]

trying to get one server to mount.cifs a share on another and when it failed I used smbclient and it lead me into this oddity and I just can't seem to reason my way through. so you can skim better in case this is too much info: the mystery: why does command #3 work from server1 against itself, but fail for all other clients? server1: samba 3.4.7 (Ubuntu 10.04 server), NT4 domain member

I have two samba servers with pretty much identical setups (same smb.conf, smbd, winbindd, libnss_winbind.so binaries), joined to the same domain, one of which works, one doesn't. I'm seeing smbd crashing when I try to connect to the problem server with the following information in the logs. OS is Solaris 10 update 5 samba is a repository snapshot that Volker pointed me at to resolve an

Hi A new setup Windows client fails to authenticate to my Samba server (3.0.24-SerNet-RedHat). What I see in log at level 10 is: Got user=[SA-MC-SMSNS@corproot.net] domain=[] workstation=[MSISMSSRV01P] len1=24 len2=122 The empty domain seams to be origin of the problem, for other systems working OK this field is not empty. The Windows client is: NativeOS=[Windows Server 2003 R2 3790 Service

New Polices created Denver policy is 1684 Atlanta Policy is 1441 IP address added 10.80.13.163 - this is allowed only to ATM services Jason Prouty CCT Manager Network Engineering 303-928-1588 Desk 720-412-1942 Cell ----- Original Message ----- From: "Davide Ianni via samba" <samba at lists.samba.org> To: samba at lists.samba.org Sent: Tuesday, January 16, 2018

Hi, My OpenIndiana (opensolaris) machine is joined to Active Directory. I'm using samba 3.6.12 from OpenCSW. wbinfo -u is working fine, getent was not working in the beginning, but after some fiddling with libraries it was working ( I had to create the following two symbolic links, not sure if they both are correct) /lib/libnss_winbind.so -> /opt/csw/lib/libnss_winbind.so.1

No takers thus far. These are the Samba 4.2 changes to which I previously referred (https://www.samba.org/samba/history/samba-4.2.0.html) : For the client side we have the following new options: "require strong key" (yes by default), "reject md5 servers" (no by default). E.g. for Samba 3.0.37 you need "require strong key = no" and for NT4 DCs

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 >