Introduction Should you assign DHCP addresses to printers? Why not! As with most things IT, there are many ways to do things. While i...
Introduction
Should you assign DHCP addresses to printers? Why not! As with most things IT, there are many ways to do things. While it would be presumptuous to say this is a best practice,
I have used this methodology for years with no issues. I'll also say up front that not all steps are required, but the steps in this topic are tried and true.Steps (5 total)
[Optional, but if you are going to do it, do it first.]
As with anything worthwhile in IT planning is key. I sub-netted a class C block of 10.x.x.x addresses into Servers (/26), Printers (/26), and Netman (/25). Your mileage may vary depending on your device counts.
This should be pretty straight forward in Windows Server. Remember - don't use the first or last IP addresses of your subnet, in the IP range of your scope.
I prefer to populate the reservation name but it's not required. I do it so I havet a meaningful name in DHCP. It's easier to browse the list of devices with my name [as opposed to the default name from the printer]. Also, in windows, just type the MAC address. No separators are required or tolerated.
Ensure your printer has DHCP selected in it's network settings. If not, select it, save and power cycle the printer. Be patient, printers are not the fastest devices around.
After what seems like forever, and is actually no more than a minute or two, your printer will have what is essentially a static IP.
Conclusion
One of the reasons I like the method is because it is dependable. No matter where you place that printer, if it's plugged into correct VLAN at the switch, the printer will always have the same address. [If you have a flat network with no VLAN's it will still pull the same IP.]
The best reason though is all record keeping is on the dhcp server! You can export the list of reservations or leases to a text file as a backup if want
No comments
Post a Comment