If there are any Windows XP drivers that are compatible with one or both of
the devices I would setup a test printer and verify this is a vendor
driver/print processor/language monitor issue.
Next I would remove all 3rd party print monitor software. There are a
couple KBs on this. I don't necessarily think this is an issue with HP
Standard TCP/IP port but I'd create Standard TCP/IP Ports and delete the HP
ones (you can add them back later if you wish but I would definitely remove
any ports targeting the same device when both port monitors are installed).
http://support.microsoft.com/kb/314073/en-us
How to troubleshoot network printing problems in Windows XP
http://support.microsoft.com/kb/810894/en-us
Error message: Spooler subsystem app has encountered a problem and needs to
close
If this does not help, then it's time to debug the spooler and determine
what function is using all the CPU cycles.
--
Alan Morris
Windows Printing Team
Search the Microsoft Knowledge Base here:
http://support.microsoft.com/default.aspx?scid=fh;[ln];kbhowto
This posting is provided "AS IS" with no warranties, and confers no rights.
"MR80" <MR80.RemoveThis@discussions.microsoft.com> wrote in message
news:C9FE01EB-AE59-4531-BB1D-D3AFF9284152@microsoft.com...
>I am using HP standard tcp/ip port. And you are also correct about the cpu
> utilization. It gets to 100% when spooler is hanging. I have tried to
> uninstall/reinstall the printer drivers, doesnt help. I have only used
> drivers from hp so far.
>
> The eventlog error is from serverB.
>
>
> "Alan Morris [MSFT]" wrote:
>
>> Are you using HP Standard TCP/IP Port or the TCP/IP port shipped in
>> Windows?
>>
>> It sounds like max CPU utilization by the spooler service on ServerB.
>>
>> Have you uninstalled / reinstalled the printers and drivers already?
>>
>> The eventlog error is from ServerB, correct?
>>
>> --
>> Alan Morris
>> Windows Printing Team
>> Search the Microsoft Knowledge Base here:
>> http://support.microsoft.com/default.aspx?scid=fh;[ln];kbhowto
>>
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>> "MR80" <MR80.RemoveThis@discussions.microsoft.com> wrote in message
>> news:994C26B7-CE5E-4183-8B50-B7D1BD56DB4D@microsoft.com...
>> > Hello,
>> >
>> > Before i describe my problem, here is my setup:
>> >
>> > printerA = HP laserjet 1022n (builtin print server)
>> > PrinterB = HP laserjet 3330 (builtin print server)
>> > ServerA = Windows 2003 Server (domain controller)
>> > ServerB = Windows xp pro sp2 (member of domain ABC)
>> > ClientA = Windows xp pro sp2 (member of domain ABC)
>> > UserA = Domain user. Each time userA logs onto clientA, a script is run
>> > that
>> > maps the shared printers on serverB.
>> >
>> > I have a problem with two printers, prinerA and PrinterB. Both printers
>> > are
>> > installed through network on serverB. Both printers have an ip adress
>> > each.
>> >
>> > I can print without any problems from the serverB through both printers
>> > as
>> > long as they are not shared. I can also print out without any problem
>> > when
>> > the printers are shared BUT when no domain users are logged on.
>> >
>> > When a userA logs onto ClientA, both printers are mapped correct. I can
>> > see
>> > them in the "printers and faxes". However when you try to print
>> > something
>> > or
>> > try to access the printer properties, nothing happens on the clientA.
>> > At
>> > the
>> > same time the service "print spooler" on the serverB hangs. This leads
>> > to
>> > explorer hanging on serverB also. The only thing i can do is to manage
>> > the
>> > serverB through serverA(active directory) and stop the spooler service.
>> > After
>> > this serverB gets normal again.
>> >
>> > I have tried to disable the script and map the shared printers
>> > manually.
>> > The
>> > same thing happens. The error in the event viewer is as following:
>> >
>> > "Timeout (30000 milliseconds) waiting for a transaction response from
>> > the
>> > spooler service"
>> >
>> > I hope somebody can help on this one, as this is very important to me.
>>
>>
>> >> Stay informed about: Print spooler hangs when trying to print from a shared print