Sponsored Content
Operating Systems Linux Red Hat RH6 samba 3.5.10 @group not working Post 302949919 by dignarn on Friday 17th of July 2015 01:35:36 PM
Old 07-17-2015
RH6 samba 3.5.10 @group not working

The problem I'm having is that if I spec a user id (valid user) in the share, I don't get prompted for a password when trying to access it from a Windows host. If however in the share options I spec a group name (ie. valid user = @aiswf), I get prompted for an account and password. The user accounts and groups have been created on the samba server. We joined the Windows AD domain (net rpc.)

Why is a group share access behaving differently from a user share access? Am I missing a config/setup step ?


Below is my smb.conf
Code:
[global] 

workgroup = DEVENG 

server string = %h Samba File Server %v 

hosts allow = 127. 10. 172. 

smb ports = 139 445 

# Domain Members Options 

security = domain         encrypt 

passwords = yes 

passdb backend = tdbsam 

password server = * 

domain master = no 

wins server = 10.XXX.XX.XX,172.XX.XX.XXX 

dns proxy = yes 

deadtime = 10 

# Browser Control Options
local master = no 

preferred master = no 

os level = 33 

# Filesystem Options
map archive = no 

map hidden = no         m
ap read only = no 

map system = no 

store dos attributes = yes
         hide dot files = no 



#=== Share Definitions === 

[neteng] 

comment = Network Engineering Share 

path = /fs_neteng 

browseable = yes 

writable = yes 

valid users = @neteng dignarn 



[aiswf]
comment = AIS Workflow Share 

path = /fs_aiswf 

browseable = yes 

writable = yes 

guest ok = yes 

admin users = arnoldr 

valid users = @aiswf


Last edited by Don Cragun; 07-17-2015 at 05:23 PM.. Reason: Add CODE tags.
 

6 More Discussions You Might Find Interesting

1. AIX

Group permission not working

Please forgive me, but I am not a Unix expert. I'm supporting SAP r/3 and we are trying to run an external command from SAP to read a file at the unix level. When we perform the more command on the following two files, we are succesful in reading the bws file, but unsucessful in reading the bws1... (13 Replies)
Discussion started by: bbauerle
13 Replies

2. Ubuntu

Samba not working

I'm trying to hook up a Ubuntu 10.04 PC to my media box by Samba and I am getting can not connect errors although I can see the directories. I have done everything I can think of to enable sharing and guest access. Can anyone think of anything to try such as restoring defaults and trying again? Has... (8 Replies)
Discussion started by: dothehustle
8 Replies

3. Red Hat

User and Group quota is not working on RHEL6.2 ext4/ext3

Hello! I am in a weird problem of not able to set quota on an ext4 file system. I have setup a logical volume on which this ext4 filesystem resides. It's going to be used by an application for dumping data. But we want to setup quota so that it does not consume all the free space of the lv. The... (5 Replies)
Discussion started by: admin_xor
5 Replies

4. Red Hat

Samba/Winbind issue - Can't get user and group info from sub domains

Hi, We now have a Samba or Winbind issue. The Linux client under RHEL6 can not get Windows' AD sub-domain info. See the following output please. The main domain 'Global' is shown online, but the sub-domain 'Europe' and 'Asia' are shown offline although they are online. Commands 'wbinfo -u' and... (0 Replies)
Discussion started by: aixlover
0 Replies

5. Ubuntu

Renamed Volume Group name on Webmin while running samba server (oops)

Hi...I'm new to Linux and was working on a home server. I have it operational with Samba Share as my NAS system. Unfortunately, while I was on Webmin I changed the Logical Volume Group Name and now I can't find the data I had saved on my Samba Server. Can anyone help me recover those files? ... (0 Replies)
Discussion started by: pangil
0 Replies

6. Red Hat

Samba share - currently not working

Long running samba share. Never have any problems, Suddenly started asking windows users for password - which doesnt work. Tried to manually reset smb password and manually map - still wrong password. Restart samba? (2 Replies)
Discussion started by: psychocandy
2 Replies
cupsaddsmb(8)							    Apple Inc.							     cupsaddsmb(8)

NAME
cupsaddsmb - export printers to samba for windows clients SYNOPSIS
cupsaddsmb [ -H samba-server ] [ -U samba-user[%samba-password] ] [ -h cups-server[:port] ] [ -v ] -a cupsaddsmb [ -H samba-server ] [ -U samba-user[%samba-password] ] [ -h cups-server[:port] ] [ -v ] printer [ ... printer ] DESCRIPTION
cupsaddsmb exports printers to the SAMBA software (version 2.2.0 or higher) for use with Windows clients. Depending on the SAMBA configura- tion, you may need to provide a password to export the printers. This program requires the Windows printer driver files described below. OPTIONS
cupsaddsmb supports the following options: -H samba-server Specifies the SAMBA server which defaults to the CUPS server. -U samba-user[%samba-password] Specifies the SAMBA print admin username which defaults to your current username. If the username contains a percent (%) character, then the text following the percent is treated as the SAMBA password to use. -a Exports all known printers. Otherwise only the named printers are exported. -h cups-server[:port] Specifies a different CUPS server to use. -v Specifies that verbose information should be shown. This is useful for debugging SAMBA configuration problems. SAMBA CONFIGURATION
cupsaddsmb uses the new RPC-based printing support in SAMBA 2.2.x to provide printer drivers and PPD files to Windows client machines. In order to use this functionality, you must first configure the SAMBA smb.conf(5) file to support printing through CUPS and provide a printer driver download share, as follows: [global] load printers = yes printing = cups printcap name = cups [printers] comment = All Printers path = /var/spool/samba browseable = no public = yes guest ok = yes writable = no printable = yes [print$] comment = Printer Drivers path = /etc/samba/drivers browseable = yes guest ok = no read only = yes write list = root This configuration assumes a FHS-compliant installation of SAMBA; adjust the [printers] and [print$] share paths accordingly on your system as needed. MICROSOFT POSTSCRIPT DRIVERS FOR WINDOWS
The base driver for Windows 2000 and higher is the Microsoft PostScript driver, which is available on any system running Windows 2000 or higher in the %WINDIR%SYSTEM32SPOOLDRIVERSW32X863 folder for 32-bit drivers and %WINDIR%SYSTEM32SPOOLDRIVERSX643 folder for 64-bit drivers. The CUPS printer driver is preferred over the Microsoft driver since it supports the page-label, job-billing, and job-hold-until options fully on all printers. However, currently only Windows 2000 and higher is supported by the Microsoft driver, so you will also need to get the Adobe driver to support Windows 95, 98, and Me clients. The Adobe and Microsoft drivers for Windows 2000 are identical. Once you have extracted the driver files, copy the 32-bit drivers to the /usr/share/cups/drivers directory and the 64-bit drivers to the /usr/share/cups/drivers/x64 directory exactly as named below: [Windows 2000 and higher] ps5ui.dll pscript.hlp pscript.ntf pscript5.dll Note: Unlike Windows, case is significant - make sure that you use the lowercase filenames shown above, otherwise cupsaddsmb will fail to export the drivers. CUPS POSTSCRIPT DRIVERS FOR WINDOWS
cupsaddsmb can use the CUPS v6 PostScript printer driver for Windows, which is available for download from the CUPS web site. The CUPS printer driver is preferred over the Adobe and Microsoft drivers since it supports the page-label, job-billing, and job-hold-until options fully on all printers. However, currently only Windows 2000 and higher is supported by the CUPS driver, so you will also need to get the Adobe driver to support Windows 95, 98, and Me clients. Once you have extracted the driver files, copy the 32-bit drivers to the /usr/share/cups/drivers directory and the 64-bit drivers to the /usr/share/cups/drivers/x64 directory exactly as named below: [Windows 2000 and higher] cups6.inf (from www.cups.org) cups6.ini (from www.cups.org) cupsps6.dll (from www.cups.org) cupsui6.dll (from www.cups.org) ps5ui.dll (from your Windows system) pscript.hlp (from your Windows system) pscript.ntf (from your Windows system) pscript5.dll (from your Windows system) Note: Unlike Windows, case is significant - make sure that you use the lowercase filenames shown above, otherwise cupsaddsmb will fail to export the drivers. ADOBE POSTSCRIPT DRIVERS FOR WINDOWS 95, 98, AND ME cupsaddsmb can use the Adobe PostScript printer driver for Windows 95, 98, and ME, which are available for download from the Adobe web site (http://www.adobe.com). The Adobe driver does not support the page-label, job-billing, or job-hold-until options. Once you have installed the driver on a Windows system, copy the following files to the /usr/share/cups/drivers directory exactly as named below: [Windows 95, 98, and Me] ADFONTS.MFM ADOBEPS4.DRV ADOBEPS4.HLP ICONLIB.DLL PSMON.DLL Note: Unlike Windows, case is significant - make sure that you use the UPPERCASE filenames shown above, otherwise cupsaddsmb will fail to export the drivers. KNOWN ISSUES
Getting the full set of Windows driver files should be easier. SEE ALSO
smbd(8), smb.conf(5), http://localhost:631/help http://www.cups.org/windows/ COPYRIGHT
Copyright 2007-2011 by Apple Inc. 25 July 2007 CUPS cupsaddsmb(8)
All times are GMT -4. The time now is 05:11 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy