similar to: security=server

Folks: I've got several systems attached to a 2003 domain where we use kerberos to authenticate. When I upgraded a system to the latest greatest samba things stopped working. Just to find where it happened in the different versions of samba I downloaded, built, & ran 3.0.23d to 3.0.25c using the same smb.conf file. Turns out the 2.0.23d and 3.0.24 works but from 3.0.25 on it fails.

Hi All, since an upgrade from 3.0.24 to 3.0.25 on 2 separate sun solaris (v3.8,v3.9) boxes I have experienced an inability to authenticate. $ smbclient -L //serverbox -U username Password: session setup failed: NT_STATUS_LOGON_FAILURE My global config is as follows: workgroup = WORKGROUP server string = SERVERBOX Samba Server security = SERVER obey pam

Hello, We're using samba 3.0.24 on a Linux box, to access and backup some XP boxes. smbclient access is okay, but there is something quite weird with the tar subfunction ----- $ smbclient //xpbox/Documents -U someuser -d 2 -Tc /tmp/tarfile . added interface ip=192.168.1.xxx bcast=192.168.1.255 nmask=255.255.255.0 session setup failed: NT_STATUS_LOGON_FAILURE ----- Smbclient does NOT ask us

Hi there I was using "username map" under 3.0.24 so that when I connected from DOM\jhaar under (ADS Win2K3) Windows, it was mapped to my local "jhaar" Unix account - with homedir "/home/jhaar", etc. However, when I upgraded to 3.0.25, I started getting NT_STATUS_LOGON_FAILURE errors - even when just trying to list the shares. This occurred using smbclient as well as

Hi all , I'm running Debian Etch . I just finished configuring SAMBA as PDC to authenticate against LDAP server which works. The system in question uses default debian etch packages. As My Linix/unix accounts can authenticate against it. The LDAP works. I Used the default shipped smbldap-populate script to setup SAMBA. Everything seems to work as Anonymous User or as user

Hello all, I got some updates for my centos 7 (core), but nothing for the sernet-samba-packages. But now, my (test) member server isn't accessable anymore. Its smb.conf: [global] netbios name = SERVERNAME workgroup = DOMAIN security = ADS realm = DOMAIN.EXAMPLE.COM dedicated keytab file = /etc/krb5.keytab kerberos method = secrets and keytab log level = 10

Hi. I have problems, when upgraded from samba sernet 3.0.24 to 3.0.25 (too early ?): 1) always must change password, when log in to windows XP professonall - samba 3.0.25 PDC - password expired 2) I can't browse widnows network on client machine - network broswer in WinXP don't respond - just hangs 3) I cann't priny any more to printers attached to another widnows machines

The bios of the server did not know about summer and winter time.. And your welkom ;-) if they were all this easy to fix ;-)) Greetz, Louis >-----Oorspronkelijk bericht----- >Van: lists at kiuni.de [mailto:samba-bounces at lists.samba.org] Namens Tim >Verzonden: donderdag 9 april 2015 16:19 >Aan: samba at lists.samba.org >Onderwerp: Re: [Samba] After Update Member Server

I updated all my servers to 3.0.25 early this morning. Everything seems 100% A-OK except for the most surprising thing, all my Windows and Macintosh clients, no problems. But I'm having severe difficulty with the 3.0.25 smbclient. If I use smbclient from 3.0.24 it too can connect to my 3.0.25 servers without issue. Its bizarre. Before I go into it let me say, I've got some 3.0.25

Help! (pretty please :) I'm still having the problem described below with samba-3.0.24. Here's an excerpt from the smbpasswd man page: When run by an ordinary user with no options, smbpasswd will prompt them for their old SMB password and then ask them for their new pass word twice, to ensure that the new password was typed correctly. No passwords will be

I use the sernet samba packages on debian sarge and have problems after upgrading to 3.0.25 with rid mappings. My rid configuration for 3.0.24 looks like this idmap backend = rid:ISC=500-100000000 idmap uid = 500-100000000 idmap gid = 500-100000000 after updating to 3.0.25 I get a core dump of winbind (log at the end of the post) with these settings. I tried to use the new configuration

Hi, I'm currently using v3.0.24 in production and all works well. I'm testing 3.0.25 to see if I'm going to have any problems with it if I have to upgrade. I have a problem with the "force group" setting if it is set to a local Unix group. This same setting works fine in 3.0.24 but I'm denied access to the same share in 3.0.25. If I comment off the "force

Good Day. In June, I posted a small query under the Subject of _odd smbpasswd / smbclient error from Linux to Solaris_ Briefly, a Solaris sparc server running 3.0.25a would not accept passwords from the Linux smbclient program if the password was 9 characters or greater. Instead, one would get this: session setup failed: NT_STATUS_LOGON_FAILURE but it worked fine with the Solaris sparc

Hi, I've been using samba for a while now with relatively simple configurations. I do however have a few questions: * When using encrypted passwords with samba, is it possible to authenticate users using the Unix user password(/etc/passwd)? * When using smbclient I get the error NT_STATUS_LOGON_FAILURE: added interface ip=192.168.1.1 bcast=192.168.1.255 nmask=255.255.255.0 Password:

We've updated from 3.0.24 to 3.0.25 and we've noticed some minor problems such as some clients had to reboot in order to mount the share. And the log is now showing this warning all the time: WARNING: Winbindd not running, mapping ids with legacy code [2007/05/17 08:57:37, 2] passdb/lookup_sid.c:sid_to_gid(1435) We are thinking to revert to the previous version 3.0.24 which works

Gerry, It looks like 3.0.25 breaks "stand alone/no winbind/no domain" servers. This is remeniscent of the 3.0.23b SID/GID problem. The only thing that jumps out at me is that you can't access your home share and other shares just quit working. Looking at the log files, I see this: [2007/05/14 15:24:55, 10] smbd/open.c:share_conflict(389) share_conflict:

Hello list, A change in smbclient between 3.0.24 and 3.0.25c breaks [1] the gollem filemanager [2] and maybe others. In particular folder creation is broken unless the folder is a top level folder on the share. To create a subfolder "level2" in the folder /level1 of a share gollem executes this command: /usr/bin/smbclient "//1.2.3.4/sharename" "-p139"

Hello, I've been testing out 3.0.25 before putting it into production and came across an issue. As a simple example.. in a share definition root preexec = echo "hey there, hi there, hello" > /tmp/hiya.txt works fine under 3.0.24 not so under 3.0.25, /tmp/hiya.txt isn't created. Cranking up the debugging and using some other similiar tests it seems to me that Samba is in

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

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