[Samba] Samba/Cups issues across a network

Marc Chamberlin marc at marcchamberlin.com
Wed Oct 28 23:54:20 MDT 2009


Jeremy Allison wrote:
> On Wed, Oct 28, 2009 at 04:11:42PM -0700, Marc Chamberlin wrote:
>   
>> Hello
>>
>> I am in the process of trying to set up a Cups server and a Samba server  
>> on a central Linux system in my home SOHO network. The network is  
>> configured as a simple workgroup with all peer to peer connections.  
>> There is no domain controller. On this network I have a printer attached  
>> to a Win2K machine.
>>
>> The Cups server is require so as to use a special driver from TurboPrint  
>> for processing and preparing files for printing. Most of the Samba  
>> server seems to be set up correctly in that I am able to access shared  
>> files from other computers on my network. The only part which is not  
>> working is the ability to send files to the Samba server, from other  
>> computers on my network, for forwarding on to the Cups server, which in  
>> turn processes and forwards the files on to the Win2K system for  
>> printing out.
>>
>> If, on the central server itself, I use an lp command to send a file  
>> directly to the CUPs server, it works fine and the file will be printed  
>> out. And like I mentioned I can browse files on the server from other  
>> computers on my network. So, too my uneducated eyes, this appears to be  
>> possibly some sort of authentication problem between the Samba server  
>> and the Cup's server? If so, how can I trace it down to figure out  
>> exactly why such a problem is occurring?
>>
>> Another item of interest is that when I send a file from some computer  
>> on my network, to the Samba/Cups server on the central computer, I do  
>> see briefly the print job showing up in the print queue on the Win2K  
>> machine! So perhaps there is some sort of authentication issue that is  
>> arising from all this interaction and the Win2K machine is refusing to  
>> print the job because of some kind of authentication problem? Again, if  
>> so, how can I trace it down?
>>
>> The Samba server is configured to use User level security. I have looked  
>> in the various log files, Samba appears to be reporting that everything  
>> went fine and the incoming username/password were accepted. However I do  
>> not see anything being reported in the CUP's log files...
>>
>> Dunno what other info is needed, and will be happy to supply copies of  
>> any config files that might be helpful. Thanks in advance for any help  
>> offered, I know this might be more complex than most setups, but I am at  
>> a loss on how to proceed.
>>     
>
> Post your smb.conf so we can see how this is set up. Also, what
> version of Samba on what Linux distro ?
>
> Jeremy.
>   
Thanks Jeremy for your reply.  I am running on SuSE 11.0 x64 
architecture. From SWAT I got the following version info - version:    
3.2.4-4.7-2210-SUSE-SL11.0   Hope that is correct.

As for my smb.conf, it is configured for my SOHO network at home. Does 
not show the printer share I am actually trying to connect to as that is 
supplied by CUPS. (autoloaded from the printcap file and called tp0.)

My printcap file is -

# This file was automatically generated by cupsd(8) from the
# /etc/cups/printers.conf file.  All changes to this file
# will be lost.
tp0|Canon_PIXMA_MP780:rm=bigbang.marcchamberlin.com:rp=tp0:


My smb.conf file is shown below -

# Samba config file created using SWAT
# from UNKNOWN ()
# Date: 2009/10/28 12:02:37

[global]
        workgroup = CHAMBERLIN
        interfaces = eth1, 192.168.2.100
        log level = 3
        printcap name = cups
        logon path = \\%L\profiles\.msprofile
        logon drive = P:
        logon home = \\%L\%U\.9xprofile
        preferred master = Auto
        ldap ssl = no
        usershare owner only = No
        cups options = raw
        hide dot files = No

[homes]
        comment = Home Directories
        path = /home
        valid users = %S, %D%w%S
        read only = No
        inherit acls = Yes

[profiles]
        comment = Network Profiles Service
        path = %H
        read only = No
        create mask = 0600
        directory mask = 0700
        store dos attributes = Yes

[users]
        comment = All users
        path = /home
        read only = No
        inherit acls = Yes
        veto files = /aquota.user/groups/shares/

[groups]
        comment = All groups
        path = /home/groups
        read only = No
        inherit acls = Yes

[printers]
        comment = All Printers
        path = /var/tmp
        create mask = 0600
        guest ok = Yes
        printable = Yes
        browseable = No

[print$]
        comment = Printer Drivers
        path = /var/lib/samba/drivers
        write list = @ntadmin, root
        force group = ntadmin
        create mask = 0664
        directory mask = 0775
        guest ok = Yes

[slash]
        comment = Root directory
        path = /
        read only = No

[temp]
        comment = Temporary directory
        path = /tmp
        read only = No
        guest ok = Yes

[homedirs]
        comment = Home Directories
        path = /home
        read only = No



More information about the samba mailing list