If the printer/servers are on different subnets, you need to check that the needed communications can occur. you are not getting far enough along yet that a specific printer driver can even be installed. I know you say you can ping the printer, but this still looks like a network issue. I suspect the 5Si driver is migrated from when it was set up on the older servers.Īny ideas what else I can try in setting it up on the servers to get it to work?Īre the servers on a different subnet from the printer? If so, were the OLD print servers also on the subnet the new servers are on? The print servers were previously Windows Server 20 R2, and then the printers were exported and set up on the new 2016 servers. The reason for the 5Si driver is that is how it was originally set up on the print servers. 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. It doesn't work with either Generic Network or Jet Direct: I tried changing the below from 'Generic Network Card' to 'HP Jet Direct' and that didn't help. 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.

But if I set it up on any of our Windows Server 2016 print servers, any print jobs error out in the print queue. If I set it up as a TCP/IP printer on my Windows 10 PC, I can print to it without a problem.

We have an HP LaserJet P2035n printer on the network.

Drivers hp laserjet p2035n