Re: [Samba] Print server on all linux network
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Well, I've licked it. I upgraded to a more recent version of Samba and it took care the problem. It seems that the version I was using didn't handle users correctly in the print que, and there was something wrong with the guest setup. The new version worked out of the box. Thanks for all the help, Joel! - -Dan On Sunday 06 October 2002 20:23, Joel Hammer wrote: Hmmm... I thought you can print well from the server itself? Are you sure you were ever using BSD printing. Maybe you were really using lprng. I think samba defaults to bsd. Have you got a printing parameter in your smb.conf? Joel On Sun, Oct 06, 2002 at 07:13:17PM -0700, Dan Sawyer wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Second update: On the advice of someone else on this mailing list, I converted from BSD printing to CUPS (still using samba). Doing so has given me what is perhaps a more identifiable error message. When I send a job to the server, I check the que and get the following response: thedude@floyd:~ lpstat -t scheduler is running system default destination: lp device for lp: samba://192.168.1.101/lp lp accepting requests printer lp disabled - reason unknown lp-1thedude 164864 Sun Oct 6 19:07:36 2002 So it seems that the printer is disabled for some reason. The job just stays there in the que and never prints. - -Dan On Thursday 03 October 2002 15:23, Joel Hammer wrote: Do you understand how printing works with samba? Essentially, you just transfer the file to the samba spool directory, and invoke lpr to print the file. You will need to look at your smb.conf file to see what is supposed to happen. I would set up a share just for your printer and not rely on the generic printer share that smb.conf comes with. Here is the sort of printer share I have: This take a postscript file as input, invokes lpr to print to queue ps on the server, which translates postscript files for my lexmark printer. Joel [ps] 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 On Thu, Oct 03, 2002 at 12:47:27PM -0700, Dan Sawyer wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, everyone - I've been trying for two weeks now to get my print server operational under Samba. After walking through the howtos and tweaking the configs per spec, it just ain't working. Printing from a client machine sends, and then nothing happens. No error messages or anything similar. Printing from the server works fine, but not from the clients. Setup: 4 machine network, 3 clients, 1 samba file/print server SuSE 7.3 running on all machines. HP 2P parallel printer on lp0 of server What else can I tell you to help figure this out? - -Dan Sawyer -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE9nJ7TaB8ur/y6V8gRArm9AJ9rRc8yhDm5Catchqv4SXedOqs5qwCfSWS/ 2IayciR10uTYysD/3F24UdE= =TMQV -END PGP SIGNATURE- -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE9oO3BaB8ur/y6V8gRAiAJAJwNmGtKOhWamaEBO2oX2bTlI0T7DACfXWEj WPZ2VS/XixCF6xBqgXbDQyc= =nwXl -END PGP SIGNATURE- -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE9pJN6aB8ur/y6V8gRAldLAKCBb6kvijPQSZ2C2PgddHQenWKhgACeLYgj Y0xbKueAJHMs0xuWTUlnSeA= =sor+ -END PGP SIGNATURE- -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Print server on all linux network
Message: 10 From: Dan Sawyer [EMAIL PROTECTED] Organization: ArtisticWhispers/Blenderwars To: Joel Hammer [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: Re: [Samba] Print server on all linux network Date: Sun, 6 Oct 2002 19:13:17 -0700 Second update: On the advice of someone else on this mailing list, I converted from BSD printing to CUPS (still using samba). WHY?? (using samba) You don't need samba to do printing between two unix boxen!!! You use samba to either share a printer on a unix box to windows clients, or you setup a print spooler from a unix box to a windows print share. If you're doing both, you're wasting your time ... You can either use bsd-style lpd, or you can use CUPS (usually much easier). We added a new printer to our network on Friday. Attached it to a Mandrake 9.0 box, set it up with CUPS, waited a few minutes and it popped up on our main print server (Mandrake 8.1), restarted samba on that box to force samba to pick up the new printer (since we share all the printers and their drivers out to the windows boxen via that box, since the windows boxen are more effort to configure than the linux boxen which pick all the printers up automatically). So, I would suggest you take this to a SuSE-specific list, since they will be able to tell you where to click (it won't help me telling you to run printerdrake). Buchan -- |Registered Linux User #182071-| Buchan MilneMechanical Engineer, Network Manager Cellphone * Work+27 82 472 2231 * +27 21 8828820x121 Stellenbosch Automotive Engineering http://www.cae.co.za GPG Key http://ranger.dnsalias.com/bgmilne.asc 1024D/60D204A7 2919 E232 5610 A038 87B1 72D6 AC92 BA50 60D2 04A7 -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Print server on all linux network
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Okay, Joel, after another bit of futzing around, here's what I've come up with. The files dumped using the command you told me to DO indeed write postscript files to the directory in question. However every attempt to print those files on the server fail. However, .txt files and others print properly from the server. This leads me to believe that, somehow, the NEC Superscript printer that's running on an HP2P ghostscript driver is somehow not a postscript printer (though it quite apparently IS a postscript printer as far as I can tell). Making that change (disabling postscript) has at least gotten me to the point where I can make the printer lights blink (when attempting to print from the client from any KDE/X program), though as yet nothing is actually printing. Add to that one more layer of wierdness: When printing text files from the client, the print job executes using the shell command (cat filename.txt | smbclient //bob/nec -c 'print - '. However, when printing a file from an X program to the server, all I get are the pretty blinking lights. This leads me to the reasonable conclusion that the problems (after disabling postscript) are client-based, involving a misconfiguration of some sort. So, here's my client's /etc/printcap file. I notice with great dismay that nothing in it actually directs me to anything on the network... - -- BEGIN CLIENT /etc/printcap: # /etc/printcap: printer capability database. See printcap(5). # You can use the filter entries df, tf, cf, gf etc. for # your own filters. See the printcap(5) manual page for further # details. # # Default Postscript printer on print-serv #lp|ps|postscript:\ #:client:lp=postscript@print-serv #lp|ps|postscript:\ #:server:oh=print-serv:\ #:sd=/var/spool/lpd/ps:\ #:lp=/dev/lp1:\ #:sh:mx#0 # # Fax-Printer for SuSEFax # fax|faxprint:\ :lp=/dev/null:\ :sd=/var/spool/lpd/faxspool:\ :lf=/var/spool/lpd/faxspool/err.log:\ :if=/var/spool/lpd/faxspool/filter:\ :mx#0:\ :sh:\ :sf: ### BEGIN apsfilter: ### /etc/gs.upp/y2prn_nec.upp nec ### # Warning: Configured for apsfilter, do not edit the labels! #apsfilter setup Sat Oct 5 23:10:36 PDT 2002 # nec-ascii|lp1|y2prn_nec.upp--ascii-nec|y2prn_nec.upp ascii:\ :lp=/dev/null:\ :sd=/var/spool/lpd/y2prn_nec.upp--ascii-nec:\ :lf=/var/spool/lpd/y2prn_nec.upp--ascii-nec/log:\ :af=/var/spool/lpd/y2prn_nec.upp--ascii-nec/acct:\ :if=/var/lib/apsfilter/bin/y2prn_nec.upp--ascii-nec:\ :la:mx#0:\ :tr=:cl:sh: # nec|lp2|y2prn_nec.upp--auto-nec|y2prn_nec.upp auto:\ :lp=/dev/null:\ :sd=/var/spool/lpd/y2prn_nec.upp--auto-nec:\ :lf=/var/spool/lpd/y2prn_nec.upp--auto-nec/log:\ :af=/var/spool/lpd/y2prn_nec.upp--auto-nec/acct:\ :if=/var/lib/apsfilter/bin/y2prn_nec.upp--auto-nec:\ :la:mx#0:\ :tr=:cl:sh: # nec-raw|lp3|y2prn_nec.upp--raw-nec|y2prn_nec.upp raw:\ :lp=/dev/null:\ :sd=/var/spool/lpd/y2prn_nec.upp--raw-nec:\ :lf=/var/spool/lpd/y2prn_nec.upp--raw-nec/log:\ :af=/var/spool/lpd/y2prn_nec.upp--raw-nec/acct:\ :if=/var/lib/apsfilter/bin/y2prn_nec.upp--raw-nec:\ :la:mx#0:\ :tr=:cl:sh: # ### END apsfilter: ### /etc/gs.upp/y2prn_nec.upp nec ### - - Or, it could be a combination of server and client based. Allow me to explain. When plugging my laptop into a network with a windows based print server, I can set up the client's printer in YAST2 by telling YAST2 to browse the network and picking the appropriate name for the server and the que, and it prints without a hitch. However, on my all-linux network, when I try to browse with YAST2 it can't find any hosts. But (to make things even more fun), browsing with LinNeighborhood allows me to see the print que. Now, here's the smb.conf from the server: _ # Samba config file created using SWAT # from 192.168.1.100 (192.168.1.100) # Date: 2002/10/06 00:52:46 # Global parameters [global] workgroup = AWP netbios name = BOB server string = file and print server encrypt passwords = Yes update encrypted = Yes map to guest = Bad User null passwords = Yes large readwrite = Yes max smbd processes = 100 socket options = SO_KEEPALIVE IPTOS_LOWDELAY TCP_NODELAY character set = ISO8859-15 os level = 2 preferred master = True hosts allow = 192.168.1.100 192.168.1.101 192.168.1.102 192.168.1.103 hosts deny = ALL [homes] comment = Home Directories path = /home/burnboy read only = No create mask = 0640 directory mask = 0750 guest ok = Yes max connections = 4 write cache size = 262144
Re: [Samba] Print server on all linux network
If it makes you feel any better, from day one with my linux experience I have never gotten printing to work on my own small home network using these automatic configuration tools. This explains why I know so much about printing. Have you ever posted to me your server printcap? On the server, can you print postscript files with just lpr? Is your printer really postscript? You can test this by printing from almost any linux app, like netscape, to a file. The file will be in postscript format. Then, can you print that file by cat'ing the file to the lp of your printer. Be prepared to turn the printer off if you get a lot of junk beginning with %!PS. Or, if this fails, what happens with lpr? About your printcap not showing any network connection, that may not be necessary. The printfilter (if) will incorporate the smbclient command I sent to you. Note that you do not need to use samba to print on your all linux network. You can set up printcaps on your clients to send their jobs to the server queue. For example, here is how I have one linux client set up. z53|rp1:\ :sd=/var/spool/lpd/rp1:\ :rm=hammer2.jhammer.org:\ :rp=ps:\ :sh:mx#0: The queue ps on my server accepts text files and postscript files for printing. It uses enscript to convert text into postscript prior to printing. Once you set up this printcap entry, (as the first one in the client printcap), run checkpc -f (I assume you are using lprng). Then, just lpr your file. It should work, if the queue on your server can handle text and postscript jobs. Joel On Sun, Oct 06, 2002 at 12:44:52AM -0700, Dan Sawyer wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Okay, Joel, after another bit of futzing around, here's what I've come up with. The files dumped using the command you told me to DO indeed write postscript files to the directory in question. However every attempt to print those files on the server fail. However, .txt files and others print properly from the server. This leads me to believe that, somehow, the NEC Superscript printer that's running on an HP2P ghostscript driver is somehow not a postscript printer (though it quite apparently IS a postscript printer as far as I can tell). Making that change (disabling postscript) has at least gotten me to the point where I can make the printer lights blink (when attempting to print from the client from any KDE/X program), though as yet nothing is actually printing. Add to that one more layer of wierdness: When printing text files from the client, the print job executes using the shell command (cat filename.txt | smbclient //bob/nec -c 'print - '. However, when printing a file from an X program to the server, all I get are the pretty blinking lights. This leads me to the reasonable conclusion that the problems (after disabling postscript) are client-based, involving a misconfiguration of some sort. So, here's my client's /etc/printcap file. I notice with great dismay that nothing in it actually directs me to anything on the network... - -- BEGIN CLIENT /etc/printcap: # /etc/printcap: printer capability database. See printcap(5). # You can use the filter entries df, tf, cf, gf etc. for # your own filters. See the printcap(5) manual page for further # details. # # Default Postscript printer on print-serv #lp|ps|postscript:\ #:client:lp=postscript@print-serv #lp|ps|postscript:\ #:server:oh=print-serv:\ #:sd=/var/spool/lpd/ps:\ #:lp=/dev/lp1:\ #:sh:mx#0 # # Fax-Printer for SuSEFax # fax|faxprint:\ :lp=/dev/null:\ :sd=/var/spool/lpd/faxspool:\ :lf=/var/spool/lpd/faxspool/err.log:\ :if=/var/spool/lpd/faxspool/filter:\ :mx#0:\ :sh:\ :sf: ### BEGIN apsfilter: ### /etc/gs.upp/y2prn_nec.upp nec ### # Warning: Configured for apsfilter, do not edit the labels! #apsfilter setup Sat Oct 5 23:10:36 PDT 2002 # nec-ascii|lp1|y2prn_nec.upp--ascii-nec|y2prn_nec.upp ascii:\ :lp=/dev/null:\ :sd=/var/spool/lpd/y2prn_nec.upp--ascii-nec:\ :lf=/var/spool/lpd/y2prn_nec.upp--ascii-nec/log:\ :af=/var/spool/lpd/y2prn_nec.upp--ascii-nec/acct:\ :if=/var/lib/apsfilter/bin/y2prn_nec.upp--ascii-nec:\ :la:mx#0:\ :tr=:cl:sh: # nec|lp2|y2prn_nec.upp--auto-nec|y2prn_nec.upp auto:\ :lp=/dev/null:\ :sd=/var/spool/lpd/y2prn_nec.upp--auto-nec:\ :lf=/var/spool/lpd/y2prn_nec.upp--auto-nec/log:\ :af=/var/spool/lpd/y2prn_nec.upp--auto-nec/acct:\ :if=/var/lib/apsfilter/bin/y2prn_nec.upp--auto-nec:\ :la:mx#0:\ :tr=:cl:sh: # nec-raw|lp3|y2prn_nec.upp--raw-nec|y2prn_nec.upp raw:\ :lp=/dev/null:\ :sd=/var/spool/lpd/y2prn_nec.upp--raw-nec:\ :lf=/var/spool/lpd/y2prn_nec.upp--raw-nec/log:\ :af=/var/spool/lpd/y2prn_nec.upp--raw-nec/acct:\
Re: [Samba] Print server on all linux network
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 A followup to the last message: I have configured the Samba server to act as a WINS server, so YAST2 finds it now. Upon examining the log.smbd file, I find that there are no log entries generated when I try to print from the console or X on the client. However, the client generates no errors. - -Dan -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE9oAURaB8ur/y6V8gRAmdmAJ9Dbum6vPIqOUoYSY02mzjEt7DWeQCfR728 fr8F5bJ/A8zrYuzCaPvwaSA= =6amJ -END PGP SIGNATURE- -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Print server on all linux network
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Second update: On the advice of someone else on this mailing list, I converted from BSD printing to CUPS (still using samba). Doing so has given me what is perhaps a more identifiable error message. When I send a job to the server, I check the que and get the following response: thedude@floyd:~ lpstat -t scheduler is running system default destination: lp device for lp: samba://192.168.1.101/lp lp accepting requests printer lp disabled - reason unknown lp-1thedude 164864 Sun Oct 6 19:07:36 2002 So it seems that the printer is disabled for some reason. The job just stays there in the que and never prints. - -Dan On Thursday 03 October 2002 15:23, Joel Hammer wrote: Do you understand how printing works with samba? Essentially, you just transfer the file to the samba spool directory, and invoke lpr to print the file. You will need to look at your smb.conf file to see what is supposed to happen. I would set up a share just for your printer and not rely on the generic printer share that smb.conf comes with. Here is the sort of printer share I have: This take a postscript file as input, invokes lpr to print to queue ps on the server, which translates postscript files for my lexmark printer. Joel [ps] 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 On Thu, Oct 03, 2002 at 12:47:27PM -0700, Dan Sawyer wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, everyone - I've been trying for two weeks now to get my print server operational under Samba. After walking through the howtos and tweaking the configs per spec, it just ain't working. Printing from a client machine sends, and then nothing happens. No error messages or anything similar. Printing from the server works fine, but not from the clients. Setup: 4 machine network, 3 clients, 1 samba file/print server SuSE 7.3 running on all machines. HP 2P parallel printer on lp0 of server What else can I tell you to help figure this out? - -Dan Sawyer -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE9nJ7TaB8ur/y6V8gRArm9AJ9rRc8yhDm5Catchqv4SXedOqs5qwCfSWS/ 2IayciR10uTYysD/3F24UdE= =TMQV -END PGP SIGNATURE- -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE9oO3BaB8ur/y6V8gRAiAJAJwNmGtKOhWamaEBO2oX2bTlI0T7DACfXWEj WPZ2VS/XixCF6xBqgXbDQyc= =nwXl -END PGP SIGNATURE- -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Print server on all linux network
Hmmm... I thought you can print well from the server itself? Are you sure you were ever using BSD printing. Maybe you were really using lprng. I think samba defaults to bsd. Have you got a printing parameter in your smb.conf? Joel On Sun, Oct 06, 2002 at 07:13:17PM -0700, Dan Sawyer wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Second update: On the advice of someone else on this mailing list, I converted from BSD printing to CUPS (still using samba). Doing so has given me what is perhaps a more identifiable error message. When I send a job to the server, I check the que and get the following response: thedude@floyd:~ lpstat -t scheduler is running system default destination: lp device for lp: samba://192.168.1.101/lp lp accepting requests printer lp disabled - reason unknown lp-1thedude 164864 Sun Oct 6 19:07:36 2002 So it seems that the printer is disabled for some reason. The job just stays there in the que and never prints. - -Dan On Thursday 03 October 2002 15:23, Joel Hammer wrote: Do you understand how printing works with samba? Essentially, you just transfer the file to the samba spool directory, and invoke lpr to print the file. You will need to look at your smb.conf file to see what is supposed to happen. I would set up a share just for your printer and not rely on the generic printer share that smb.conf comes with. Here is the sort of printer share I have: This take a postscript file as input, invokes lpr to print to queue ps on the server, which translates postscript files for my lexmark printer. Joel [ps] 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 On Thu, Oct 03, 2002 at 12:47:27PM -0700, Dan Sawyer wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, everyone - I've been trying for two weeks now to get my print server operational under Samba. After walking through the howtos and tweaking the configs per spec, it just ain't working. Printing from a client machine sends, and then nothing happens. No error messages or anything similar. Printing from the server works fine, but not from the clients. Setup: 4 machine network, 3 clients, 1 samba file/print server SuSE 7.3 running on all machines. HP 2P parallel printer on lp0 of server What else can I tell you to help figure this out? - -Dan Sawyer -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE9nJ7TaB8ur/y6V8gRArm9AJ9rRc8yhDm5Catchqv4SXedOqs5qwCfSWS/ 2IayciR10uTYysD/3F24UdE= =TMQV -END PGP SIGNATURE- -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE9oO3BaB8ur/y6V8gRAiAJAJwNmGtKOhWamaEBO2oX2bTlI0T7DACfXWEj WPZ2VS/XixCF6xBqgXbDQyc= =nwXl -END PGP SIGNATURE- -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Print server on all linux network
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Well, I now got a positive response from the console, but nothing printed. Here's the console dump: thedude@floyd:~ cat kittykey.txt | smbclient //bob/nec -c 'print -' added interface ip=192.168.1.100 bcast=192.168.1.255 nmask=255.255.255.0 Got a positive name query response from 192.168.1.101 ( 192.168.1.101 ) Password: Domain=[AWP] OS=[Unix] Server=[Samba 2.2.1a] putting file - as stdin-8361 (1.7 kb/s) (average 1.7 kb/s) - -Dan On Thursday 03 October 2002 21:54, Joel Hammer wrote: Try putting a space between print and - Joel On Thu, Oct 03, 2002 at 09:32:49PM -0700, Dan Sawyer wrote: -BEGIN PGP SIGNED MESSAGE- thedude@floyd:~ cat kittykey.txt | smbclient //bob/nec -c 'print-' added interface ip=192.168.1.100 bcast=192.168.1.255 nmask=255.255.255.0 Got a positive name query response from 192.168.1.101 ( 192.168.1.101 ) Password: Domain=[AWP] OS=[Unix] Server=[Samba 2.2.1a] print-: command not found -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE9ncpOaB8ur/y6V8gRAoSDAJ9362kOuDev9LG4JnJ+ZapLBm31EwCeOsFP hFK5IHwDMCilV8987pWzTx8= =ajN9 -END PGP SIGNATURE- -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Print server on all linux network
Well, this is progress. This means that the file has been transferred to the samba server. Now, I would look at the spool directory given in your smb.conf share definition, and make sure the file got there. It may have been removed via the printing command in your share. (I blush to say I didn't save your smb.conf) Now, once it is there, I would try to print it with the command given in your smb.conf printer definition. This sounds like either a simple printer misconfiguration in smb.conf, or you need a different print filter. Can you print text files from the server with the same command you have in your smb.conf? Joel On Fri, Oct 04, 2002 at 10:05:14AM -0700, Dan Sawyer wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Well, I now got a positive response from the console, but nothing printed. Here's the console dump: thedude@floyd:~ cat kittykey.txt | smbclient //bob/nec -c 'print -' added interface ip=192.168.1.100 bcast=192.168.1.255 nmask=255.255.255.0 Got a positive name query response from 192.168.1.101 ( 192.168.1.101 ) Password: Domain=[AWP] OS=[Unix] Server=[Samba 2.2.1a] putting file - as stdin-8361 (1.7 kb/s) (average 1.7 kb/s) - -Dan On Thursday 03 October 2002 21:54, Joel Hammer wrote: Try putting a space between print and - Joel On Thu, Oct 03, 2002 at 09:32:49PM -0700, Dan Sawyer wrote: -BEGIN PGP SIGNED MESSAGE- thedude@floyd:~ cat kittykey.txt | smbclient //bob/nec -c 'print-' added interface ip=192.168.1.100 bcast=192.168.1.255 nmask=255.255.255.0 Got a positive name query response from 192.168.1.101 ( 192.168.1.101 ) Password: Domain=[AWP] OS=[Unix] Server=[Samba 2.2.1a] print-: command not found -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE9ncpOaB8ur/y6V8gRAoSDAJ9362kOuDev9LG4JnJ+ZapLBm31EwCeOsFP hFK5IHwDMCilV8987pWzTx8= =ajN9 -END PGP SIGNATURE- -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Print server on all linux network
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, everyone - I've been trying for two weeks now to get my print server operational under Samba. After walking through the howtos and tweaking the configs per spec, it just ain't working. Printing from a client machine sends, and then nothing happens. No error messages or anything similar. Printing from the server works fine, but not from the clients. Setup: 4 machine network, 3 clients, 1 samba file/print server SuSE 7.3 running on all machines. HP 2P parallel printer on lp0 of server What else can I tell you to help figure this out? - -Dan Sawyer -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE9nJ7TaB8ur/y6V8gRArm9AJ9rRc8yhDm5Catchqv4SXedOqs5qwCfSWS/ 2IayciR10uTYysD/3F24UdE= =TMQV -END PGP SIGNATURE- -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Print server on all linux network
Do you understand how printing works with samba? Essentially, you just transfer the file to the samba spool directory, and invoke lpr to print the file. You will need to look at your smb.conf file to see what is supposed to happen. I would set up a share just for your printer and not rely on the generic printer share that smb.conf comes with. Here is the sort of printer share I have: This take a postscript file as input, invokes lpr to print to queue ps on the server, which translates postscript files for my lexmark printer. Joel [ps] 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 On Thu, Oct 03, 2002 at 12:47:27PM -0700, Dan Sawyer wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, everyone - I've been trying for two weeks now to get my print server operational under Samba. After walking through the howtos and tweaking the configs per spec, it just ain't working. Printing from a client machine sends, and then nothing happens. No error messages or anything similar. Printing from the server works fine, but not from the clients. Setup: 4 machine network, 3 clients, 1 samba file/print server SuSE 7.3 running on all machines. HP 2P parallel printer on lp0 of server What else can I tell you to help figure this out? - -Dan Sawyer -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE9nJ7TaB8ur/y6V8gRArm9AJ9rRc8yhDm5Catchqv4SXedOqs5qwCfSWS/ 2IayciR10uTYysD/3F24UdE= =TMQV -END PGP SIGNATURE- -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Print server on all linux network
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Okay, I've removed the [printers] tab. When I print locally, I do indeed use lpr -Pnec (or at least, that command works very well). However, using that command from the client doesn't do a thing for me (nor does printing from a gui program). I've now modified the .conf so it looks like this: [nec] comment = NEC Superscript 1200 path = /tmp read only = No create mask = 0700 guest ok = Yes hosts allow = 192.168. printable = Yes postscript = Yes print command = lpr -Pnec 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 printer name = nec share modes = No What's the next step? - -Dan On Thursday 03 October 2002 16:54, Joel Hammer wrote: I would remove [printers] since neither you or I know what it really does. Now, when you print locally, you print to the queue nec? This will depend on the lpr command (lpr -Pnec) or if you just use lpr the first printer defined in you /etc/princap will be invoked. Joel -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE9nOFkaB8ur/y6V8gRAj0NAJ9uBivobBUug7ILKnWtvTWFSF7VfACgoE+7 znVXZF5BGzp7IIGXHH19lEo= =0C98 -END PGP SIGNATURE- -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Print server on all linux network
Well, you have to talk to the samba server from the client: The basic command is as follows: cat file | smbclient //server/nec -c 'print -' Does this command work for you? The file has to be in a format the printer (queue) can use on the server. If this works, then you can set up print queues on the clients to do this. Joel On Thu, Oct 03, 2002 at 05:31:28PM -0700, Dan Sawyer wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Okay, I've removed the [printers] tab. When I print locally, I do indeed use lpr -Pnec (or at least, that command works very well). However, using that command from the client doesn't do a thing for me (nor does printing from a gui program). I've now modified the .conf so it looks like this: [nec] comment = NEC Superscript 1200 path = /tmp read only = No create mask = 0700 guest ok = Yes hosts allow = 192.168. printable = Yes postscript = Yes print command = lpr -Pnec 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 printer name = nec share modes = No What's the next step? - -Dan On Thursday 03 October 2002 16:54, Joel Hammer wrote: I would remove [printers] since neither you or I know what it really does. Now, when you print locally, you print to the queue nec? This will depend on the lpr command (lpr -Pnec) or if you just use lpr the first printer defined in you /etc/princap will be invoked. Joel -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE9nOFkaB8ur/y6V8gRAj0NAJ9uBivobBUug7ILKnWtvTWFSF7VfACgoE+7 znVXZF5BGzp7IIGXHH19lEo= =0C98 -END PGP SIGNATURE- -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Print server on all linux network
Try putting a space between print and - Joel On Thu, Oct 03, 2002 at 09:32:49PM -0700, Dan Sawyer wrote: -BEGIN PGP SIGNED MESSAGE- thedude@floyd:~ cat kittykey.txt | smbclient //bob/nec -c 'print-' added interface ip=192.168.1.100 bcast=192.168.1.255 nmask=255.255.255.0 Got a positive name query response from 192.168.1.101 ( 192.168.1.101 ) Password: Domain=[AWP] OS=[Unix] Server=[Samba 2.2.1a] print-: command not found -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
