For the rest of us, our HP printers struggle to resolve remote AND local DNS records for AWHILE, in my case 2+ hours, even when they have received valid, working and reachable DNS servers via DHCP.Īnd if the HP is having a DNS meltdown, then it’ll repeatedly fail to resolve a valid network path with an FQDN and (rudely) blame YOU for providing an “invalid” path. Granted, if the FQDN is already working for you, then by all means, use it.

🧨 Instead of using the FQDN of the server in the network path, use the server’s IP address, at least until the printer starts resolving DNS correctly. Yes, it really, really sucks, and using a top-level share folder poses other challenges, but I’ll share how I worked around this a bit later. Don’t waste hours of your life fighting this like I did with mine, because it’s just an HP problem that affects some (not all) of their printers, and there may not be any true fix for this limitation short of a firmware update.ĭon’t waste hours of your life fighting this like I did with mine. I couldn’t believe this was true, especially since I’ve seen it work with other HP printers, and NONE of the existing forum threads talk about this limitation, but here we are. If it sounds ridiculous, it’s because it is. Alas, ( surprise?) some HP printers just CANNOT figure out network share subfolders. In other words, instead of this thing that you wanted to do: The Network Path should be a top-level share folder of an existing SMB share. Please note: I am not affiliated with HP in any way.

Hp scan to folder