Windows 2016 Server Print Management and shared printer issues? Cannot set up shared printers only via IP off server.

Anonymous
2022-07-29T21:26:15.587+00:00

We have a print server VM 2016 server OS, not allowing shared printers to send print jobs to machine. We have tried the following:

  1. troubleshooted the printer/copier itself. Made sure the settings were correct.
  2. Had network verify the Vlan 2 on the port
  3. They do connect to Host site, and we tried connecting through a similar print server.
  4. Reinstalled the OS for the Print server.
  5. backrolled windows updates
  6. tried older printer drivers

That is as far as I got. We have them printing via IP direct connection.

Windows Server 2016
Windows Server 2016
A Microsoft server operating system that supports enterprise-level management updated to data storage.
2,425 questions
Windows Server Printing
Windows Server Printing
Windows Server: A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.Printing: Printer centralized deployment and management, scan and fax resources management, and document services
653 questions

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2022-08-01T21:54:10.67+00:00

    Yes, the problem is that there are no errors in the event logs, it only gives the windows message that the job failed.
    The printer is correctly added to our VM print server, you can send a job by adding the printer on a client machine by ip, but not through the printer server.

    226846-event-viewer-error.png

    0 comments
  2. Alan Morris 1,161 Reputation points
    2022-08-02T00:06:29.63+00:00

    @Anonymous

    The printer on the server is set up using a Standard TCP/IP Port, correct. No WSD please.

    Does the job from the client get fully copied to the print server. Check the spool file size. The default location is in C:\windows\system32\spool\printers but I do always suggest moving this to a different location not under systemroot. If it's zero bytes that would be part of the issue.

    After that 801 event, I hope that is the client job, there should be 805, 842, and 307.

    I see the file is a Word doc. You are not selecting only some pages, correct.

    The server name does not have DC in the machine name so I am confirming the print server is not now nor ever was a Domain Controller. dcpromo messes with the file security. DCs make unreliable print servers.

    Enable debug spooler logs. I attached a video how to do this. Save the logs in EVTX format.

    226908-printservice-debug.gif