SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I am trying to share my Lexmark printer which is connected to my Slackware 12.1 server.
Everything works fine when i print test pages from my Slackbox, but i cant print from my vista and xp pc's.
I have tried several how-to's but nothing worked for me
problem :
pinter prints on slackware, but not from my other pc's
this is my cupsd.conf
Code:
#
# "$Id: cupsd.conf.in 7199 2008-01-08 00:16:30Z mike $"
# Sample configuration file for the Common UNIX Printing System (CUPS)
# scheduler. See "man cupsd.conf" for a complete description of this
# file.
#
# Log general information in error_log - change "info" to "debug" for
# troubleshooting...
LogLevel debug
# Administrator user group...
SystemGroup sys root lp
# Only listen for connections from the local machine.
Listen Port 631
Listen /var/run/cups/cups.sock
# Show shared printers on the local network.
Browsing On
BrowseOrder allow,deny
BrowseAllow all
# Default authentication type, when authentication is required...
DefaultAuthType Basic
# Restrict access to the server...
<Location />
Order allow,deny
Allow all
</Location>
# Restrict access to the admin pages...
<Location /admin>
Encryption Required
Order allow,deny
</Location>
# Restrict access to configuration files...
<Location /admin/conf>
AuthType Default
Require user @SYSTEM
Order allow,deny
</Location>
# Set the default printer/job policies...
<Policy default>
# Job-related operations must be done by the owner or an administrator...
<Limit Send-Document Send-URI Hold-Job Release-Job Restart-Job Purge-Jobs Set-Job-Attributes Create-Job-Subscription Renew-Subscription Cancel-Subscription Get-Notifications Reprocess-Job Cancel-Current-Job Suspend-Current-Job Resume-Job CUPS-Move-Job>
Require user @OWNER @SYSTEM
Order deny,allow
Allow all
</Limit>
# All administration operations require an administrator to authenticate...
<Limit CUPS-Add-Modify-Printer CUPS-Delete-Printer CUPS-Add-Modify-Class CUPS-Delete-Class CUPS-Set-Default>
AuthType Default
Require user @SYSTEM
Order deny,allow
</Limit>
# All printer operations require a printer operator to authenticate...
<Limit Pause-Printer Resume-Printer Enable-Printer Disable-Printer Pause-Printer-After-Current-Job Hold-New-Jobs Release-Held-New-Jobs Deactivate-Printer Activate-Printer Restart-Printer Shutdown-Printer Startup-Printer Promote-Job Schedule-Job-After CUPS-Accept-Jobs CUPS-Reject-Jobs>
AuthType Default
Require user @SYSTEM
Order deny,allow
Allow all
</Limit>
# Only the owner or an administrator can cancel or authenticate a job...
<Limit Cancel-Job CUPS-Authenticate-Job>
Require user @OWNER @SYSTEM
Order deny,allow
Allow all
</Limit>
<Limit All>
Order deny,allow
</Limit>
</Policy>
#
# End of "$Id: cupsd.conf.in 7199 2008-01-08 00:16:30Z mike $".
#
and this is my error log :
Code:
D [05/Jun/2008:11:58:20 +0200] cupsdAcceptClient: 5 from localhost (Domain)
D [05/Jun/2008:11:58:20 +0200] cupsdReadClient: 5 POST / HTTP/1.1
D [05/Jun/2008:11:58:20 +0200] cupsdAuthorize: No authentication data provided.
D [05/Jun/2008:11:58:20 +0200] Get-Printer-Attributes ipp:///printers/LexmarkZ65
D [05/Jun/2008:11:58:20 +0200] cupsdProcessIPPRequest: 5 status_code=0 (successful-ok)
D [05/Jun/2008:11:58:20 +0200] cupsdCloseClient: 5
D [05/Jun/2008:11:58:20 +0200] cupsdAcceptClient: 5 from localhost (Domain)
D [05/Jun/2008:11:58:20 +0200] cupsdAcceptClient: 7 from localhost (Domain)
D [05/Jun/2008:11:58:20 +0200] cupsdReadClient: 7 POST / HTTP/1.1
D [05/Jun/2008:11:58:20 +0200] cupsdAuthorize: No authentication data provided.
D [05/Jun/2008:11:58:20 +0200] Get-Jobs ipp://localhost/printers/LexmarkZ65
D [05/Jun/2008:11:58:20 +0200] cupsdProcessIPPRequest: 7 status_code=0 (successful-ok)
D [05/Jun/2008:11:58:20 +0200] cupsdReadClient: 5 POST / HTTP/1.1
D [05/Jun/2008:11:58:20 +0200] cupsdAuthorize: No authentication data provided.
D [05/Jun/2008:11:58:20 +0200] Get-Printer-Attributes ipp:///printers/LexmarkZ65
D [05/Jun/2008:11:58:20 +0200] cupsdProcessIPPRequest: 5 status_code=0 (successful-ok)
D [05/Jun/2008:11:58:20 +0200] cupsdReadClient: 7 POST / HTTP/1.1
I hope someone can help me
Tobas
P.s. Alienbob im sorry but my other post contains a wrong error log
I would bet this is a Samba server issue. Were you able to add the Lexmark Z65 printer to any of your windoze clients? Would you post your smb.conf file?
# This is the main Samba configuration file. You should read the
# smb.conf(5) manual page in order to understand the options listed
# here. Samba has a huge number of configurable options (perhaps too
# many!) most of which are not shown in this example
#
# For a step to step guide on installing, configuring and using samba,
# read the Samba HOWTO Collection.
#
# Any line which starts with a ; (semi-colon) or a # (hash)
# is a comment and is ignored. In this example we will use a #
# for commentry and a ; for parts of the config file that you
# may wish to enable
#
# NOTE: Whenever you modify this file you should run the command "testparm"
# to check that you have not made any basic syntactic errors.
#
#======================= Global Settings =====================================
[global]
log file = /var/log/samba.%m
dns proxy = no
load printers = yes
netbios name = SERVER
printcapname = cups
printing = cups
server string = Samba Server
socket options = TCP_NODELAY
workgroup = WERKGROUP
os level = 20
hosts allow = 192.168.1. 192.168.2. 127.
encrypt passwords = Yes
security = user
max log size = 50
# workgroup = NT-Domain-Name or Workgroup-Name, eg: LINUX2
# server string is the equivalent of the NT Description field
# 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 HOWTO Collection for details.
# 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
# If you want to automatically load your printer list rather
# than setting them up individually then you'll need this
# 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 = pcguest
# this tells Samba to use a separate log file for each machine
# that connects
# Put a capping on the size of the log files (in Kb).
# Use password server option only with security = server
# The argument list may include:
# password server = My_PDC_Name [My_BDC_Name] [My_Next_BDC_Name]
# or to auto-locate the domain controller/s
# password server = *
; password server = <NT-Server-Name>
# Use the realm option only with security = ads
# Specifies the Active Directory realm the host is part of
; realm = MY_REALM
# Backend to store user information in. New installations should
# use either tdbsam or ldapsam. smbpasswd is available for backwards
# compatibility. tdbsam requires no further configuration.
; passdb backend = tdbsam
# Using the following line enables you to customise your configuration
# on a per machine basis. The %m gets replaced with the netbios name
# of the machine that is connecting.
# Note: Consider carefully the location in the configuration file of
# this line. The included file is read at that point.
; include = /usr/local/samba/lib/smb.conf.%m
# Most people will find that this option gives better performance.
# See the chapter 'Samba performance issues' in the Samba HOWTO Collection
# and the manual pages for details.
# You may want to add the following on a Linux system:
# SO_RCVBUF=8192 SO_SNDBUF=8192
# Configure Samba to use multiple interfaces
# If you have multiple network interfaces then you must list them
# here. See the man page for details.
; interfaces = 192.168.12.2/24 192.168.13.2/24
# Browser Control Options:
# set local master to no if you don't want Samba to become a master
# browser on your network. Otherwise the normal election rules apply
; local master = no
# OS Level determines the precedence of this server in master browser
# elections. The default value should be reasonable
; os level = 33
# Domain Master specifies Samba to be the Domain Master Browser. This
# allows Samba to collate browse lists between subnets. Don't use this
# if you already have a Windows NT domain controller doing this job
; domain master = yes
# Preferred Master causes Samba to force a local browser election on startup
# and gives it a slightly higher chance of winning the election
; preferred master = yes
# Enable this if you want Samba to be a domain logon server for
# Windows95 workstations.
; domain logons = yes
# if you enable domain logons then you may want a per-machine or
# per user logon script
# run a specific logon batch file per workstation (machine)
; logon script = %m.bat
# run a specific logon batch file per username
; logon script = %U.bat
# Where to store roving profiles (only for Win95 and WinNT)
# %L substitutes for this servers netbios name, %U is username
# You must uncomment the [Profiles] share below
; logon path = \\%L\Profiles\%U
# Windows Internet Name Serving Support Section:
# WINS Support - Tells the NMBD component of Samba to enable it's WINS Server
; wins support = yes
# WINS Server - Tells the NMBD components of Samba to be a WINS Client
# Note: Samba can be either a WINS Server, or a WINS Client, but NOT both
; wins server = w.x.y.z
# WINS Proxy - Tells Samba to answer name resolution queries on
# behalf of a non WINS capable client, for this to work there must be
# at least one WINS Server on the network. The default is NO.
; wins proxy = yes
# DNS Proxy - tells Samba whether or not to try to resolve NetBIOS names
# via DNS nslookups. The default is NO.
# These scripts are used on a domain controller or stand-alone
# machine to add or delete corresponding unix accounts
; add user script = /usr/sbin/useradd %u
; add group script = /usr/sbin/groupadd %g
; add machine script = /usr/sbin/adduser -n -g machines -c Machine -d /dev/null -s /bin/false %u
; delete user script = /usr/sbin/userdel %u
; delete user from group script = /usr/sbin/deluser %u %g
; delete group script = /usr/sbin/groupdel %g
#============================ Share Definitions ==============================
[homes]
comment = Home Directories
browseable = no
writable = yes
# NOTE: If you have a BSD-style print system there is no need to
# specifically define each individual printer
[LexmarkZ65]
printer = LexmarkZ65
comment = All Printers
browseable = yes
valid users = tobas,julian,@users
printable = yes
create mode = 0777
path = /var/spool/samba
use client driver = yes
# Set public = yes to allow user 'guest account' to print
[Vault]
revalidate = yes
force user = tobas
delete readonly = yes
writeable = yes
valid users = tobas,@users
path = /home/vault
force group = users
[Queue]
writeable = yes
valid users = tobas,julian,@users
path = /home/tobas/hellanzb/nzb/daemon.queue
The way samba is set up, your users will have to log in as a user before they can print. Do you have each user set up as samba users? Have you logged it before you tried printing?
Another thing, are these windoze machines on the subnets defined in the global section?
The way samba is set up, your users will have to log in as a user before they can print. Do you have each user set up as samba users? Have you logged it before you tried printing?
Another thing, are these windoze machines on the subnets defined in the global section?
I logged in to acces the shares before i tried to print.
And yes that are windoze machines
I would bet this is a Samba server issue. Were you able to add the Lexmark Z65 printer to any of your windoze clients? Would you post your smb.conf file?
No this a a vista issue. I have the same issue. my samba server works just fine for window$ XP, and other Linux boxes.
Check if the vista box can create a file on the samba box. If not you need to hack the window$ registry.
It's not really Vista that sucks, but the driver developers. I've never been a fan of Windows, but the Vista-bashing is very exaggerated. XP was quite insecure, and that allowed driver developers (and application developers) to mildly exploit holes to gain higher priveleges and interface with the hardware. If they had written their drivers properly without exploiting security holes, they would probably (though not always) work with Vista (or maybe requiring only a little bit of modification), but they didn't because it was so darn easy and effective to hack away at XP.
The second Microsoft actually tries to implement any sort of security beyond a surface-based spyware detector, people think the OS is crap. I have news for you. My Lexmark printer is almost, thought not quite, a paperweight in Linux. It's terrible. Do I blame Linux? No, I blame Lexmark for writing crappy 1995 drivers and never updating them. They have some open-source kit, but it was released far too late and I think I'm the only one left with this piece of crap Z23 which actually worked very well in Windows (though I haven't tried in Vista). I'm forced to live with black-and-white and only being able to print one page at a time (literally) when it works at all -- or I can print using Windows in a VM. Both choices suck.
Before we get to far off topic; Did my post fix your printing?
I also have a fix for vista boxes behind linux firewalls. It appears Micro $oft did several things in the networking code for vista, To make Linux and Unix servers look bad. The samba team as other have their hands full this time.
To get around the authentication problem, could you add the following to your global section.
Quote:
guest account = guest
If you look at the Printers section I posted earlier, you will see 'guest ok = yes'. When you turn on guest account, any smbuser should have access
to any share you add guest ok = yes to. Anyone on the lan without a smbuser still should not be able to print.
I believe you could make an allow, deny lists of users, if you needed to restrict printing to specific users.
I have XP systems, and 1 vista system printing to my linux printer share. I didn't have to do any hacks on any system to get the printing going. I just
added the guest account.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.