Sponsored Content
Operating Systems Linux Red Hat cannot access a directory with samba Post 302713261 by Corona688 on Wednesday 10th of October 2012 12:04:12 PM
Old 10-10-2012
Yes, the permissions of the folders being shared have a great effect on whether people can access them. Their users and groups also matter.

This does not mean you should jam 777 on everything! There's a reason it's not working, figure out what their permissions are and what your users can access and what permissions they actually need.

What are the permissions and ownership of the dir that can't be accessed?
 

8 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Unix directory permissions for Samba

Hi, I've installed Samba on an AIX machine and configured smb.conf to have a bunch of shares available to Windows. I can see the shares, but I couldn't access them. After about 30 minutes of chmod'ding if finally got access by doing the following to the directories I shared: chmod -R... (2 Replies)
Discussion started by: szahir1
2 Replies

2. IP Networking

Access samba over wan

How do I access a samba server over a wan with routers used as the gateways between the lans (1 Reply)
Discussion started by: ogah
1 Replies

3. Windows & DOS: Issues & Discussions

samba with public access

Hello friends .. I have configured "smb" in debian machine . Created a share named "share_one" with public access and started samba service . I am able to access the share "share_one" directly without any difficulty on linux machines. But when it comes to windows it asks for username... (1 Reply)
Discussion started by: pradeepreddy
1 Replies

4. Red Hat

Winbind and pam - restrict all services except for samba access

Hi, I have recently taken control of a number of RHEL5.3 servers that have samba shares setup on them and are authenticating using pam and winbind. My issue is that any user that has an active directory account can currently log in to the linux boxes using their ad credentials. I need to... (0 Replies)
Discussion started by: klyne
0 Replies

5. Solaris

samba read write access to owner and no access to other users

Hi All, I want to configure samba share permission so that only directory creator/owner has a read and write permission and other users should not have any read/write access to that folder.Will that be possible and how can this be achieved within samba configuration. Regards, Sahil (1 Reply)
Discussion started by: sahil_shine
1 Replies

6. Proxy Server

Unable to access Samba share with Ubuntu on Win7

I have an issue with my Samba share - I am unable to write to it, edit a file or rename a folder etc within Windows. I am using Windows 7 and Ubuntu 12.04 and this is my Samba config. I can connect to the /sylius directory no problem (no password required), but I cannot save to it. Is... (3 Replies)
Discussion started by: crmpicco
3 Replies

7. UNIX for Beginners Questions & Answers

Samba Share access from windows

Hello, I want to connect to two samba shares both on the same Linux box but each with a different username from a windows server 2008. I created 2 gpos to connect and I can connect to the shares individually via net use command, but once I entered credentials for one of the shares, it seems I... (1 Reply)
Discussion started by: zaineyma
1 Replies

8. AIX

Samba 3.6 on AIX 7.1 - Windows 10 Access to AIX file shares using Active Directory authentication

I am running AIX 7.1 and currently we have samba 3.6.25 installed on the server. As it stands some AIX folders are shared that can be accessed by certain Windows users. The problem is that since Windows 10 the guest feature no longer works so users have to manually type in their Windows login/pwd... (14 Replies)
Discussion started by: linuxsnake
14 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. However, currently only Windows 2000 and higher is supported by the Microsoft driver, so you will also need to get the Adobe driver to sup- port 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. 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 COPYRIGHT
Copyright 2007-2013 by Apple Inc. 8 July 2013 CUPS cupsaddsmb(8)
All times are GMT -4. The time now is 11:18 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy