similar to: smbclient inconsistant auth issue

I have a number of Samba servers on RHEL (Samba 3.0.33) in an AD environment using a mix of Windows 2008 and windows 2008 R2 servers. Configuration file is pretty minimal: [global] workgroup = AVWORLD security = DOMAIN log file = /var/log/samba/samba.log max log size = 500 wins server = 10.50.4.31 dns proxy = no #log level = 10 log level = 3 passdb:5 auth:10

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,

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

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]

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

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

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

I am experiencing slowdown due to changes introduced after 3.0.1 to the various DC lookup routines. I have it narrowed down but don't know where to go from here. First the relevant pieces of the conf: [global] workgroup = COMPANY.COM security = server log level = "4 auth:6" password server = SERVER1 SERVER2 wins server = 10.0.0.29 os level = 0 domain /

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

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

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 >

Hi. I'm using CentOS 5 with samba3x packages (Samba 3.5.10) and Solaris 10 (Samba 3.5.8) for achieving AD integration. Samba hosts are added as domain members. Now, I've tried to add CentOS 6, which also uses 3.5.10, but have encountered a problem -> users cannot authenticate for some reason. Configurations are pretty much the same across the board, and they look like this: #

Hello, Specifications of the environment: Samba 3.0.13 running on Solaris 8. This is configured as a domain member of a NT4 style PDC. The smb.conf file is provided for details. Problem definition: When trying to access the Samba server from a windows machine through network neighborhood, the system challenges the user for their credentials. On providing the username/password the system rejects

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:

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

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

To test gluster's behavior under heavy load, I'm currently doing this on two machines sharing a common /mnt/gfs gluster mount: ssh bal-6.example.com apt-get install dbench && dbench 6 -t 60 -D /mnt/gfs ssh bal-7.example.com apt-get install dbench && dbench 6 -t 60 -D /mnt/gfs One of the processes usually dies pretty quickly like this: [608] open

At a number of sites we are using Windows 2000 Server SP4 (APPSERVER) as a Terminal Server and a PDC. All user areas are stored on a NetBSD 1.6.2 server with Samba 3.0.7 using security = domain and a named password server. We've joined the domain from the Samba box (domain DOMAINNAME). In general everything works fine, but when a number of clients log on at around the same time (say 25 users