I have just the same problem on a three workstation peer
to peer Win2000 network. All 3 systems are SP4 Win2000.
Sys1 has an HP2200 that is shared and is configured on the
other systems "sys2" and "sys3", each system can print
without error to the HP2200. HP2200 connected via
parallel to "sys1". All is happy in the world - then an
HP1500L is added to "sys1" via a USB cable. Printer is
setup using the supplied CD-ROM - it works just fine
on "sys1" the host. "Sys2" is configured to use the
HP1500L, again using the HP supplied CD-ROM which is setup
to configure a variety of network print otions. This is
peer to peer so very straight forward setup and it works.
I can print to both the HP2200 and the HP1500L
from "sys2". Go to configure on "sys3" and now I get the
same error message as is posted in this original message.
However I can still print to the HP2200 and see the
HP1500L in my network places or with Windows Explorer.
Trying to install the printer with the HP CD or via the
Windows network will produce the same error message. Just
in case there was an odd network problem different
protocols were installed - no change. Sys3 was moved to
another network with a mix of workstation types - same
result - the original HP2200 still shows in the printers
folder but not one of the printers on the other network
can be configured - same error message. The printers I
wish to connect to can be seen from "sys3" on the new
network it is attached to, but they cannot be installed as
I allways get the error message "Could not connect to
printer. You either entered a printer name that was
incorrect or the specified printer is no longer
connected .."
It must be a registry problem but where? have unistalled
network drivers - installed different network adapters -
even tried a USB to Ethernet adapter - no change, still
can see the peinters, but not install them on this
computer. Hardware is AOpen MX46-533GN MB - Realtek
RTL8139(A) but others tried. Have run fixed IP and DHCP
and installed both IPX/SPX and NETBEUI protocols. Still
unable to install network printer type. We are stuck with
\\sys1\hp2200. Am now going to uninstall the only working
printer just to see if it is the HP2200/2500 driver that
is the problem. If anyone has similar experiences or any
ideas please e-mail (e-mail address removed) or reply to this
post. This is just another example of the hours of un-
billable time that is spent by service techs trying to
support their customers. One day there may be a
resolution to the thousands of hours spent trying to
troubleshoot problems created by operating systems
designed by a company more interested in marketing image
than reliability, or in providing the front line people
with real tools and information to troubleshoot problems.
O.K. it may be an HP problem not MS this time, but! After
37 years in the industry I have seen more than a few odd
problems.
T.Q. R.D.
