Tom's Guide | Tom's Hardware | Tom's Games
![]() |
![]() |
![]() |
I am in real need of help. I have tried many sources to get to the bottom of this issue but no one else has had this problem (that I can find).
About a month ago they started to have application hangs when printing (any application, not one specific). First I thought it was specific to one client on a network (all clients are XP Pro, patched and updated), so we rebuilt that system.
The problem came back, then it moved to other systems. So I though it was specific to one printer (Samsung ML-4600), so I reinstalled the driver and it appeared to solve the problem. Then the problem came back on a different printer (HP 5si).
These printers are connected via clients on the LAN which are acting as their printer servers. I noticed that the server might have been acting as a secondary print server to these printers, so I turned off the Print Spooler on the server and it appeared to solve the problem. Then the problem came back, now it appears to have stayed with one printer (the 5si) and is not going away. Around the same time this started, I had noticed that this printer had a NIC card and I attached it to the network, but hadn't set it up on the server as a resource yet. I have since disconnected its NIC hoping that might solve the problem, no luck.
I have done more changes to no avail. I have replaced the switch, updated the firmware on the D-Link DL-514 router. Blown and reseated all Cat5 cables. Checked and updated the Security on the printer. Found out that I get about 2-3 days of working with the printer and then the users system hangs. It appears random with no specific situation that causes the Application Hang. It can hang Word, AutoCAD, Explorer, etc.
The systems are all using the most recent version of the spooler 5.1.2600.2696 and when you stop and start the spooler service you get another 2-3 days of functionality. When stopping the spooler services, as you can imagine, it freezes says it can't stop the service/the service did not respond but it does shut it down. We are stuck. It is difficult to troubleshoot because of the time period it takes to replicate the issue 2-3 days. We can try solutions which work for a while then break down again. Any advise would be greatly appreciated.

The description you give is so complicated
that no one responds
try to break the problem in steps
Maybe the users are the problem ?
Maybe there is too little space on the HD
somewhere ?
Netdiag ?

![]() |
![]() |
![]() |

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |