Receive IP address by DHCP as client (HP Laserjet 1320n)

[4GottenOne]

Hello! I've faced with a problem regarding assignment an IP address for the printer (model HP Laserjet 1320n) by DHCP server, which could be received by client-side request to my network router. Such approach is very useful for the corporate network.

Is it possible to set up an option for this printer, to "make him do" like a client, receiving the IP-address from the router? So will it be dynamical or static, will be a headache of the router itself.

What I can do now, is to set up the printer as DHCP-server, but this make no sense, because of actual working router as the DHCP-server.

[davidzuts]

Not sure what you want to do. The best way if using windows is to leave the printer on dhcp and use the host name of the printer instead of the ip address. The host name will never change unless you change it so no matter what ip address the printer has, the user can print as long as the port is set to the host name.

[4GottenOne]

Thanks for your answer!

Yes, it is like you said now. PC's are working with hostname of the printer (I called it HPLJ1320), so it doesn't matter of assignment of IP address, therefore any client PC have an ability to start printing. But I need something else.

The situation look like this: I have a pool of free IP-addresses to "lease", let's say it starts from 192.168.1.2 and ends by 192.168.1.254. In my local network many different PC's could lease addresses from the pool, so a client could "take" any address from this pool, so the printer could. I don't know how to set up this feature.

Now the printer have some static IP-address (which is actual 192.168.1.100), but theoretically one of client could "get" this address from the free pool, and this will cause a conflict. So I want the printer IP address to be dynamical along the network. By another words, to "make him do" like a DHCP-client, not a server.

[4GottenOne]

Now, if I activate BOOTP/DHCP option in the printer webinterface setup, the printer beginning to work as DHCP-server and starting give away IP-addresses to the clients, in subnet like 162.254.xx.xx

[Matti_Kurkela · Accepted solution]

If a client takes on an IP address in the 169.254.xx.xx subnet, it actually means the client did not receive an answer from the DHCP server and used the Zeroconf procedure instead.

Have you excluded the real DHCP Server's own IP address from the pool of DHCP-allocatable addresses? If not, the DHCP server might be giving out its own address to a random client, thus making itself hard to reach due to an IP address conflict.

(A well-implemented DHCP server should not make a stupid mistake like that, but I've also seen pretty poor DHCP server implementations in some non-enterprise routers.)

As far as I know, HP printers do not include DHCP server functionality at all.

[4GottenOne]

You were right! Thanks a lot 😃

Question is now closed.