Can not Install Network Printer on Windows 2019 Standard

Question

I am trying to install 2 network printers on a new Windows 2019 Standard server. This is my first time with a Windows Server and I did not setup this Server. I can ping the printers from the Server but I can not open the printers' web interface from the server. I know the IPs are good because I installed them on my computer and I can print test pages, ping and web interface from my computer but not the server. I think there is a setting somewhere in the GP or the server manager somewhere that is blocking them somehow but I do not know enough to find it. Does anyone know how to fix this? Any and all help is greatly appreciated!

Windows 2019 Standard Server V1809 64bit

HP LaserJet P4515n and HP Color LaserJet CP2025 both can use the HP Universal Driver PCL6 downloaded from the HP site as well as the Windows update one from the search.

I have tried from both the server manager/print manager and the control panel/add printer neither work.

The error I get is to make sure the printer is on (it is), connected to the network (it is), and the address is correct (it is).

The printers will act like they install but then they say either offline (SNMP status is checked which it is on the old server) and will not print or they say ready (SNMP status unchecked) and will not print. The error simply says failed to print.

There is this error stuff but I do not know if it is for the printer, is effecting the printer or is irrelevant.

Faulting application name: ctfmon.exe, version: 10.0.17763.1, time stamp: 0x4923c22a
Faulting module name: InputService.dll, version: 10.0.17763.1432, time stamp: 0x8e1dc10e
Exception code: 0x00000675
Fault offset: 0x00000000002a1cbc
Faulting process id: 0x680
Faulting application start time: 0x01d69e7e9ce5a36e
Faulting application path: C:\Windows\system32\ctfmon.exe
Faulting module path: C:\Windows\system32\InputService.dll
Report Id: da7bee30-bc0b-4677-9e6f-a1f086728e69
Faulting package full name:
Faulting package-relative application ID:

Answer 1

Turns out the issues was with firewall rules. Thank you for your help in fixing this!

Answer 2

How would I do this? How do I patch fully?

A clean install is done by booting the install media, delete / recreate partitions and continue the install. Then patch fully by turning on automatic updates, or optionally install them from update catalog.
https://support.microsoft.com/en-us/help/4009470/windows-8-1-windows-server-2012-r2-update-history

--please don't forget to Accept as answer if the reply is helpful--

Answer 3

There is this error stuff but I do not know if it is for the printer

I'd check the operating system is patched fully, check here and with manufacturer about support for Server 2019
https://www.windowsservercatalog.com/

also check the manufacturer's site for the latest firmware, ROM bios, chipset and driver support pack.

--please don't forget to Accept as answer if the reply is helpful--

Answer 4

I have been running updates on this machine daily since 10-1 and monthly before that since 7-30 in prepping the machine to take over for an old Windows 7 machine. Are there updates that do not come through automatically? I tried the link you posted but it did not make much sense to me unless I am looking for things that work with/are compatible with windows server? They are HP printers so I am guessing they should be compatible. I tried a search in the windows catalog but the newest update I could find says it is already on the system. Are there others I should look for? The drivers are newest available on HP site.

Answer 5

I was referring to the server itself. Also check Control Panel\Network and Internet\Network and Sharing Center\Advanced sharing settings\Turn on file and printer sharing

Also note the jet direct ports mentioned here may need to be allowed through firewall.
https://support.hp.com/us-en/document/c02480766

A new install should be be throwing the mentioned errors. You can also try a repair install by running setup.exe from the root of the install media, but time may be better spent clean installing it, patch fully, migrate the roles / applications back over.

--please don't forget to Accept as answer if the reply is helpful--