Printer using DHCP.

[Blammo300]

I have a HP 8150DN Printer on my office network which connects to the internet through a Linksys VPN Router using Verizon Static DSL.

The printer is currently set up as DHCP, will the DHCP cause my printers IP address to change?

 

[thirdlegstump]

Use DHCP only to have it configure itself once for the first time and never as a permanent network address. I'd static that sucker with an IP outside the DHCP scope.

 

[Blammo300]

I am currently on the Printer settings web page that shows the DHCP, Manual, and BOOTP as my choices. Right now it is on DHCP and I am trying to change it to manual, but when I do change it to manual and click apply it always reverts back to DHCP setting. Or it will ask for a community name, but it will say invalid name until I switch back to DHCP.

If my router loses power will the printer change its IP with the current config? If it changes IP wont I have to set up the printer again for all the client computers?

 

[spidey07]

it will more than likely keep that address for eternity.

Best practice is to setup a DHCP reservation to make sure it gets the same address.

The only thing in modern networks with a statically assigned address should be network infratucture gear (routers/switches/firewalls, etc)

 

[nweaver]

Originally posted by: spidey07
it will more than likely keep that address for eternity.

Best practice is to setup a DHCP reservation to make sure it gets the same address.

The only thing in modern networks with a statically assigned address should be network infratucture gear (routers/switches/firewalls, etc)

:thumbsup:

good all around advice there.

 

[OdiN]

Originally posted by: nweaver

Originally posted by: spidey07
it will more than likely keep that address for eternity.

Best practice is to setup a DHCP reservation to make sure it gets the same address.

The only thing in modern networks with a statically assigned address should be network infratucture gear (routers/switches/firewalls, etc)

:thumbsup:

good all around advice there.

I disagree. I manully set static IP's for network printers. I have had less problems this way than any other way.

 

[IamElectro]

Originally posted by: OdiN

Originally posted by: nweaver

Originally posted by: spidey07
it will more than likely keep that address for eternity.

Best practice is to setup a DHCP reservation to make sure it gets the same address.

The only thing in modern networks with a statically assigned address should be network infratucture gear (routers/switches/firewalls, etc)

:thumbsup:

good all around advice there.

I disagree. I manully set static IP's for network printers. I have had less problems this way than any other way.

I would have to agree with OdiN here static IP will save you trouble down the road. We maintain over a dozen network printers in our labs. One printer in particular a HP design jet 1050c was configured for DHCP would for no reason drop its IP address occasionally and need powered down and restarted to pick the IP up again. I reconfigured for static and the problem went away.

 

[spidey07]

well the big problem with static addressing is when/if you have to renumber an IP network the printers and static addresses will make what should be an easy switch a total nightmare.

 

[BML]

Most dhcp servers bing the logical address to the physical address, This is then put into a database. Most dhcp leases are 8 days. The dhcp server will keep the the logical address bound to the physical address as long as its not needed. If your dhcp server is running out of ip address then your printer might have its ip address taken, thats if its off for 8 days. You should be fine with it on dhcp, just make sure dns is working good.

 

[nweaver]

The reason to use DHCP is because you have random assignments (often not documented) and then you have conflicts, etc. That is why they created the reservation table in DHCP. Now you have all the convience of Static with the convenience of DHCP. If a printer is having issues using DHCP, then fix the printer.

I only assign static IP's to my infrstructure, such as routers, switches, and critical servers. I do this and do documentation one time when I build out an enviorment. My AD server, DHCP, DNS, Routers all get IP's static. All the other servers get reservations not in the scope, and the switches (normally) get private IP's on a different subnet asigned to vlan 1, and I assign myself a static IP in the range (or on the server, with a normal IP and the private IP) if I need to talk to them.