OK, that eliminates one possibility; it seems like the problem may lie somewhere in the config setup between XP, Samba and CUPS. I didn't look real hard and you may have already seen this, but here's one possibility:
http://www.debian-administration.org/article/Sharing_a_printer_to_Windows_XP_clients_with_Samba_and_Cups <http://www.debian-administration.org/article/Sharing_a_printer_to_Windows_XP_clients_with_Samba_and_Cups> On Wed, Feb 23, 2011 at 9:03 PM, Kevin Broderick <[email protected]>wrote: > There is no evidence of the test pages making it into the print queue—they > don't show up in the queue from the clients, nor do they show up in the cups > job list. > > (and printing works fine from all clients I've tried *except for* Windows > XP...which, of course, is the OS on the majority of our company-owned > machines). > > On 23 Feb 2011, at 8:52 PM, David Hardy wrote: > > > *Are the attempted test pages showing up in the printer queues at all and > > stalled there?* > > > > > > > > On Wed, Feb 23, 2011 at 8:34 PM, Kevin Broderick <[email protected] > >wrote: > > > >> So I've got an almost-working Samba/CUPS printing setup, and I'm > wondering > >> if anyone else has run into the same issue. Point-and-Print works fine > >> under Windows 7, and I think WIndows Vista. Point-and-print *almost* > works > >> under Windows XP; the clients will download the drivers (with a warning > >> about software installation if not domain members, without any dialog > boxes > >> for domain members). > >> > >> Hoewver, printing doesn't work. If I try to print a test page from XP > to > >> one printer, I get "Test page failed to print. Would you like to view > the > >> print troubleshooter for assistance?" with no errors in the system or > >> application logs on the client, and no obvious errors in the server logs > >> (nothing useful shows up at log level 1, and log level 3 provides a lot > of > >> detail with nothing obviously wrong). > >> > >> To the other printer from domain machines, I get "Test page failed to > >> print. Would you like to view the print troubleshooter for assistance? > >> Operation could not be completed." Again, nothing apparent in the > system > >> or application logs on the client or anything on the server. > >> > >> Both printers give "Test page failed to print..." without the "Operation > >> could not be completed" on the non-domain XP client (running as an admin > >> user, which may be the difference). > >> > >> Any thoughts? I've been googling for hours and have yet to find this > >> scenario, or any way to get useful error messages, let alone fix the > >> problem. > >> > >> (Printing works fine from Windows 7 clients and from OS X via the same > SMB > >> connection with the same username, so the queue seems to work fine.) > >> > >> > >> Kevin Broderick > >> [email protected] > > Kevin Broderick > [email protected] >
