Sponsored Content
Operating Systems Solaris samba issue: one samba share without password prompting and the others with. Post 302589785 by ideal2545 on Thursday 12th of January 2012 02:45:03 PM
Old 01-12-2012
samba issue: one samba share without password prompting and the others with.

Hi All, I've been trying to configure samba on Solaris 10 to allow me to have one share that is open and writable to all users and have the rest of my shares password protected by a generic account.

If I set my security to user, my secured shares work just fine and prompt accordingly, but when I try to visit my "open" share, it prompts for a password. If I set my security to share, then my "open" share works as it should, but then my "secured" shares do not work at all! Could someone give me a hand?

global:


# workgroup = NT-Domain-Name or Workgroup-Name, eg: MIDEARTH
workgroup = xxx

# server string is the equivalent of the NT Description field
server string = xxx

# Security mode. Defines in which mode Samba will operate. Possible
# values are share, user, server, domain and ads. Most people will want
# user level security. See the Samba-HOWTO-Collection for details.
security = user


# This option is important for security. It allows you to restrict
# connections to machines which are on your local network. The
# following example restricts access to two C class networks and
# the "loopback" interface. For more examples of the syntax see
# the smb.conf man page
; hosts allow = 192.168.1. 192.168.2. 127.

# If you want to automatically load your printer list rather
# than setting them up individually then you'll need this
; load printers = yes

# you may wish to override the location of the printcap file
; printcap name = /etc/printcap

# on SystemV system setting printcap name to lpstat should allow
# you to automatically obtain a printer list from the SystemV spool
# system
; printcap name = lpstat

# It should not be necessary to specify the print system type unless
# it is non-standard. Currently supported print systems include:
# bsd, cups, sysv, plp, lprng, aix, hpux, qnx
; printing = cups

# Uncomment this if you want a guest account, you must add this to /etc/passwd
# otherwise the user "nobody" is used
guest account = nobody

shared defs:
[app]
path = /d/biapps/
writable = yes
browsable = yes
create mask = 775
valid users = weblogic

[temp]
path = /w/temp
public = yes
writable = yes
browsable = yes
create mask = 775
guest ok = yes
guest only = yes


Thanks guys
Jon
 

10 More Discussions You Might Find Interesting

1. Solaris

Samba: share subfolder as read only.

Hi, Currently I have a Samba shared configured as follows: comment = Public fileshare path = /u02/pub guest ok = Yes writeable = Yes There is a subfolder under /u02/pub called /u02/pub/expenses/hardware that I need to make read only. How do I do this? I am new to using Samba. ... (2 Replies)
Discussion started by: sparcman
2 Replies

2. Linux

Samba share script

Hi everyone! I'm trying to run a script when a folder is shared and when it stop being shared. Is there something like .start_share or .stop_share scripts in Samba where I could run some commands?:confused: edit: maybe with a wrapper in smbmount but I share folders via nautilus. Any ideas? (0 Replies)
Discussion started by: funyotros
0 Replies

3. Solaris

SAMBA is connecting to the share somehow as root

I'm running Solaris 10 with Samba server. The client is a Windows XP desktop. I have set this up for various other servers and this is the first time that I'm seeing the problem. I have a prod & test solaris samba server configured exactly the same and the share is encrypted by Vormetric. The... (0 Replies)
Discussion started by: woot14
0 Replies

4. Red Hat

chroot sftp, samba share, ownership issue linux hosts

Hello, I have sftp server with chroot for a group and username is on a Linux host, I have created a few subdirectories under sftpuser home directories with 775. Then using a Samba I shared this user home directory to another linux client. On the Linux client, I have jboss user to access... (2 Replies)
Discussion started by: bobby320
2 Replies

5. Red Hat

Samba share problem in Linux 6.4

Hi , In samba i have shared my home directory, but its showing as a printer. Not able to share data. $ smbclient -L 192.168.122.1 Enter priyank's password: Domain= OS= Server= Sharename Type Comment --------- ---- ------- shared_priyank Printer ... (3 Replies)
Discussion started by: Priy
3 Replies

6. UNIX for Dummies Questions & Answers

Samba share Windows problem

I have a problem with a Samba share (Debian) on Windows. My config http://pastebin.com/18ncwngr With smbclient -U ftp //xxx.xxx.xxx.xxx/daten I can connect with another Linux Server. Only with Windows it does not work. Deactivate firewall also but I can not connect me. ... (0 Replies)
Discussion started by: PAfreakFlorian
0 Replies

7. Red Hat

Samba share assess w/no authentication

RH 6.4 Samba 3.5.10. Joined a Windows AD (net rpc) I'm trying to create a public read-only share but regardless of the options I've tried users get prompted for a user/password. Can someone tell me whats wrong with my setup? I'm trying to make a whole filesystem that will contain installation... (0 Replies)
Discussion started by: dignarn
0 Replies

8. 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

9. 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

10. UNIX for Advanced & Expert Users

Mounting a samba share

Hi, I need to mount a directory from a Windows server to a CentOS box. The Windows server used is Windows Server 2003, and the path to the directory that I want to mount on CentOS is C:\Tomcat6\webapps\NASApp\logs. I am not sure of the correct way to mount this on CentOS, as most of the... (2 Replies)
Discussion started by: anaigini45
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 09:22 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy