I cannot print to my Samba-printer from Win NT. Printing works fine under X-windows. What could be wrong? //Michael
Hi,
I installed Samba 2.0.3 on my Irix6.2 machine and now have a PC mount my
Irix files successfully.
Now, I am trying to print from the PC to the printer connected to the
UNIX network. I have "lp" setup on my Irix network such that it logs
to
/var/spool/lp.
I edited the smb.conf file to have proper "print command". Now when I
try to "add printer" from my PC (Win 98), it is recognizing
\\server\lp
but when it tries to print a test page, it says "unknown system
error".
Now, I try to use smbclient to do the print. I logon. Then when I do
"print file", the contents of the file are gone (becomes 0 bytes). I
have tied changing lot of things in my smb.conf file, but no success.
Here is my testparm result:
# Global parameters
workgroup = WORKGROUP
netbios name =
netbios aliases =
server string = Samba 2.0.3
interfaces =
bind interfaces only = No
security = USER
encrypt passwords = No
update encrypted = No
use rhosts = No
min passwd length = 5
map to guest = Never
null passwords = No
password server =
smb passwd file = /usr/samba/private/smbpasswd
hosts equiv =
root directory = /
passwd program = /usr/bin/passwd %u
passwd chat = *ew*password:* %n\n *e-enter*new*password:* %n\n
passwd chat debug = No
username map =
password level = 0
username level = 0
unix password sync = No
log level = 2
syslog = 1
syslog only = No
log file =
max log size = 50
timestamp logs = Yes
protocol = NT1
read bmpx = Yes
read raw = Yes
write raw = Yes
nt smb support = Yes
nt pipe support = Yes
nt acl support = No
announce version = 4.2
announce as = NT
max mux = 50
max xmit = 65535
name resolve order = lmhosts host wins bcast
max packet = 65535
max ttl = 259200
max wins ttl = 518400
min wins ttl = 21600
time server = No
change notify timeout = 60
deadtime = 0
getwd cache = Yes
keepalive = 300
lpq cache time = 10
max disk size = 0
max open files = 10000
read prediction = No
read size = 16384
shared mem size = 1048576
socket options = TCP_NODELAY
stat cache size = 50
load printers = Yes
printcap name = lpstat
printer driver file = /usr/samba/lib/printers.def
strip dot = No
character set =
mangled stack = 50
coding system =
client code page = 850
stat cache = Yes
domain groups =
domain admin group =
domain guest group =
domain admin users =
domain guest users =
machine password timeout = 604800
add user script =
delete user script =
logon script = %U.bat
logon path = \\%N\%U\profile
logon drive =
logon home = \\%N\%U
domain logons = Yes
os level = 0
lm announce = Auto
lm interval = 60
preferred master = No
local master = No
domain master = No
browse list = Yes
dns proxy = Yes
wins proxy = No
wins server =
wins support = Yes
kernel oplocks = Yes
ole locking compatibility = Yes
smbrun = /usr/samba/bin/smbrun
config file =
preload =
lock dir = /usr/samba/var/locks
default service =
message command =
dfree command =
valid chars =
remote announce =
remote browse sync =
socket address = 0.0.0.0
homedir map =
time offset = 0
unix realname = No
NIS homedir = No
panic action =
comment = Samba %v
path =
alternate permissions = No
revalidate = No
username =
guest account = nobody
invalid users =
valid users =
admin users =
read list =
write list =
force user =
force group =
read only = Yes
create mask = 0744
force create mode = 00
directory mask = 0755
force directory mode = 00
guest only = No
guest ok = No
only user = No
hosts allow =
hosts deny =
status = Yes
max connections = 0
min print space = 0
strict sync = No
sync always = No
print ok = No
postscript = No
printing = sysv
print command = /usr/bin/lp -c -d%p -t"%U on machine %m" %s ;
rm
%s
lpq command = lpstat -o%p
lprm command = cancel %p-%j
lppause command = lp -i %p-%j -H hold
lpresume command = lp -i %p-%j -H resume
queuepause command = lpc stop %p
queueresume command = lpc start %p
printer name = hops
printer driver = NULL
printer driver location =
default case = lower
case sensitive = No
preserve case = Yes
short preserve case = Yes
mangle case = No
mangling char = ~
hide dot files = Yes
delete veto files = No
veto files =
hide files =
veto oplock files =
map system = No
map hidden = No
map archive = Yes
mangled names = Yes
mangled map =
browseable = Yes
blocking locks = Yes
fake oplocks = No
locking = Yes
oplocks = Yes
strict locking = No
share modes = Yes
copy =
include =
exec =
postexec =
root preexec =
root postexec =
available = Yes
volume =
fstype = NTFS
set directory = No
wide links = Yes
follow symlinks = Yes
dont descend =
magic script =
magic output =
delete readonly = No
dos filetimes = No
dos filetime resolution = No
fake directory create times = No
[homes]
comment = Home Directories
read only = No
browseable = No
[printers]
comment = All Printers
path = /usr/tmp
create mask = 0700
guest ok = Yes
print ok = Yes
browseable = No
[tmp]
comment = Temporary file space
path = /usr/tmp
read only = No
guest ok = Yes
[netlogon]
path = /data/dos/netlogon
Is anything obviously wrong? Any ideas? Thanks, and please note that I
am not in the list, so plese email me directly.
Thanks.
--
Prakash Mahesh
prakash@drawcomp.com
--or--
prakash@openworlds.com
I am using Samba 2.0.3 and have set up a printer to share. The printer works fine from the server but, when I print from a Windoze box, Windoze sends the print job and is happy. The job never prints. As far as I can tell it never makes it to the print queue. I have an identical configuration on a different server running Samba 1.9.18p5 and it works fine. Does anyone have any suggestions? Thanks BRG
I am having a strange problem on my Samba server. It is : RedHat 6.0 (Intel) Samba 2.05a 9 printers with HP JetDirect devices Occasionally, 2 or 3 printers will just stop printing and report in windows print manager that they are paused. To get the printers to print again, I must stop lpd manually remove the spool files from the print spool directories and the restart lpd. Any ideas as to what could cause this problem or a remedy to fix it. Thanks Brian Ginter brian.ginter@southern-air.com (804) 385-1277 Southern Air, Inc. http://www.southern-air.com
I was searching through the list archives for a solution to this problem but
couldn't find one. All I could find was other people asking the same thing.
How do I solve this error:
There was a problem printing to the printer due to an unknown system error.
Restart Windows, and then try printing again.
This printer will be set to work off-line.
To save your print job in the local printer queue, click OK.
OK Cancel
Here is my smb.conf
# Global parameters
[global]
workgroup = OIS
netbios name = SERVER2
encrypt passwords = Yes
restrict anonymous = Yes
log level = 4
max log size = 0
domain logons = Yes
os level = 65
preferred master = Yes
domain master = Yes
wins support = Yes
valid users = aworthin, dbrown, kbrown
[homes]
read only = No
browseable = No
[netlogon]
path =
/usr/local/server2/samba/netlogon
[smbdocs]
path = /usr/local/server2/src/samba-2.0.5a/docs
[staff]
path = /home/staff
read only = No
[files]
path = /home/staff/files
read only = No
[laserjet]
path = /var/spool/lpd/laserjet
print ok = Yes
postscript = Yes
Here is my /etc/printcap file:
laserjet:\
:sd=/var/spool/lpd/laserjet:\
:mx#0:\
:sh:\
:rm=laserjet:\
:rp=raw:\
:if=/var/spool/lpd/laserjet/filter:
Thanks
Andy Worthington
-------------- next part --------------
HTML attachment scrubbed and removed
Hello !! I have samba 2.0.4b on server IBM - AIX 4.2 and the clients are about 40 win 95/98 and i have the following problem: i don't know why, but at a certain point can print only the user 'root', all other users send the print and the temporany file is blocked in the printer path of the smb.conf. The log file tell: [1999/09/15 08:04:36, 0] lib/smbrun.c:(127) smbrun: fork failed with error Resource temporarily unavailable . I stop the samba process, i restart samba and all the users can print. Can you help me !! Thank you Claudia
help? I am trying to set up a samba server to print. a book I have says to copy the windows inf files msprint.inf and msprint2.inf to the linux box from the windows box. book says the files should be in c:\windows\inf directory. I cannot find these on my windows 98 machine. any idea where they are? thanks.
On Fri, 29 Oct 1999 16:06:22 +1000, hai scritto:>help? I am trying to set up a samba server to print. a book I have says to >copy the windows inf files msprint.inf and msprint2.inf to the linux box from >the windows box. book says the files should be in c:\windows\inf directory.This is only needed to download printer drivers from the samba machines to win9x machines. You can print through samba withouth doing this. I think you should start printing, and after that you see it works, then you can add drivers download. -- giulioo@tiscalinet.it
Hi all,
I am having problems printing from Win95 clients to an RS/6000 box
running AIX 4.3.3 using Samba 2.0.5a.
I have been using Samba for quite some time now on various *NIX
platforms without ever encountering any major problems. On the machine
in question, I recently upgraded AIX form 4.2.1 to 4.3.2. After this
upgrade Samba continued to function properly. However, this past
Saturday (11/6/99) I applied some patches to AIX to bring the os level
up to 4.3.3. After rebooting the system I did attempt a print job from
a Win95 client which worked successfully. I also see in the Samba logs
one other successful print job. Since that job, however no other print
jobs have completed. My Samba print directory is /tmp and I do see
files being created in this directory in the usual manner however
nothing ever gets passed to the spooler. I have verified that AIX
printing is working properly.
When I send a print job I get the following in the log.smb:
jrw106 (129.100.201.10) connect to service lp_mis as user jrw (uid=12,
gid=11)
(pid 58722)
[1999/11/08 13:31:22, 0] lib/smbrun.c:smbrun(128)
smbrun: fork failed with error Resource temporarily unavailable
[1999/11/08 13:31:22, 0] lib/smbrun.c:smbrun(128)
smbrun: fork failed with error Resource temporarily unavailable
[1999/11/08 13:31:22, 0] lib/smbrun.c:smbrun(128)
smbrun: fork failed with error Resource temporarily unavailable
[1999/11/08 13:31:25, 0] lib/smbrun.c:smbrun(128)
smbrun: fork failed with error Resource temporarily unavailable
Other Samba functions such as copying files seem to work correctly.
Besides this printing problem all other processes seem OK on the
RS/6000.
I am not sure where to go from here. Any thoughts or suggestions
would be appreciated.
Thank You in Advance,
John Welch
Systems Analyst
Brockway-Smith Co.
I am trying to print from my samba server to an NT printer. In my /etc/printcap i am using if=/usr/bin/smbprint. I can print if I manually use smbclient and give a valid user name and password. When I use smbclient to print to the specific printer with the -N option I get a access denied error. Basically NT is not letting me access the printer. I do not have the printer password protected. It is an HP4000 LaserJet off a HP jetdirect print server. Any ideas on how I need to set this up correctly to print? Thanks, Charles R. Gatrelle Network Administrator SecureLogix Corporation Direct/Voice mail: (210)402-9669 x 926 mailto:cgatrelle@securelogix.com This email is intended for the named recipient(s) only and may contain information that is privileged and/or confidential. Nothing in this email is intended to constitute a waiver of any privilege or the confidentiality of this message. If you have received this email in error, please notify me immediately by reply and delete this message.
I'm trying to get a printer share running off a Redhat 6.1 machine using samba 2.0.5a. I have the printers set up on the samba redhat box. They work great from the command line etc.. lpr -Pprinter file... All users can print from the RH box.. The problem is that when net users print to the shared printers nothing happens.. Well nothing in the printer room atleast! All the documents get queued up in the /var/spool/samba directory. I've tried changing the print owner from nobody to users on the system as well as root! They still all get sent to /var/spool/samba where they sit until I delete them.. Checking the print queues out with lpc and lpq reveal nothing waiting to be printed.... All of the shared printers are browsable from the network neighborhood. Although I haven't automated the drivers (yet). Permissions on the /var/spool/samba directory are drwxrwxrwxt so user NOBODY should be able to print... errr! Does anyone have a clue what I am doing wrong?? I think I've tried every config switch with swat to no avail. Any help would be appreciated. Thanks Bob Robert Bartels Network Administrator Department of Physiology MS571 Chandler Medical Center University of Kentucky 40536 606.323.6264 physiology.uky.edu
Hello, I've got 2 problems with printing with HP Network printers and Samba. I'm using an logon script (logon.bat) with : # connecting to hp5 jetdirect net use \\server\hp1 lpt2: # connecting to hp2000 jetdirect net use \\server\hp2 ltp3: The script returns with an error on the second line (unable to find share <abort><retry<fail>). If you choose fail, the connection is made and no other errors occure. Has anyone seen the same problem? The second problem is with queueing. When two users are printing at the same time, only the first users document is printed. I'm using lprng with the default configuration as from the HP JetDirect manual. With kind regards, Micha Kersloot KovoKs Automatiseringspartner
Hi, need help! I have installed dual samba (both with the newest cvs) now I would like to print on the HEAD server (domain member). If I try to connect to the printer I get an errormessage :"The connection could not be established. There is not enough memory." What I am doing wrong or what is going wrong ??? Sascha
This showed up on a Windows XP machine with 2.2.4 -- I'm reverting back to a 2.2.4-pre version that was running fine (at least I never saw this problem before I upgraded the other day). [2002/06/06 18:30:12, 0] rpc_client/cli_pipe.c:rpc_api_pipe(359) cli_pipe: return critical error. Error was NT_STATUS_INVALID_PIPE_STATE [2002/06/06 18:30:12, 0] rpc_server/srv_spoolss_nt.c:srv_spoolss_replycloseprinter(177) srv_spoolss_replycloseprinter: reply_close_printer failed [DOS code 0x0000001f]. [2002/06/06 18:30:12, 0] rpc_client/cli_pipe.c:rpc_api_pipe(359) cli_pipe: return critical error. Error was NT_STATUS_INVALID_PIPE_STATE [2002/06/06 18:30:12, 0] rpc_server/srv_spoolss_nt.c:srv_spoolss_replycloseprinter(177) srv_spoolss_replycloseprinter: reply_close_printer failed [DOS code 0x0000001f]. [2002/06/06 18:30:12, 0] rpc_client/cli_pipe.c:rpc_api_pipe(359) cli_pipe: return critical error. Error was NT_STATUS_INVALID_PIPE_STATE [2002/06/06 18:30:12, 0] rpc_server/srv_spoolss_nt.c:srv_spoolss_replycloseprinter(177) srv_spoolss_replycloseprinter: reply_close_printer failed [DOS code 0x0000001f]. [2002/06/06 18:30:12, 0] rpc_client/cli_pipe.c:rpc_api_pipe(359) cli_pipe: return critical error. Error was NT_STATUS_INVALID_PIPE_STATE [2002/06/06 18:30:12, 0] rpc_server/srv_spoolss_nt.c:srv_spoolss_replycloseprinter(177) srv_spoolss_replycloseprinter: reply_close_printer failed [DOS code 0x0000001f]. Michael D. Black mblack@csihq.com http://www.csihq.com/ http://www.csihq.com/~mike 321-676-2923, x203 Melbourne FL
When printing locally the printer works fine, but when I try to print from a client computer the following message prints out. ****Unable to open the initial device, quitting. Can any body help with this problem.
Post: 1. Your printing system (lprng, etc.) 2. Your smb.conf 3. Your printer 4. Your /etc/printcap 5. The print driver you are using for your printer. 6. Your flavor of unix/linux. 7. The client OS. This information may help. Joel On Sun, Jun 16, 2002 at 03:11:25PM -0400, Joe Carmon wrote:> When printing locally the printer works fine, but when I try to print from > a client computer the following message prints out. > > ****Unable to open the initial device, quitting. > > Can any body help with this problem. > > > > -- > To unsubscribe from this list go to the following URL and read the > instructions: http://lists.samba.org/mailman/listinfo/samba
Just some observations while you figure out what is wrong.
I can't comment much about your printcap because I don't use gimp to
print, I use ghostscript. Have you run checkpc -f to look for errors and
adjust permissions on your spool directories?
Your path in your smb.conf looks odd. Usually, that path is put someplace
like /tmp. Could there be a permissions problem?
You have only one print queue. This queue must be able therefore to handle
ALL file types, including those sent from your clients. Now, your linux
server sends postscript files which seem to be printed OK. I do not know if
your linux print queue handles files formatted by the windows
clients. What print driver are you using on your windows clients?
(windows may call it a printer definition). You can test this by printing
to a file on your windows client, and then transferring that file to
your linux server, and then lpr'ing the file. This is what samba does, by
the way.
A very nice and easy work around in this situation is as follows:
If your linux server prints postscript files well, using just that one
queue, then on your clients install the network printer using the HP
laserjet III plus as the printer definition. This driver will send
postscript files to your server, which your server will handle. Postscript
is THE printer language for linux, after all. I do not know why this isn't
considered a general solution for linux print servers.
The other thing to try is to set up a print queue in /etc/printcap which has
NO filter and install the proper drivers on your windows clients for your
printer. Such a raw queue will just dump the print file to your printer. You
will have to negotiate printtool to do this. Or, disable the automatic call
to printtool in your lpd startup script.
Here is my smb.conf regarding printing matters. I use guest logins and have
therefore less security but fewer headaches. I use the %J variable to capture
the windows file name. I list all the printing commands explicitly.
# Global parameters
[global]
security = SHARE
guest account = ftp
hosts allow = 192.168. 127.0.0.
[ps]
comment = Filtered for Z53
path = /tmp
read only = No
create mask = 0700
guest ok = Yes
hosts allow = 192.168.
printable = Yes
printing = lprng
print command = echo %J %p %s >> /tmp/junkJ;\
a="`echo '%J' | sed "s/^.*-
//"`" ;\
echo This is truncated $a >> /tmp/junkJ;\
/usr/bin/lpr -Pps -J"$a" %s;\
rm %s
lpq command = /usr/bin/lpq -Pps
lprm command = /usr/bin/lprm -Pps %j
lppause command = /usr/sbin/lpc hold z53 %j
lpresume command = /usr/sbin/lpc release z53 %j
share modes = No
use client driver = yes
You aren't the only one to have trouble with the RedHat printtool. I dumped
mine after it failed to set up my network printer properly.
Joel
On Sun, Jun 16, 2002 at 03:37:47PM -0400, Joe Carmon
wrote:>
> >1. Your printing system (lprng, etc.)-- LPR
> >2. Your smb.conf
> >3. Your printer EPson Stylus Color 980
> >4. Your /etc/printcap
> >5. The print driver you are using for your printer.-- Gimp
> >6. Your flavor of unix/linux. Red Hat 7.3
> >7. The client OS. -- Win 2k PRO, Windows 98 SE
>
> The printcap and smb.conf files are attached.
>
>
>
> >This information may help.
> >Joel
> >
> >On Sun, Jun 16, 2002 at 03:11:25PM -0400, Joe Carmon wrote:
> > > When printing locally the printer works fine, but when I try to
print from
> > > a client computer the following message prints out.
> > >
> > > ****Unable to open the initial device, quitting.
> > >
> > > Can any body help with this problem.
> > >
> > >
> > >
> > > --
> > > To unsubscribe from this list go to the following URL and read
the
> > > instructions: http://lists.samba.org/mailman/listinfo/samba
For future reference, as these questions get asked again and again, can you describe in detail just what was misconfigured? Thanks, Joel On Mon, Jun 17, 2002 at 08:43:06AM -0400, Joe Carmon wrote:> Thanks for the nudge in the right direction. It was a mis-configured driver > that printer driver. > > At 04:12 PM 6/16/2002 -0400, you wrote: > >Just some observations while you figure out what is wrong. > > > >I can't comment much about your printcap because I don't use gimp to > >print, I use ghostscript. Have you run checkpc -f to look for errors and > >adjust permissions on your spool directories? > > > >Your path in your smb.conf looks odd. Usually, that path is put someplace > >like /tmp. Could there be a permissions problem? > > > >You have only one print queue. This queue must be able therefore to handle > >ALL file types, including those sent from your clients. Now, your linux > >server sends postscript files which seem to be printed OK. I do not know if > >your linux print queue handles files formatted by the windows > >clients. What print driver are you using on your windows clients? > >(windows may call it a printer definition). You can test this by printing > >to a file on your windows client, and then transferring that file to > >your linux server, and then lpr'ing the file. This is what samba does, by > >the way. > > > >A very nice and easy work around in this situation is as follows: > >If your linux server prints postscript files well, using just that one > >queue, then on your clients install the network printer using the HP > >laserjet III plus as the printer definition. This driver will send > >postscript files to your server, which your server will handle. Postscript > >is THE printer language for linux, after all. I do not know why this isn't > >considered a general solution for linux print servers. > > > >The other thing to try is to set up a print queue in /etc/printcap which has > >NO filter and install the proper drivers on your windows clients for your > >printer. Such a raw queue will just dump the print file to your printer. You > >will have to negotiate printtool to do this. Or, disable the automatic call > >to printtool in your lpd startup script. > > > >Here is my smb.conf regarding printing matters. I use guest logins and have > >therefore less security but fewer headaches. I use the %J variable to capture > >the windows file name. I list all the printing commands explicitly. > > > > > ># Global parameters > >[global] > > security = SHARE > > guest account = ftp > > hosts allow = 192.168. 127.0.0. > >[ps] > > comment = Filtered for Z53 > > path = /tmp > > read only = No > > create mask = 0700 > > guest ok = Yes > > hosts allow = 192.168. > > printable = Yes > > printing = lprng > > print command = echo %J %p %s >> /tmp/junkJ;\ > > a="`echo '%J' | sed "s/^.*- //"`" ;\ > > echo This is truncated $a >> /tmp/junkJ;\ > > /usr/bin/lpr -Pps -J"$a" %s;\ > > rm %s > > lpq command = /usr/bin/lpq -Pps > > lprm command = /usr/bin/lprm -Pps %j > > lppause command = /usr/sbin/lpc hold z53 %j > > lpresume command = /usr/sbin/lpc release z53 %j > > share modes = No > > use client driver = yes > > > >You aren't the only one to have trouble with the RedHat printtool. I dumped > >mine after it failed to set up my network printer properly. > > > >Joel > > > >On Sun, Jun 16, 2002 at 03:37:47PM -0400, Joe Carmon wrote: > > > > > > >1. Your printing system (lprng, etc.)-- LPR > > > >2. Your smb.conf > > > >3. Your printer EPson Stylus Color 980 > > > >4. Your /etc/printcap > > > >5. The print driver you are using for your printer.-- Gimp > > > >6. Your flavor of unix/linux. Red Hat 7.3 > > > >7. The client OS. -- Win 2k PRO, Windows 98 SE > > > > > > The printcap and smb.conf files are attached. > > > > > > > > > > > > >This information may help. > > > >Joel > > > > > > > >On Sun, Jun 16, 2002 at 03:11:25PM -0400, Joe Carmon wrote: > > > > > When printing locally the printer works fine, but when I try to > > print from > > > > > a client computer the following message prints out. > > > > > > > > > > ****Unable to open the initial device, quitting. > > > > > > > > > > Can any body help with this problem. > > > > > > > > > > > > > > > > > > > > -- > > > > > To unsubscribe from this list go to the following URL and read the > > > > > instructions: http://lists.samba.org/mailman/listinfo/samba
I've got a HP JetDirect printer that I print to through Samba. I use Windows XP to print to it. It works fine. The only problem is that if I shut the printer off, Samba loses it. I can't print again until Samba is restarted. Any thoughts? -------------- next part -------------- HTML attachment scrubbed and removed
Hello, this is the first time I am wrting to this list.
I have a Ricoh Aficio 1015 printer/copier that, unfortunately,
is not supported under linux. I have a Debian "testing" linux
box running as a PDC as well as a file, fax, etc... server and I want it
to
work as a printing server, too.
I have downloaded the latest Samba release 2.2.5,
which allows two configure a printer
using the Windows 2000 device drivers provided by the
manufacturer. I have defined an entry in the /etc/printcap file
for the printer:
ricoh|ricoh aficio 1015:\
:lp=/dev/lp0:sd=/var/spool/lpd/ricoh:\
:sh:pw#80:pl#72:px#1440:mx#0:\
:af=/var/log/lp-acct:lf=/var/log/lp-errs:
Next, I login the server as "root" fron a windows 2000
client and I add the windows drivers for the printer,
drivers that are uploaded in the linux server successfully.
Finally, when I try to print a test page, I get an error
from the windows 2000 client
"Operation could not be completed" and no log
message is registered in the linux server.
May the problem arise from the /etc/printcap
configuration? And from the conection between
samba and lprng?I am using lprng 3.8.10-1
Samba smb.conf related entries are currently
setup as follows:
total print jobs = 0
load printers = Yes
printcap name = /etc/printcap
addprinter command deleteprinter command show add
printer wizard = Yes
printer admin = root
min print space = 0
max print jobs = 1000
printable = No
printing = lprng
print command = lpr -r -P%p %s
printer name printer driver printer driver file =
/usr/local/samba/lib/printers.def
printer driver location
Any help would be greatly appreciated.
Thanks in advance,
Manuel Arenaz
arenaz: | Hello, this is the first time I am wrting to this list. | | I have a Ricoh Aficio 1015 printer/copier that, unfortunately, | is not supported under linux. I have a Debian "testing" linux | box running as a PDC as well as a file, fax, etc... server and I want it | to | work as a printing server, too. | | I have downloaded the latest Samba release 2.2.5, | which allows two configure a printer | using the Windows 2000 device drivers provided by the | manufacturer. I have defined an entry in the /etc/printcap file | for the printer: | | ricoh|ricoh aficio 1015:\ | :lp=/dev/lp0:sd=/var/spool/lpd/ricoh:\ | :sh:pw#80:pl#72:px#1440:mx#0:\ | :af=/var/log/lp-acct:lf=/var/log/lp-errs: This seems okay but someone with a more keen eye may disagree. | Next, I login the server as "root" fron a windows 2000 | client and I add the windows drivers for the printer, | drivers that are uploaded in the linux server successfully. | Finally, when I try to print a test page, I get an error | from the windows 2000 client | "Operation could not be completed" and no log | message is registered in the linux server. Is it the samba log or is it the lprng log you fail to see? Both lprng and samba has many levels of debug facilities... | May the problem arise from the /etc/printcap | configuration? And from the conection between | samba and lprng?I am using lprng 3.8.10-1 | Samba smb.conf related entries are currently | setup as follows: | | total print jobs = 0 | load printers = Yes | printcap name = /etc/printcap | addprinter command | deleteprinter command | show add printer wizard = Yes | printer admin = root | min print space = 0 | max print jobs = 1000 | printable = No | printing = lprng | print command = lpr -r -P%p %s | printer name | printer driver | printer driver file = /usr/local/samba/lib/printers.def | printer driver location As far as I can see you shold include path = /some/public/spool. Check out man smb.conf for details. To be absolutely sure about the loggin I would use [global] log file = somepath debug level = something Nonetheless, you should be able to tail the sambalog if you set debug level high. My hunch is that there is something with a missing spool or that some access right is wrong. What I would recommend is: 1. get a yellow cat (inside joke) 2. set up a bogous printer and print to a file. 2.1 check that the lprng works. 2.1 tail logs 3. set up samba 3.1 turn on logging 3.2 tail the log 3.3 identify the problem 4. cuddle the yellow cat (still a inside joke) :) By the way, I may be out on a limb here - my samba/lprng knowledge is somewhat rusty. -- Sverre S.
I have moved my epson stylus color 800 to my redhat 7.2 server and I am printing fine. Except for one daunting problem. I am unable to print more than one copy. I have originally installed it using bsd and the stcolor driver stp froze the machine. anyway I moved to cups and again I can print fine and locally on the server I can print as many copies as I want. I cannot still print more than one copy from my windows boxes xp,2000,me,98. I am stumped can anyone help. Please reply direct to gary@gneff.com
I'm using Samba 2.2.7, RH 7.3, CUPS printing to a Canon BJC-265SP, accessing the "shared" printer via either regular network connection from a WinXP workstation or via VMWare WinXP; I've "shared" the printer via Samba, but when printing, instead of EOL's, the printer is receiving EOP's - (for each line printed to the printer, a new sheet gets put in instead of an end-of-line)...hence, printing is not good. Any suggestions? TIA, Stephen -- Mon Dec 9 15:00:00 EST 2002 3:00pm up 18:45, 5 users, load average: 0.40, 0.33, 0.47 .o0 linux user:267497 0o. -------------------------------- | __ __ | k?hn media australia | / \ /| |'-. | http://kma.0catch.com | .\__/ || | | | | _ / `._ \|_|_.-' | stephen k?hn | | / \__.`=._) (_ | email: skuhn@telpacific.com.au | |/ ._/ |"""""""""| | email: stephen.kuhn@gmx.net | |'. `\ | | | icq: 5483808 | ;"""/ / | | | | smk ) /_/| |.-------.| | mobile: 0410-728-389 | ' `-`' " " | Berkeley, New South Wales, AU -------------------------------- Coralament*Best Gr?tens*Liebe Gr??e*Best Regards*Elkorajn Salutojn Gypsy robot: You want to die? Bender: No, I wanna live! There's still too many things I don't own.
not sure what Iv'e messed up here, but I did have my mandrake 9 server
sharing it's printer to my windows boxes with samba.
I reinstalled linus on the server, and replaced winxp with mandrake 9 on one
workstation.
the linux workstation and server each have a printer connected and both machines
can use each others printers.
I have been trying for a week to get the windows boxes to use the printers to no
avail.
The printers are found and installed, but the print jobs disappear....no errors.
any ideas?
oh yeah, below is part of my smb.conf
#============== Global Settings ====================[global]
workgroup = CURRICULUM
netbios name = hal
load printers = yes
security = server
server string = Samba Server %v
passwd chat = *New*UNIX*password* %n\n *ReType*new*UNIX*password* %n\n
printing = cups
default = home
password server = 192.168.0.1
update encrypted = no
encrypt passwords = no
passwd program = /usr/bin/passwd %u
domain logons = no
wins server = 192.168.0.1
local master = yes
preferred master = No
domain master = No
socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
#============ Share Definitions ==============
[printers]
comment = All Printers
path = /var/spool/samba
read only = No
create mask = 0700
guest ok = yes
hosts allow = 192.168.
printable = Yes
printing = cups
use client driver = yes
print command = lpr-cups -P %p %s # using cups own drivers (use generic
PostScript on clients).
lpq command = lpstat -o %p
lprm command = cancel %p-%j
browseable = yes