Question : SonicWall DHCP Question

Just started working at a company that uses a SonicWall TZ170 as DHCP server.  All IP addresses are assigned dynamicly; there are no static IP addresses set up on it.  Lately there have been IP address conflicts.  Today, a computer that prints checks conflicted midway through a check run (not good!).

Can someone please explain the logic behind assigning static IP addresses?  What type of machines/printers on our network should have them?  Should we have one for the computer printing checks?  What should I designate as the  scope?

Thank you so much!

Answer : SonicWall DHCP Question

If possible it is best to make your server the DHCP server. It allows for central management, more scope options, secure DNS updates, and proper registration of older clients (older O/S's).

Regardless, servers should always have static IP's, the other common ones are routers, managed switches, and printers. It's important from a management point of view to keep documentation and organize the selection of IP's by services, as an example:
x.x.x.1 to 10 for servers
x.x.x.11 to 50 statically assigned PC's (if needed such as those accessed remotely)
x.x.x.51 to 100 printers
x.x.x.101 to 200 DHCP devices
x.x.x.201 to 254 Routers and managed switches

Though I always recommend static for servers, other devices such as printers can be better managed, if using the server for DHCP, by using DHCP reservations. The device gets its IP though DHCP but always the same IP. This way it shows up in the list of leases in the DHCP management console so you don't have to remember to document what device uses what IP.