Log in

View Full Version : XP/Vista printing nightmare


Jonstar
Mar 18, 2008, 08:36 AM
Here's one for you... according to some techs, my problem seems to be the reverse of most problems and they can't figure it out.

Here's the basics... I have a network running through a Linksys Router. 3 computers. 2 run XP and 1 runs Vista.

The one XP system has an old HP LaserJet 4 Plus hooked to it through the Parallel port.
The Vista system has a HP PSC 2100 hooked to it through USB.
The other XP system doesn't have any printer on it.

All computers communicate and see each other and all can share the printers.

My problem is that when I print to the LaserJet (hooked to the XP system) from either XP system, the printer spits out a blank page. No text.
And here's the kicker...the Vista system will print to the LaserJet without any problems! And it's not directly hooked up to it!

I've tried isolating the XP system with the LaserJet by taking it off the network and shutting off printer sharing. I've even deleted the printer and re-installed the drivers but I still get a blank page.

Oh, and all 3 computers print to the PSC2100 no problem. So far I've puzzled 2 techs on this one. The printer worked perfectly until I introduced a Vista system to the network. Then this problem started!

I've attached a diagram of the network...

Any ideas?

donf
Mar 21, 2008, 10:35 AM
My first suggestion is to place the failing printer in Hex Trace Mode and then send a job to the printer and lets see what the raw data going to the printer is. If you do not know how to read the data on the page, fax it to me at (757) 491-5023 and I'll read it for free for you.

If you can't get the printer into a trace mode, set the driver to "Print to File" and we can catch the data that way. Send the file to me at [email protected] and I'll read through it and see if I can find a busted printer code.

Jonstar
Mar 21, 2008, 04:30 PM
I appreciate your help on this Don, but it was a work computer and after talking to other techs that were baffled we ended up getting new printer (we needed one anyway) and that has fixed the problem.

I would really like to have known what was causing the issue and I feel that we've taken the easy way out by doing this but we needed it working for the business.

Thanks again for your thoughts...

donf
Mar 21, 2008, 04:39 PM
Not to worry.