This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(144, 40%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJW%3C/text%3E%3C/svg%3E)
We recently upgraded our networking equipment, and in the process have had lots of issues with firewalling on the subnet where this domain lives. The router firewalling is supposedly resolved now, but I am unable to print from the domain controllers on the domain.
Prior to changing gear, we had a CUPS print server setup to accept connections from all of our public subnets, but we've had to tweak this a bit since the change to take NAT-ed subnets. The router firewall seems to be as open as it's going to get to allow printer ports (631, 515, 9100) and yet I am getting "Printer Busy or Error" in the print queue on the server, and the document never reaches the CUPS server.
Domain controller firewall and A/V software has been disabled and still the same results. I can print to these printers directly via IPP on individual workstations, but if I use an LPR/LPD connection, the system never completes the handoff to CUPS. I can set up the IPP connection on the domain controller, but attempting to print or look at printer properties always crashes MMC or explorer.exe every time. This is with print services, LPD printing, IPP printing, and the various related features installed. Both on the old server (2008r2) and the 2012r2 server I am trying to set up to replace that one. At this point I am at a loss what to do, other than individually add IPP printers as local printers to each of our workstations by hand. What -- if anything -- am I missing on the troubleshooting here?
To confuse the issue a bit further: I configured printers on the 2012r2 domain controller using an IPP port, same way I would have configured it for a non-domain client. When I run tcpdump on the CUPS server, it's seeing the incoming traffic as "printer" -- i.e. tcp/ip port 515 -- instead of "ipp" on port 631.
Printing from the same IPP port on a domain client directly to the CUPS server, the CUPS server sees that traffic as "ipp" traffic, not "printer" traffic.
I'm just trying to make sure this is not Windows Server doing something weird with printer ports, before I fully dig into the CUPS side of things.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(252.8, 30%, 34%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EEY%3C/text%3E%3C/svg%3E)
Hi,
Please check if there is any related event log on both the server and clients that might indicate some possible causes.
Event Viewer - Windows Logs - Application/System/Security
Event Viewer - Applications and Services Logs - Microsoft - Windows - PrintService
Thanks,
If the Answer is helpful, please click "Accept Answer" and upvote it. Thanks.
Nothing related to printing errors in any of those logs. The PrintService log only shows me when the print service was restarted/stopped/etc.
I did another wireshark session on the domain controller, and tcpdump on the CUPS server, and NONE of the IPP traffic is appearing now. Print jobs never get started, apparently, if the port is configured on IPP port 631. I did a LPR port test, and an IPP port test, and only the LPR port traffic is captured. And as usual, the connection is reset, resulting in a lack of printing from any port on the domain controller.
But as usual, if I print to an IPP configured printer from the workstation, I can see that traffic flow, and print jobs complete normally.
Hi,
You might need to capture some dumps or traces to further investigate the issue, which I suggest to contact Microsoft Customer Support and Services where more in-depth investigation can be done so that you would get a more satisfying explanation and solution to this issue.
You may find phone number for your region accordingly from the link below:
Global Customer Service phone numbers
https://support.microsoft.com/en-us/help/4051701/global-customer-service-phone-numbers
Thanks,
If the Answer is helpful, please click "Accept Answer" and upvote it. Thanks.