Hello Family, My RedHat-7.2 box prints perfectly to an Epson777 color injet printer which I gave an IP address via a mini printserver attached to the back of the printer. I have a Windows2000 computer hooking into the same RedHat-7.2 box via Samba-2.2.2 fine. I have not been able to get my Windows2000 box to print to the Epson777 color injet via Samba. [question] Since Linux already "filters" the docs it prints should I send the Windows2000 files to the Linux box in RAW mode and let Linux filter the text ? If there is any "Windows2000 && Samba && Printing" success stories (smb.conf files) or http://links to resources I'd appreciate it. I've tried printing straight from the Windows2000 box to the Epson777 color injet (static ip to statice ip) but for the life of me can't get even a chirp out of the printer. -- Bill Schoolcraft PO Box 210076 -o) San Francisco CA 94121 /\ "UNIX, A Way Of Life." _\_v http://forwardslashunix.com
Just a few ideas. As far as I know, windows does all the print filtering. The only exception is postscript. linux/samba can process a postscript file from windows (created using a postscript filter definition). If the printer is postscript, it can be just dumped to the printer, but, if the printer is not postscript, linux could filter the postscript job for you. I would first try to install the proper printer definition in windows, and send your print jobs to samba to a raw print filter, ie, one that just dumps the job to the printer. This is usually called lp on the linux box and is the preferred way of doing this sort of thing. If the problem is installing the Epson driver files on windows, you could bypass that by choosing a postscript printer definition in windows, and then sending that job to the filtering print queue on linux, usually call ps. You say linux prints pefectly to this printer. Have you tried text files as well as postscript files (postscript is generated from most linux software, including netscape.) Text file require enscript, which postscript files do not. N.B. I have found that the test page you print after installation is sent to the raw queue, not the filtered queue, so a test page may print but nothing else will. Joel> On Mon, Nov 19, 2001 at 12:59:46PM -0800, Bill Schoolcraft wrote:> Hello Family, > > My RedHat-7.2 box prints perfectly to an Epson777 color injet > printer which I gave an IP address via a mini printserver attached > to the back of the printer. > > I have a Windows2000 computer hooking into the same RedHat-7.2 box > via Samba-2.2.2 fine. > > I have not been able to get my Windows2000 box to print to the > Epson777 color injet via Samba. > > [question] > > Since Linux already "filters" the docs it prints should I send the > Windows2000 files to the Linux box in RAW mode and let Linux filter > the text ? > > If there is any "Windows2000 && Samba && Printing" success stories > (smb.conf files) or http://links to resources I'd appreciate it. > > I've tried printing straight from the Windows2000 box to the > Epson777 color injet (static ip to statice ip) but for the life of > me can't get even a chirp out of the printer. > > -- > Bill Schoolcraft > PO Box 210076 -o) > San Francisco CA 94121 /\ > "UNIX, A Way Of Life." _\_v > http://forwardslashunix.com > > > > -- > To unsubscribe from this list go to the following URL and read the > instructions: http://lists.samba.org/mailman/listinfo/samba
At Tue, 20 Nov 2001 it looks like Gerald (Jerry) Carter composed:> See the "use client driver" parameter in 2.2.2. Also, you might want > to read the Printing chapter in Samba-HOWTO-Collection.pdf >Thanks for the posting, I read the manpage and invoked the line: use client driver = yes and ran testparm and received the following. ####### [root@corten8 * RedHat-7.2 /usr/local/samba/lib]-> testparm|less Load smb config files from /etc/samba/smb.conf Processing section"[homes]" Processing section "[lp]" Processing section "[epson777]" Unknown parameter encountered: "use client driver" Ignoring unknown parameter "use client driver" Loaded services file OK. ###### My smb.conf looks like this: # Global parameters [global] workgroup = workgroup server string = Corten8 Samba Server encrypt passwords = yes log file = /var/log/samba/%m.log max log size = 0 socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 dns proxy = No hosts allow = 192.168.7. 127. printing = lprng printcap name = /etc/printcap smb passwd file = /etc/samba/smbpasswd passwd program = /usr/bin/passwd remote announce = 192.168.0.255 local master = yes preferred master = yes create mask = 0770 directory mask = 0750 fake oplocks = yes valid users = wiliweld, bill, administrator [homes] comment = Home Directories valid users = %S read only = No create mask = 0664 directory mask = 0775 browseable = yes [lp] path = /var/spool/lpd/lp guest ok = Yes printable = Yes print ok = yes valid users = wiliweld, bill, administrator postscript = yes [epson777] path = /var/spool/lpd/epson777 guest ok = Yes printable = Yes print ok = yes valid users = wiliweld, bill, administrator use client driver = yes
Are you sure that you have upgraded samba to 2.2.2 (RH 7.2 uses 2.2.1a I think), this parameter was introduced in 2.2.2. If you have, make sure that you are starting the correct binaries. Eirik Thorsnes Bill Schoolcraft wrote:>At Tue, 20 Nov 2001 it looks like Gerald (Jerry) Carter composed: > >>See the "use client driver" parameter in 2.2.2. Also, you might want >>to read the Printing chapter in Samba-HOWTO-Collection.pdf >> > >Thanks for the posting, I read the manpage and invoked the line: > >use client driver = yes > >and ran testparm and received the following. > >####### > >[root@corten8 * RedHat-7.2 /usr/local/samba/lib]-> testparm|less >Load smb config files from /etc/samba/smb.conf >Processing section"[homes]" >Processing section "[lp]" >Processing section "[epson777]" >Unknown parameter encountered: "use client driver" >Ignoring unknown parameter "use client driver" >Loaded services file OK. > >###### > >My smb.conf looks like this: > ># Global parameters [global] > workgroup = workgroup > server string = Corten8 Samba Server > encrypt passwords = yes > log file = /var/log/samba/%m.log > max log size = 0 > socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 > dns proxy = No > hosts allow = 192.168.7. 127. > printing = lprng > printcap name = /etc/printcap > smb passwd file = /etc/samba/smbpasswd > passwd program = /usr/bin/passwd > remote announce = 192.168.0.255 > local master = yes > preferred master = yes > create mask = 0770 > directory mask = 0750 > fake oplocks = yes > valid users = wiliweld, bill, administrator > >[homes] > comment = Home Directories > valid users = %S > read only = No > create mask = 0664 > directory mask = 0775 > browseable = yes > >[lp] > path = /var/spool/lpd/lp > guest ok = Yes > printable = Yes > print ok = yes > valid users = wiliweld, bill, administrator > postscript = yes > >[epson777] > path = /var/spool/lpd/epson777 > guest ok = Yes > printable = Yes > print ok = yes > valid users = wiliweld, bill, administrator > use client driver = yes > >
Maybe Matching Threads
- Fwd: SOLVED [cups] print_job: Unsupported format "application/octet-stream"
- Win2k-->Linux-->Epson777 (smb.conf + /etc/printcap included)
- (best error yet) A StartDocPrinter call was not issued.
- [win2k] Epson777 "IT WORKS !!!!!"
- SOLVED [cups] print_job: Unsupported format "application/octet-stream"