P
Patrick
Hi. We recently installed the SP4 patch to all of the
Win2k machines in my department including our office
file/print server. After doing this, we began noticing
some hang time in graphics and communications with our
networked HP LaserJet 4100n. However, this seems to a
major problem mainly on two of our Dell Optiplexes. None
of our other PCs (non-Optiplexes) in the department seem
to be experiencing this problem (knock on wood). Whenver
you try to print anything from any application using the
4100n, it takes a few (est. 5 mins. +/-) to just get to
the print selection/settings/etc. window. Then it takes
forever from the time you press OK/Send and the actual
printing. In around 1/3 to 1/2 of the instances, it's
causing the two PCs to freeze up, forcing us to reboot
them. We tried uninstalling/reinstalling the 4100n
drivers and changing the spool settings, but to no avail.
Plus, the probs only seem to occur when trying to print to
the 4100 or when the 4100 is set as the default.
Has anyone else encountered this or similar problems? If
so, how did you fix it?
Thanks,
Pat
Win2k machines in my department including our office
file/print server. After doing this, we began noticing
some hang time in graphics and communications with our
networked HP LaserJet 4100n. However, this seems to a
major problem mainly on two of our Dell Optiplexes. None
of our other PCs (non-Optiplexes) in the department seem
to be experiencing this problem (knock on wood). Whenver
you try to print anything from any application using the
4100n, it takes a few (est. 5 mins. +/-) to just get to
the print selection/settings/etc. window. Then it takes
forever from the time you press OK/Send and the actual
printing. In around 1/3 to 1/2 of the instances, it's
causing the two PCs to freeze up, forcing us to reboot
them. We tried uninstalling/reinstalling the 4100n
drivers and changing the spool settings, but to no avail.
Plus, the probs only seem to occur when trying to print to
the 4100 or when the 4100 is set as the default.
Has anyone else encountered this or similar problems? If
so, how did you fix it?
Thanks,
Pat