Page 2 of 2
Posted: Wed 16 Jul 2008, 22:31
by rcrsn51
It now looks like the print job made it from Puppy to Windows. Since the printer won't complete the job, my first instinct would be that the driver is wrong. But I believe that you tested it as a local printer and it worked. I'm stumped again.
By the way - did using "guest" actually make a difference?
Posted: Wed 16 Jul 2008, 22:50
by rcrsn51
Have you rebooted the printer recently?
Posted: Thu 17 Jul 2008, 06:48
by exProphecy
Well, every time I use smbclient -NL PC_NAME it gives the error:
Connection to PC_NAME failed (Error NT_STATUS_BAD_NETWORK_NAME)
But when I open up Pnethood, and leave it open, I am able to use smbclient -NL PC_NAME and it works. So I suppose opening up Pnethood helped it somehow? Yes I've rebooted the printer multiple times and the Windows host as well.
Posted: Thu 17 Jul 2008, 11:50
by rcrsn51
PC_NAME should be the actual name of the particular Windows machine to which you are connecting.
Posted: Thu 17 Jul 2008, 19:28
by exProphecy
rcrsn51 wrote:PC_NAME should be the actual name of the particular Windows machine to which you are connecting.
Yes of course I know hahaha! The PC_NAME is SINISTER. I'm not that noobish. =P
Posted: Mon 21 Jul 2008, 07:24
by exProphecy
So you guys think it's a driver problem because I installed the hpijs-2.8.2.pet from the PETget package manager, and the driver I'm using is the HP PSC 1310 driver. It said it should work for 1315xi.