HP LaserJet P2035n prints from Windows 10 but not Windows Server 2016

[mauld-louie]

We have an HP LaserJet P2035n printer on the network. If I set it up as a TCP/IP printer on my Windows 10 PC, I can print to it without a problem. But if I set it up on any of our Windows Server 2016 print servers, any print jobs error out in the print queue. Also, when I go to install it on any server (as a TCP/IP printer), it gives the below error, even though I can ping the IP of it from the server. I tried changing the below from "Generic Network Card" to "HP Jet Direct" and that didn't help. It doesn't work with either Generic Network or Jet Direct:

 

I have tried the following drivers on the servers, none of which work, even though the printer shows a status of "ready" on the server: HP LaserJet P2035n Class, HP Universal Printing PCL 5 (v5.9.0), HP LaserJet 5Si. The reason for the 5Si driver is that is how it was originally set up on the print servers. The print servers were previously Windows Server 2008 and 2012 R2, and then the printers were exported and set up on the new 2016 servers. I suspect the 5Si driver is migrated from when it was set up on the older servers. 

Any ideas what else I can try in setting it up on the servers to get it to work?

[Anderson_CR]

Hello,

Hope you are well, looks like the server is not seeing the printer on the network, its recommended to check the server IP address and compare it to the IP of the printer, for example, 192.168.1.0 , server and printer should be 192.168.1.x (x stands for the unique number for each device).

Also, the most easy test is to use the IP address into a web browser URL in the server, this should unlock a printer menu called embedded web server, if the computer have access to this page with the IP address of the printer, the connection is fine, in case it says site cant be reached or unable to connect , make sure the printer and server are in the same network range.

Regards,

[mauld-louie]

The server can ping the printer at the IP address and I can open the web console for the printer at the IP of the printer. I can also print to the printer from my PC at that IP. I just can't get the servers to print to it. 

[Anderson_CR]

if the server can ping the printer IP, a good way to test is to access the embedded web server of the printer from the server and print a report from the web server using the server.  That would confirm the server and printer had a stable connectivity, and no firewall or anything is blocking it.

If that prints fine, it would be a good idea to check the printing spool service up and running, or restart it as well. 

Regards,

[Repairatrooper]

The 2035 is a host based printing system and does not contain a PCL interpreter and the only universal driver you can use is the PCL5 which has not been updated for a few years. 

[mauld-louie]

The embedded web server is not accessible from the server though it comes up on my PC. I cannot print at all from the server (a test page errors out). There is no firewall blocking it or issues with the print spooler service since the server is hosting dozens of other printers that print without an issue, including printers on the same subnet. 

[mauld-louie]

I tried all the PCL 5 universal drivers on the server and none of them work.

[Repairatrooper]

The best advice I can give you is to stop expending energy on this and just go out an buy an M404.

[mauld-louie]

I agree it's not worth putting more time into trying to make an old printer work. It's not my call to buy a new printer but I'll recommend that.