Well, The final outcome goes something like this.
The items in Diagnose where no help, even the command line changes for the print commabd never seemed to work. The issue was an item in the smb.conf file that didn't appear in any examples that I found with the exception of one that I found on Google, there needs to be both a "writeable" and " printable" = Yes for each printer and writable is needed for all disk shares. SWAT was little to no help in this regard. It all working except Win2K and XP refuse to show the printers as available evnthough they are and can be prited to by the offending machines. Must be more MS FUD. Thanks for the info and suggestions guys. They were appreciated.... stayler On Sat, 29 Jun 2002 23:30:19 -0400, Joel Hammer wrote: >Like Billy Joel says, >Advice is cheap because opinions are free. >Here are some opinions. > >Have you walked through DIAGNOSIS.txt in the docs/textdocs directory? >TEST #8 reports some of these same types of errors. >There are odd errors that "use client driver = yes" seems to help. >Have these printers ever worked right with this server and clients? >Do the other shares really work, or only seem to work? Can you save and read >from them? >Can you set up a phony print queue on your linux server which just dumps >the print jobs to a file? Something like this: _______________________________________________ Linux-users mailing list - http://linux-sxs.org/mailman/listinfo/linux-users Subscribe/Unsubscribe info, Archives,and Digests are located at the above URL.
