If the issue happens again I'd prob remove the print server from the domain and re-add with local admin account. Also, see if you have any permission levels you can set on the server for the printer s specifically if it happens after re-joining the domain. Could be a DNS issue. Experienced the following operational errors trying to retrieve replication info rmation:.
Fixed the DNS Replication issues between both DC, but still taking seconds to print a test page from work stations. There are 5 network printers, 2 Sharp and 3 HP's they are all taking 30 seconds from each workstation, and directly from the print server itself is taking around 30 seconds as well.
Update : I added the printer as a local TCPIP instead of going through the print server, and all prints spools right up. I also used a timer app, and 3 different workstations gives the exact same time This allows all print job to spool instantly.
But, not sure why this is the case, if it worked fine before? Brand Representative for Sharp Electronics. If neither of these steps work for you, let us know specifically what version of MS Server you are running along with the client OS. There may be some stuff we are missing. I've tried Derek's tip, but it looks like it only works if the printer was currently already spooling something.
Otherwise, it still takes 30 seconds. I am going to remove print server this weekend, and clear out all the installed drivers as well and try to re-add everything, to see if that works.
Ive tried removing the print server role, and reinstalling the role as well as drivers, but still no luck. I installed the print server role on another DC and it has no issues. DLL, error code 0xc1. See the event user data for context information. To continue this discussion, please ask a new question. Get answers from your peers along with millions of IT pros who visit Spiceworks. Hi All, We just moved offices. Edited Mar 29, at UTC. Would it be possible for you take make this the default setting when installing the printer on Windows Server R2?
Can you test this on your win R2 server? Get PDF Suite, the expert. Re: Slow performance on Windows Server R2 Post by Rich » Mon Mar 26 The reason for the different behaviour using spooling or direct printing is this: The features that are added to the output PDF document after conversion, must be added in a step called post processing. This is the case of direct printing setting. If the printer is set to spooling, there is no further control over the printing document.
Details required :. Cancel Submit. Reza Ameri Volunteer Moderator. Is it a printer connected through network or USB? Is it a shared printer? The best way to start investigate the issue is through Event Viewer. How satisfied are you with this reply? Thanks for your feedback, it helps us improve the site.
In reply to Reza Ameri's post on April 26, Both Windows and Mac connect thru network and are shared. It makes no sense that two Windows computers should have the same problem.
Thagstrom Independent Advisor. I am a Microsoft Independent Advisor, I would love to help you out! Windows is built quite differently from Apples OS.
There are ups and downs for that. There are some steps you could do to see if they help at all. The first thing to do would be a fresh restart of the computer and see if that helps at all.
0コメント