Hi,

I have a HP 1205 psc printer/scanner/copier connected to an XP box. My linux laptop (Suse 9.1)b connects to the XP box and is able to network, share and connect to the internet.

I have set up the printer on the linux laptop using Yast and the printer is visible to the Linux laptop. I have selected the HP PSC 1205 Foomatic/hpijs driver as shipped with 9.1 and everything seems to install ok until I try a test print. (or print anything else for that matter).

1. The print job is sent to the XP box which receives it and places it in the print queue (which is at the top - no queue!!).

2. The green LED on the printer starts to flash indicating that it is preparing to print.

3. The print heads start to move (presumably self calibrating)

4. The green LED on the printer continues to flash.

5. But, no printing.

6. After about 30 seconds the print head 'parks' itself.

7. The XP status shows 'Printing', Size is stuck at 64.0KB/1.28MB - seems like the printer is waiting for more data ...

8. The linux laptop does not report any errors during transmission and assumes job is complete.

Only thing to do is cancel job on XP box and reset printer by switching off and on.

Any ideas?

Thanks

Edit /etc/cups/cupsd.conf and change loglevel to debug. Try printing again then look at /var/log/cups/error_log and see if it has any clues as to why it failed. (If those paths are wrong I apologise, I'm not familiar with SuSE)

This is the error log :

[03/Jul/2004:00:52:16 +0100] Adding start banner page "none" to job 1.
[03/Jul/2004:00:52:16 +0100] Adding end banner page "none" to job 1.
[03/Jul/2004:00:52:16 +0100] Job 1 queued on 'Printer' by 'Guest'.
[03/Jul/2004:00:52:16 +0100] Started filter /usr/lib/cups/filter/pstops (PID 3573) for job 1.
[03/Jul/2004:00:52:16 +0100] Started filter /usr/lib/cups/filter/foomatic-rip (PID 3574) for job 1.
[03/Jul/2004:00:52:16 +0100] Started backend /usr/lib/cups/backend/smb (PID 3575) for job 1.

Doesn't appear to be any error - although I can't see anything that says it has completed or ended ... backend maybe?

I think it must either be a config error or a problem with the driver since I can get it to work ok when the laptop is booted into XP.

Have noticed that when printing from XP that the status shows on the machine with the printier connected 'spooling', whereas this is not the case with linux - just goes straight to printing.

Anybody know of any spool settings ...

I tried for days to get this to work once and couldn't...
also worked with others with the same trouble
and no one could get it going....
so you are not alone.

OK, I'll try for a bit longer, if I get it going I'll post the solution ......

I am experiencing exactly the same problem. I am using the latest hpijs printer drivers (1.6.1) on Fedora Core 2 (with the latest rpms via yum). I am able to configure a SMB printer and the print job is sent to an XP based shared printer. The HP PSC 1210 does a few gyrations and then hangs. It seems to me that the hpijs print driver or the Samba software (or some combination thereof) is not sending the appropriate bits and bytes to the shared printer. The printer is shared fine by other Windows machines on my network. The question is whether it is a configuration issue (something I can fix) or a bug with the drivers or Samba system (something I cannot fix). I am not aware of any configurations I can change. I have not tried connecting the printer directly to the Fedora box; my assumption is that it would work based on feedback from forums.

- Nick

I tend to agree with you - I feel sure that it would pobably work if connected directly to the Linux machine, but maybe a problem with the driver when connected via XP.

I still haven't managed to find a fix yet. If I get time I'll try and connect direct to Linux and see if it works.

I have finally managed to sort this out (trying since June on and off) - so if any one else is having a problem getting a printer to work over a network on an XP box this is what was stopping mine from working ...

On the XP box goto Printer > Properties > Port then [B]uncheck[\B] 'Enable bi-directional Support'.

Now it all works ...

1 members found this post helpful.