Windows 10: Non-Domain Windows Computers Unable to Print via Print Server

Hello,We recently encountered a problem i.e. multiple machines wherein if they attempt to add a printer or print via our print server they encounter an error:"Windows cannot connect to the printer. Operation failed with error 0x0000007c."The other error that we are getting is in the Device/Printers pane "Driver needs an update." For the computers on our domain, updating the driver was relatively easy/painless. For computers not on the domain however, it seems to be much more problematic.One user was experiencing an issue wherein any they tried to print from would become unresponsive. Another

:)

 

Basic print server

yes, its linux, itl work with any os and any printer.

GRANTED you might have to make sure you are useing a router with the proper hardware to be able to connect to the printer, or some kind of gobetween, like my router does not have USB...

not real sure about DD-WRT's print server capibilitys but openWRT definatly has a package for that

cups[linux style print server]
p910nd[i dont know style print server, says something about non-spooling whatever that is.]
samba-server[windows style print server]
kmod-lp [driver for oldschool printers]
kmod-usb-printer[driver for usb printers]

 

Basic print server

Are you sure that Canon MP830 is even print server capable?

Also, you'll lose a lot of printer features by plugging it into a print server. It'll pretty much only be able to print.

 

Print server instantly "prints" documents after they spooling but nothing actually prints.

We have a print server running on a Hyper-V Generation 2 Virtual Windows Server 2016 1607 hosted on a Windows Server 2016 1607. Up until a couple of days ago, things were printing fine,
now all of a sudden we are unable to print anything. Documents will briefly spool and then disappear from the queue. If a printer is set to keep printed documents in the queue they will show as printed immediately after they finish spooling no matter how many
pages are supposedly printed.

Here's the troubleshooting I've tried so far:

• Ensured Print Server has the latest Windows Update
• Uninstalled the most recent non-security updates since problems started (and shortly before)
• Restarted Server
• Restarted Print Spooler service, both using the restart option and simply stopping and starting it
• Ensured printers print on their own; both configuration pages and USB direct connect
• Tried printing from Multiple computers, including the print server itself
• Shut down print spooler and cleared everything out of System32\spool\PRINTERS
• For one of our multi-purpose printers I:
  • Created a new printer and port to it's IP address
  • Tried literally ever latest Windows 10 Driver available on the manufacturer's site.
  • Tried every Print Processor
  • Unchecked "Render print jobs on client computers"
  • Unchecked "SNMP Status Enabled" in the port configuration
  • Set it to print only after all pages are spooled
  • Unchecked "Print spooled documents first"
  • Checked "Hold mismatched documents"
  • Set a new IP Address

The only major change since this problem arose was a change to the permissions, but as far as I can tell the permissions are set up correctly and this doesn't sound like a permissions
issue because there's no permissions errors and documents are spooling correctly.

Any new suggestions are welcome because I've run out of ideas and at this point we are considering just rebuilding the thing on physical
hardware to see if Hyper-V is causing the issue.