I've installed Samba 2.2.7a on my SuSE 8.1 system in an effort to
persuade it to act as a print server on my LAN, which consists of it
and 6 Windows desktops of various flavors. Right away it seemed to
allow file sharing and printing from DOS and became browsable from the
Network Neighborhood, but I can't get it to print from Windows. I
keep getting a Status of "Access denied, unable to connect", even when
simply trying to print a test page. A perusal of the Samba logs has
been inconclusive as has a poring through both Samba and SuSE
documentation. I'm guessing that it's a stupid permission or
authentication configuration I've overlooked, but it's making me
crazy!
I tried to keep my smb.conf very simple:
# This is /usr/local/samba/lib/smb.conf
[global]
netbios name = penguin
workgroup = workgroup
log level = 2
log file = /var/log/samba.log
security = share
[pub]
path = /home/public
browseable = yes
guest ok = yes
read only = no
[printers]
path = /var/spool/samba
printable = yes
guest ok = yes
============================================================Paul David Mena
Haiku in Low Places, Ltd.
Email: haiku@lowplaces.net
Webpage: http://www.lowplaces.net
=============================================================
> I've installed Samba 2.2.7a on my SuSE 8.1 system in an effort to > persuade it to act as a print server on my LAN, which consists of it > and 6 Windows desktops of various flavors. Right away it seemed to > allow file sharing and printing from DOS and became browsable from the > Network Neighborhood, but I can't get it to print from Windows. I > keep getting a Status of "Access denied, unable to connect", even when > simply trying to print a test page. A perusal of the Samba logs has > been inconclusive as has a poring through both Samba and SuSE > documentation. I'm guessing that it's a stupid permission or > authentication configuration I've overlooked, but it's making me > crazy!Does it really fail to print, or just show that error message (yet print ok)? If those various flavors are NT/2000/XP, and you can still print, this happens when: 1. Your users are local admins of their machines 2. They have installed the drivers locally (rather than from the print$ share). 3. spools has not been disabled for that share with use client driver yes (or globally with disable spoolss = yes). Best thing to do is fix #2. Doing the "use client driver = yes" thing will suffice if your users need to be local admins, but it's "an ugly hack." Check out "use client driver" in man smb.conf ~ Daniel ----------------------------------------------------------------------- This message is the property of Time Inc. or its affiliates. It may be legally privileged and/or confidential and is intended only for the use of the addressee(s). No addressee should forward, print, copy, or otherwise reproduce this message in any manner that would allow it to be viewed by any individual not originally listed as a recipient. If the reader of this message is not the intended recipient, you are hereby notified that any unauthorized disclosure, dissemination, distribution, copying or the taking of any action in reliance on the information herein is strictly prohibited. If you have received this communication in error, please immediately notify the sender and delete this message. Thank you.
> I've installed Samba 2.2.7a on my SuSE 8.1 system in an effort to > persuade it to act as a print server on my LAN, which consists of it > and 6 Windows desktops of various flavors. Right away it seemed to > allow file sharing and printing from DOS and became browsable from the > Network Neighborhood, but I can't get it to print from Windows. I > keep getting a Status of "Access denied, unable to connect", even when > simply trying to print a test page. A perusal of the Samba logs has > been inconclusive as has a poring through both Samba and SuSE > documentation. I'm guessing that it's a stupid permission or > authentication configuration I've overlooked, but it's making me > crazy!I had the exact same problem and it cost me a full day to solve it but now it works! At first I had my printer connected to the Samba server using the lpd protocol, but that did not work at all. On my W2k clients I had the 'Access denied' problem all the time. Then I went over to using CUPS for managing my printer and read some info on this issue. Here are the sites I read that lead me to victory: http://us3.samba.org/samba/ftp/docs/htmldocs/cups.html http://www.cups.org/sam.html#8_6 I copied the Adobe PS drivers to the mentioned location, ran cupsaddsmb and added the printer to the W2k client again. This time it worked. Give it a try and success! Jaap