The problem here is the combination of crossing both versions and
"bit-ness". Over time, I've found the best solution is to use platform
independent print servers that sit directly on the network and allow
individual workstations to connect to the printer directly. There are models
from HP (JetDirect), or D-Link, or Linksys or a dozen other vendors, and
they can include USB or parallel port output (or both), and can have regular
wired Ethernet or Wireless connectivity. I usually just choose printers that
have this capability built in, but I also have a simple wireless print
server from D-Link that I use (
http://www.dlink.com/products/?pid=482).
--
Charlie.
http://msmvps.com/blogs/russel
"skeeter" <> wrote in message
news:...
>
> "Marcin Balcerzak" <> wrote in message
> news:...
>> On Sun, 22 Nov 2009 21:40:57 -0800, Charlie Russel - MVP wrote:
>>
>>> How is the printer physically connected to the network? Is it attached
>>> to a
>>> machine via USB or Parallel port? Or does it have an Ethernet port? If
>>> Ethernet, then you need to create a port for the printer to attach to.
>>
>> It's connected via parallel port (LPT1) to the computer with Windows
>> 2000.
>>
>>
>> --
>> Marcin Balcerzak
>
> i hate to just add "me too" but i have the same issue with HP 3050. same
> OS, win 7 64 bit with printer on 1 desktop xp sp3 32 bit. laptop found the
> 64 bit driver but the desktop with 7 didn't. i pointed it to the hp
> universal drivers and still no luck.