Windows cannot connect to the printer the server print spooler

Printer now working again. Just need to stop it re installing it again LOL. Have you tried anything to fix it? Is this a home setup or business- Is the printer connected to one pc with USB — on that pc can you do a test print? Tried switching the printer off and on? If you have not already — uninstall the last win10 update. If it doesnt correct it then the problem lies elsewhere so you can re install it. Re Recent update After installing this update, Windows print clients might encounter the following errors when connecting to a remote printer shared on a Windows print server:.

Note The printer connection issues described in this issue are specific to print servers and are not commonly observed in devices designed for home use. Printing environments affected by this issue are more commonly found in enterprises and organizations. Notify me of followup comments via e-mail. You can also subscribe without commenting. Leave this field empty.

Home About. Connect to Printer Windows cannot connect to the printer. You can also use the PowerShell to uninstall the printer driver :. Learn more about the main ways to uninstall updates in Windows. If you are deploying updates from a local WSUS server , you should decline their installation.

Connecting a printer via a local port is described in the article about another common error connecting a network printer — 0xe. Related Reading. January 10, December 29, Vipin January 15, - am thanks a lot done. Aviad March 9, - pm is this command removes the driver from the localhost or from the print server? Bogdan December 3, - am Simple and efective. Job done. Eduardo March 3, - pm Thanks!! Mark Isi Microsoft Agent. Hello, We can offer a few troubleshooting steps related to this issue and see which helps.

Type services. Find the Print Spooler services, right-click and select Stop. Leave the services window open and launch the Run dialog once again. Check if the folder is empty. If otherwise, delete all files. Go back to step 3, right-click and select Start.

Restart your PC. Keep us posted and let us know the outcome. How satisfied are you with this reply? The new method must exist on the client and server to successfully connect to and copy spool files to the share. The client systems "should" have already been updated, Win 10 have had the method since February of this year. I do not expect this protocol method to be available for Windows 7 but we will see how many people react to this new requirement.

Also, if there are Mac systems connecting to the shares, the Macs don't have the protocol method so I am unsure what Microsoft will do for Apple. Error , this is actually a domain services mismatch error but I think this is just confusion on the client spooler due to the protocol mismatch and Error 0xb.

Enlightening in that it points to something I had never really considered until I was running a Wireshark on Client-Server printing. This is outbound from the actual printer object in Windows. For logged in domain clients authentication is pre-established. An administrator had set-up printers outside of AD in some atypical manner and the SMB transaction changed to force a kerberos auth prior to proceeding, producing a second delay seen when accessing printer preferences as well.

Slow is on the left and has to start the SMB spool as a typical port negotiation from scratch. Get answers from your peers along with millions of IT pros who visit Spiceworks. I have a server that is still R2. It also is our DC. This server acts as the print management server. The only change that was made was a bunch of updates on the DC and the dc restarted. Event viewer logs short of a error i saw arent very helpful on those affected machines. One machine is running windows 10, the other workstation is still on windows 8.

EDIT: I had one error but it was last night this event viewer is from the server itself While attempting to publish the printer to the Active Directory directory service, the print spooler could not find the appropriate print queue container because the Domain Name System DNS domain name could not be retrieved.

Thanks in advance. Popular Topics in Windows Server.