XP client slow response from shared printer on W98 host

My Canon ip4000 is a shared USB printer on my Windows 98 desktop computer.
The share name is "CANON" and the computer identification is "MSI".

I want to use it from my Windows XP notebook computer over my
crossover-cable network. Alas, the response time is poor - about 1.5 minutes
to open the printer properties window.

Worse yet, it takes about 3-5 minutes to open a MS Word document on the
Windows XP computer. Apparently, before opening the document, Word checks
the printer properties in order to configure the page setup menu.

>From the Windows 98 host, the printer test page show port name "MPUSBPRN01"
and a list of Windows 98 drivers.

>From the Windows XP client, the printer test page shows port name
\\MSI\CANON and a list of Windows XP drivers. In printer properties, the
port description is "LAN Manager Printer Port".

If I disconnect the network cable, the MS Word document opens almost
immediately.

I tried a different installation approach, to no avail: I connected the
Windows XP computer directly to the printer through a USB port. Thus, I
added another printer. Next, I attempted to change the port of printer
number 2, from USB to \\MSI\CANON. This change was refused.

Am I plumb out of luck? I had no problems using a Windows 98 notebook to
access the host printer.

Suggestions?

JohnF



.

Relevant Pages

  • RE: redhat-list Digest, Vol 4, Issue 38
    ... Re: Iptables: port 22 open only for my IP ... Windows Services for Unix 3.5 ... It does absolutely nothing if you have a rampant application on your Windows box that opens a port to the outside world. ...
    (RedHat)
  • Re: USB device detection via query registry information
    ... specific parts of a driver. ... it correctly enforces exclusivity to the port ... for Windows being crash-prone? ... serenum opens the port, detects the device, ...
    (microsoft.public.development.device.drivers)
  • Re: USB device detection via query registry information
    ... it correctly enforces exclusivity to the port ... WHQL is realistically not going to be able to catch all bugs before shipment, so maybe the answer is for WHQL signing to require a commitment from the driver developer to participate in the BSOD crash dump program and issue timely bug fixes. ... Yes these things would not come free, but is it important to Microsoft to shed the reputation for Windows being crash-prone? ... serenum opens the port, detects the device, ...
    (microsoft.public.development.device.drivers)
  • Re: keeping ports open
    ... If a port is open, it means that 1) a software or service is running on your ... and 2) you're not using a firewall or your firewall isn't ... Use firewall software and hardware and antivirus software that is ... Follow the instructions for hardening Windows and IIS at ...
    (microsoft.public.security)
  • [Full-Disclosure] ron1n phone home, episode 4
    ... Hacking from Windows 3.x, 95 and NT ... Use secret Windows 95 DOS commands to track down and port surf computers ... Download hacker tools such as port scanners and password crackers designed ... Now you have the option of eight TCP/IP utilities to play with: telnet, ...
    (Full-Disclosure)
Loading