G
Guest
This is a home network using a peer to peer workgroup. The printer is a HP
psc 2110 All-in-one, connected to a computer running Windows 98. The client
computer is running W2K Professional. The printer was shared and available
to the W2K machine for quite some time.
The W98 machine was moved to another room; different Cat5 cable connections
involved, but no other changes. All shared drives, etc work as they always
did. However, the W2K Pro machine can no longer print to the HP 2110.
The printer appeared as a shared printer still available on the W2K machine,
but attempts to print generated errors. The shared printer was then deleted
and an attempt made to add it again. The "Add Printer" wizard easily browses
to the printer on the workgroup network, but when it is selected, the
following error message pops up:
"Error: The data area passed to a system call is too small"
The other W98 machines on the workgroup (2) have no problems using this
shared printer. Only the W2K machine has the problem; no changes have been
made to this machine since the last Microsoft updates about a week before
this started.
Ideas?
psc 2110 All-in-one, connected to a computer running Windows 98. The client
computer is running W2K Professional. The printer was shared and available
to the W2K machine for quite some time.
The W98 machine was moved to another room; different Cat5 cable connections
involved, but no other changes. All shared drives, etc work as they always
did. However, the W2K Pro machine can no longer print to the HP 2110.
The printer appeared as a shared printer still available on the W2K machine,
but attempts to print generated errors. The shared printer was then deleted
and an attempt made to add it again. The "Add Printer" wizard easily browses
to the printer on the workgroup network, but when it is selected, the
following error message pops up:
"Error: The data area passed to a system call is too small"
The other W98 machines on the workgroup (2) have no problems using this
shared printer. Only the W2K machine has the problem; no changes have been
made to this machine since the last Microsoft updates about a week before
this started.
Ideas?