There is a menu on the lexmarkz53 windows software which disables two way communication.
If you use the lexmarkz53 windows client software, you need to send your jobs to a raw queue on the server. Joel On Fri, Jul 25, 2003 at 08:49:08AM -0700, Jim C wrote: > OK, some progress. I managed to get access to the printer but now I > have the bi-directional communications problem. > Using Lexmark Z52 drivers did not help. From the communications I've > been googleing, several have had this problem and my guess is that at > least one person has solved it. Note that for right now I don't really > care much about bi-directional communication. I just want to get it > working. > > Jim C. > > Joel Hammer wrote: > > >Is is established yet if your setup is using the lexmark supplied software > >or cups drivers? It may not really matter. If the printer is working > >fine locally, then it seems to be a problem with samba. What you have to > >do is figure out which queue is accepting jobs on your server, locally, > >then set up your samba share to direct jobs to that queue. > > > >You might look at /var/spool/lpd. The print queues usually hang out there. > >Look for a print queue which is controlling your printer, and use that > >in your samba share. > > > >Your system seems to be generating its printcap file dynamically. This > >sounds like something with which I contended when I used RH at one > >time. This is one of the many advances in linux which just makes it > >harder to fix problems. I didn't get any results with network printing > >until I disabled that automatic generation of the printcap. There is > >some sort of printing frontend which does this. I would get rid of it and > >set up a regular printcap file, or else try to edit the configuration file > >this printing frontend is using. > > > >Joel > > > > > > > > > > > > > -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
