Xerox Network Printer-Work Stations to Not Responding When Printing

[Coastalbendcomputers]

This is going to be long but hopefully detailed. I just cannot figure this out, everything was working fine for 2+ years then it just started causing the error. Every Workstation on the network goes not responding for 10-20 seconds after hitting print then it starts to respond again and the print comes out of the xerox.

First the network
Workstations (4 Wired, 2 Wireless all Win7 x64) > Patch Panel > Unmanaged Switch
Xerox > Patch Panel > Switch
Server (AD, DNS, no DHCP) > Unmanaged Switch
Router (DHCP) > Unmanaged Switch

Originally all workstations had there own driver installed. I removed all of them and setup the print server. Same problem.

Swapped out the router with a known good. - Same Issue

Buypassed the patch panel and went directly through the router. - Same Issue so it was Workstation > Router | Server > Router | Printer > Router

I messed around with bidirectional settings and changed from Raw to LPR this has helped me with driver issues in the past and removed SNMP Status per Xerox Article.

Print directly from my Laptop to the Xerox hardwired - Worked with no problem!

Print directly from the server to the Xerox Worked!
Setup was Server > Switch > Router | Printer > Switch > Router

After this the Customer got a new Xerox going from Workcenter 7545 to a 7845 with this change they has had different drivers. - Same issues, Same things worked.

I feel like it was a permissions issue but I have created an admin user for the xerox and gave it full permissions on both the printer side and to the scan to network directory just in case. I have also made sure the Everyone user had full privileges to print and manage the printer. I checked and all are able to set there own printer properties from there workstations. I even tested adding one of the AD admin Users directly to the printer and gave him all privileges to see if it would change anything and it didn't.

1 other note they also have a Brother Wireless Network Printer. Installed and shared through the server. It prints jobs quickly with no issues. So this makes me think the server is fine. Also nothing changed on the server between when it was working and when it stopped.

I have disabled TCP Chimney Offload, RSS, and Receive window auto-tuning level. As well as removing the antivirus temporarily.

1 last note I was just testing and downloaded a random HP network printer PCL 6 driver and installed it for the xerox and it worked!! Quickly with no problems just missing a lot of features which makes since since it's not the xerox driver. The odd thing here is this Xerox driver is not new it's been around we didn't update them to start the issue. As you can see I have tried a lot and I'm left head in hands, please help me.

 

[YeOldeStonecat]

I setup a WorkCentre just two weeks ago.....old WorkCentre...on a new server and Win7 workstations. I went straight for their universal driver...I forget the name Xerox users...wasn't the PCL5 or 6....but similar to HPs Unidrivers, or Canons UFRII. Did you try that instead of the 5 or 6?

 

[Martyn]

Could be a printer spooler issue on the server I'm thinking. Load a driver locally on a pc and point it to the share on the print server and see if that works. If the server is running out of space the print spool file may have trouble. Some of the drivers create massive files.

 

[Coastalbendcomputers]

I'm having a hard time finding a global xerox print driver but I'm willing to try anything at this point.

Martyn I'm not sure exactly how to do that I understand the local driver where would I point it I'm not sure what the Share is. I will do some research on my side as well.

 

[Martyn]

I'm having a hard time finding a global xerox print driver but I'm willing to try anything at this point.

Martyn I'm not sure exactly how to do that I understand the local driver where would I point it I'm not sure what the Share is. I will do some research on my side as well.

Share the printer on the server so the path becomes \\server\share. On the local installed driver install the full driver and point it to that path. It will just pass through the driver but process locally on the client. Just to see what does or doesn't happen. I'm out of the corporate world for a good few years though but I did deal with a lot of printer(not Xerox) issues.

 

[Coastalbendcomputers]

I setup a WorkCentre just two weeks ago.....old WorkCentre...on a new server and Win7 workstations. I went straight for their universal driver...I forget the name Xerox users...wasn't the PCL5 or 6....but similar to HPs Unidrivers, or Canons UFRII. Did you try that instead of the 5 or 6?

I think this is the driver you are talking about.
http://www.support.xerox.com/suppor...r/downloads/enus.html?operatingSystem=win7x64

 

[Coastalbendcomputers]

Share the printer on the server so the path becomes \\server\share. On the local installed driver install the full driver and point it to that path. It will just pass through the driver but process locally on the client. Just to see what does or doesn't happen. I'm out of the corporate world for a good few years though but I did deal with a lot of printer(not Xerox) issues.

I know that you know what you're talking about when I posted this I was hoping you or YeOldeStonecat would chime in as I value both of your opinions and I got both! what a day. I'm trying both of your suggestions now and appreciate you taking the time to help me out.

 

[Coastalbendcomputers]

Ok, I installed the Global Print Driver as postscript (recommend) didn't include plc5 or plc6 and I'm having the same issue. Prints instantly from the server via RDP but causes a delay and not responding from workstation.

 

[Coastalbendcomputers]

Share the printer on the server so the path becomes \\server\share. On the local installed driver install the full driver and point it to that path. It will just pass through the driver but process locally on the client. Just to see what does or doesn't happen. I'm out of the corporate world for a good few years though but I did deal with a lot of printer(not Xerox) issues.

I'm not figuring this one out I installed the driver locally but don't see where to point it to a different path. I didn't see any option for doing this during the driver install either. I tried google for the answer but this is just not getting through my head.

 

[nlinecomputers]

Have you cleaned out the spool directories on each workstation? You need to stop the printer service and the delete everything in the printer spool.

http://www.techienewsnetwork.com/fixing-or-cleaning-the-problematic-windows-print-spooler/

 

[Martyn]

Yes create a share on the printer on the server. On the client computer install the full driver and point it to the share. Add a port - local port then \\servername\share name. Yes clear the spooler etc and just check that is ok. I remember from years back you can move the spool directory and have a separate one for the printer in question. That way if you crash the spooler then all printers don't stop working.

 

[YeOldeStonecat]

Global, or WHQL....I often shoot for the WHQL if I can. But I think the "global" one was what I was trying to remember. Apologize for not being prompt in replies on this thread...today I did a ferry boat ride out to an island in the Atlantic that has a golf resort...and I'm crunched for time with 2 hours remaining til the ferry leave to go back to mainland...always a mad rush to finish things up when coming out here. BRRR...cold and windy today too..surprise snow last night. And it's spring...I was just working shirtless in the yard this weekend sweating away.

 

[Coastalbendcomputers]

Have you cleaned out the spool directories on each workstation? You need to stop the printer service and the delete everything in the printer spool.

http://www.techienewsnetwork.com/fixing-or-cleaning-the-problematic-windows-print-spooler/

Yea they are all clear also it doesn't pause when using the other network printer, or there dymo / graphic products label printer. It only hangs on the Xerox. Weirdest thing ever, I hate to leave telling them I don't know whats causing it but thats the truth. I told them I would do some research and get back to them.

 

[Markverhyden]

It's not entirely clear but it appears, based on your descriptions, that you have the server managing the print Q. Have you tried installing the driver on a workstation and pointing it directly to the Xerox?

 

[Coastalbendcomputers]

It's not entirely clear but it appears, based on your descriptions, that you have the server managing the print Q. Have you tried installing the driver on a workstation and pointing it directly to the Xerox?

Yes Originally when the problem started all the workstations where setup this way. I switch it all over to the server to see if that would help. It's a weird issue because all of the workstations 4-6 depending on the mobile employees started having the same issue on the same day but all the workstations had their own individual drivers at the time. That is why I spend so much time troubleshooting the network because that was all they had in common except for server (DNS / AD).

 

[Coastalbendcomputers]

Yes create a share on the printer on the server. On the client computer install the full driver and point it to the share. Add a port - local port then \\servername\share name. Yes clear the spooler etc and just check that is ok. I remember from years back you can move the spool directory and have a separate one for the printer in question. That way if you crash the spooler then all printers don't stop working.

Thanks for being patient with me I did get it reinstalled with a local port point to the shared printer on the server but the same issue is happening.

 

[Martyn]

If you only have 4-6 users I would just set each client direct to the printer at least for the time being until you resolve the issue. Have you uninstalled the print driver on the server and set it up again? If you really want to break down the issue you can pause the printer on the server print your file and grab the .spl file out of the spool directory. You used to be able to view the file in notepad and look for the header. This was on pcl and ps files. You could then take that file and LPR it from from another computer direct to the printer. To be honest for that few users I would just go local direct to the printer and save the bother if all other printers are ok. Certainly worth uninstalling the printer totally including the ports on the server and reinstall them. Are you sure the port is set up correctly? I've seen some strange problem caused by incorrect settings on the print server driver.

 

[Coastalbendcomputers]

If you only have 4-6 users I would just set each client direct to the printer at least for the time being until you resolve the issue. Have you uninstalled the print driver on the server and set it up again? If you really want to break down the issue you can pause the printer on the server print your file and grab the .spl file out of the spool directory. You used to be able to view the file in notepad and look for the header. This was on pcl and ps files. You could then take that file and LPR it from from another computer direct to the printer. To be honest for that few users I would just go local direct to the printer and save the bother if all other printers are ok. Certainly worth uninstalling the printer totally including the ports on the server and reinstall them. Are you sure the port is set up correctly? I've seen some strange problem caused by incorrect settings on the print server driver.

If you mean install the printer from each workstation directly via IP address. I have tried that and the issue is still there. I have installed it as a local printer using tcp/ip on 1 of the work stations and it still causes it to go not responding.

 

[Martyn]

If you mean install the printer from each workstation directly via IP address. I have tried that and the issue is still there. I have installed it as a local printer using tcp/ip on 1 of the work stations and it still causes it to go not responding.

Wait a minute. If you setup the printer direct via tcp/ip and you have the problem then the server is out of the equation. I must have missed that. Are you sure it's not something silly like a duplicate ip address?

 

[Markverhyden]

Yes Originally when the problem started all the workstations where setup this way. I switch it all over to the server to see if that would help. It's a weird issue because all of the workstations 4-6 depending on the mobile employees started having the same issue on the same day but all the workstations had their own individual drivers at the time. That is why I spend so much time troubleshooting the network because that was all they had in common except for server (DNS / AD).

Ok, so the same either way. Did you clear out the print Q folders according to the link nlinecomputers posted. You cannot just make sure the print Q folders are empty. You must stop the service and then delete those spooler folders. The folder have some special properties so deleting them and re-creating them does make a difference.