similar to: try 2: group setting doesn't work

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

Hi All, I'm posting this just in case someone can tell what's going on with samba that would prevent this from working. Cisco has the ability to see a smb share from their webvpn product with CIFS. We can browse windows shares but not samba shares. The following log outputs are from my ASA firewall. I know these are cisco logs but I'm hoping a lightbulb will come on for someone. The

Since I haven't gotten any responses from the segfault log I posted earlier, I will try another approach. Below is what happens when a client tries to connect. Again, this all started after I changed a username mapping entry from root = DOMAIN\Administrator to root = @"DOMAIN\Domain Admins". This is in a security = ADS setup. wbinfo -u and -g return the correct information.

Hi all, I've searched the list archives and found similar issues, but none of the resolutions I found worked for me. When I try to connect to my samba share with an Active Directory domain account, I get denied: $ smbclient -U SOTS+jason //media/tmp xxxxxxxx session setup failed: NT_STATUS_LOGON_FAILURE Looking at the log files I found this (complete file is posted below):

Hi, everyone. I need your help. I am administrating a not very big network of 7 computers. The server is Win2003 Server with Active Directory on it. The workstations are Mandriva 2007 free. I have configured samba, winbind and all the stuff, so it seams to be alright. But there is a big problem. All the workstations are samba file servers. When accessing a samba server from a linux PC, it

-------- Weitergeleitete Nachricht -------- Von: Kuldeep <kuldeep@turbolinux.co.in> An: Mario Lipinski <mario.lipinski@gymszbad.de> Betreff: Re: [Samba] Authentication fails (sometimes) Datum: Fri, 01 Sep 2006 09:34:17 +0530 Dear Mario, Can you tell me procedure for login on to domain(Windows server) linux client. I have joined in to domain but not able to login Mario Lipinski

I have a file server with two shares accessible to 2 different groups. After the last update ( from debian 2:3.2.5-4 to 2:3.3.2-1 ) i cannot any more access ONLY ONE of the two shares and I can't understand the reason! Can anyone hel me? I'm getting mad! Thanks Giorgio from smb.conf: [documenti_movi] path = /home/documenti_movi valid users = @staffmovi read

Hello, I am usually able to log me onto my domain. However, i have problems to get authentication under windows where I need admin rights, which also succeeds some times. I have the following in my groupmap: # net groupmap list admin (S-1-5-21-4092459118-2595994810-1099795350-512) -> admin guests (S-1-5-21-4092459118-2595994810-1099795350-514) -> guests gsb

Am 26.02.19 um 12:26 schrieb Ralph Böhme: > On Tue, Feb 26, 2019 at 11:19:45AM +0100, Alexander Spannagel via samba > wrote: >> The huge delays are seen, when user isn't known to sssd and winbind >> tries to look that user without explicitly a domain given and the >> option "winbind use default domain" is on it's default of "No" in >>

Hi! I've tried to compile samba 3.0.23rc2 --with-vfs-afsacl --fake-kaserver, but I've got errors. The first error and its solution is: I've to add -lssl to the LIBS line in the top level Makefile. Then I've got this: Compiling modules/vfs_afsacl.c with -fPIC modules/vfs_afsacl.c: In function `new_afs_ace': modules/vfs_afsacl.c:145: warning: passing arg 2 of

Hi, We have been running samba file server about 2 years without this problem. The problem appeared at the same time on our debian and centos servers. Not sure if it's related to any updates on our windows AD servers. Debian Squeeze sernet-samba-3.5.8-27 Centos 5.5 samba3-3.5.5-43.el5 Use Active Directory for user login authentication Use uid/gid from ldap The reason we still want winbind

Hi I'm using Samba 3.6.3 on ubuntu 12.04 as a domain member with AD on Win Server 2012. My hare is configured like this: valid users = @"EVSOFFICE.LOCAL+dangroup" When I try to connect to a share via IP from Win7 (part of the domain) it succeeds but when use host name \\node15 I can see shares but double-click on share shows AccessDenied. I'm trying to connect as

Hie, I can't connect to my samba 3.022 pdc (I can join the domain and access share) and no error messages. I find in the log : the dump_data message musn't be clearest (domain,netboisname...) ? An idea ? [2008/04/30 15:26:50, 5] lib/util.c:show_msg(464) size=627 smb_com=0x2e smb_rcls=0 smb_reh=0 smb_err=0 smb_flg=136 smb_flg2=51201 smb_tid=1 smb_pid=65279

Below is a log file of a panic that occurs on two different sites running Debian Stable Samba 3.2.5. The problem is triggered by Sophos Control Centre doing it's hourly check for updates, and as SCC is running on a user's PC in both cases causes problems for the user. I've tried everything and cannot figure it out - anyone got any pointers/ideas what to do next ? [2009/05/18

Hello All, I am having a very strange problem with samba 3.0.23c. I upgraded everything from 3.0.9 and I am able to smbclient to the samba 3.0.23c PDC with the administrator user just fine. When I go to add a machine to the domain, it adds the unix machine account to the ou=computers like it is supposed to but none of the samba entries are added. I get an error on the windows side of

Hi, When I use "valid users" in smb.conf to limit access on my share, I have this message with smbclient : [global] workgroup = MYDOM domain master = no local master = no security = user passdb backend = ldapsam:ldap://x.x.x.x:389 ldap admin dn = cn=admin,dc=company,dc=com ldap suffix = dc=company,dc=com ldap user

We've got nicely ADS integrated Samba-3.0.27a servers that are working fine with Win2000 through to standard Vista. However, we are starting to test RC1 of Vista SP1 and discovered that once applied, that workstation cannot connect to Samba server shares - unless the share is open - i.e. no "valid user" style settings. The moment one is defined, Vista fails to connect and pops up an

For the last 3 weeks I've been working on getting RHEL4 (and 5, but that's a different story) to play well with Active Directory, OpenLDAP, Kerberos, PAM and NSS. It's been a long struggle but I now have a process to authenticate and authorize a RHEL4 client to a windows Active Directory server to that my AD Users can log into my Linux boxes (assuming their group permissions are set

Hi, after upgrading samba from 4.1.17 to 4.1.19 on OpenSuSE 13.2, any shares offered by this machine can nolonger be accessed, when these shares contain an entry "force group" which specifies a local unix group and when there exists a unix user with the same name. Here's an excerpt from smb.conf: [FactWork] comment = FactWork-Downloadportal path =

I'm trying to connect from a vista machine to a samba share on debian (latest). This is going fine with these settings: [global] directory security mask 0775 security mask 0775 create mask 0775 directory mask 0775 workgroup = nlstr server string = %h server panic action = /usr/share/samba/panic-action %d encrypt passwords = true passdb backend = tdbsam obey pam