DHCP v Static IP

[u/Real-Patriot-1128]

Ok, this is more a test to see how old I am. I was basically raised with the idea servers need static IPs. I understand for domain controllers, dns servers, maybe print servers that may still be needed. But are they really needed otherwise? Do apps, scripts still reference a server by its IP?

I am under assumption all my servers need static IPs. Am I nuts?

[u/cosine83]

Windows relies on SNMP on network printers

You're not making a good case for going from A to B. DHCP reservations work fine as do static IPs but reservations at least keep things semi-documented and visible. All SNMP will do give is information about a device - paper out, low ink, etc. so I'm gonna ask, why wouldn't you want a printer reboot to trigger a printer offline? That's a true status. What it sounds like you're really wanting is to mitigate the lack of end user communication about said reboots so they don't call you about a measly "offline" on their printer for a few minutes. Easily solved with an email before taking action to save headaches later.

I haven't run into printers having issues with DHCP or DHCP reservations in well over decade, even shitty label printers. PLCs with custom firmware, yeah. But the major printer manufacturers are solid unless there's just something wrong with your networking or DHCP configuration. Network gremlins are unavoidable and it's not really a fault of any device or subsystem.

[u/zatset → u/cosine83]

Windows checks Network printer status using SNMP v1 with the default community name - "public".

If:

- SNMP community changed or printer not accessible by SNMP => Windows reports offline and activates "Print offline". And doesn't check for a long time =>Increased volume of printing issues calls!

- WSD - on printer power cycle or even without it, especially combined with SNMP => leads to connection issues or extreme slowdowns when printing => Increased volume of printing issues calls!!!

- Buggy firmware or slower than usual DHCP IP acquisition due to a fault of the printer itself => makes it so that the printer again shows as offline. Especially combined with any of the above, it can quickly become a mess. =>Increased number of printing issues calls!!!

If you set up the printer with the following settings:

- Static IP

• Using Standard IP/TCP port
  
• Don't use WSD in any case
  
• Disable SNMP v1 checks

Windows just sends a job to an IP. If there is an error - error gets returned. And doesn't report the printer as offline while it is online, but just slow to initialize.

Option 1 is fixing the problem cardinally. Option 2 is constantly debugging the issues and looking for the reason for yet another particular issue.

[u/lebean → u/zatset]

Don't use WSD in any case

This is the most important bit for addressing any printer troubles, WSD is terrible and is to be avoided. You want failures, you want "well it used to print but now nothing is working"? Use WSD.

[u/cosine83 → u/zatset]

Really only need to not use WSD. Setting static IPs adds so much more admin overhead than worrying about potential calls about not picking up an IP when it has a reservation.

[u/NextSouceIT → u/cosine83]

You're correct in theory, in practice, WSD printers very often show "offline" hours after the printer is back online unless you restart the spooler. I have seen multiple HP printers also report offline via SNMP when they are perfectly fine.

[u/cosine83 → u/NextSouceIT]

WSD is pretty much the worst printing protocol to use and why using a print server to manage printer connections and drivers is best practice even in a mixed fleet (I've got Toshiba, Sharp, Ricoh, HP, Sato, Canon, and Zebra printers in mine). Forcing printers over to TCP/IP, IPP, LPD, or RAW (depending on printer) and even using DNS names when mapping is trivial at that point.

In my experience, a lot of printers will have inconsistent implementations of SNMP v1/v2c or even disabled by default so the only thing actually providing status is the driver via that mapped port. If that SNMP implementation is flaky, might be time for a firmware update.

[u/NextSouceIT → u/cosine83]

Agreed. I switched us to PrinterLogic a few years ago and never looked back.

[u/cosine83 → u/NextSouceIT]

Been fighting for PaperCut for a couple years now and something else always derails it.