Network Printer - Cannot Acquire a Lease through DHCP

[Stoa]

TL;DR:  Changed ISP and printer does not/cannot acquire a lease from new modem/router.

I haver an Hp LaserJet 4050 with an HP 615n 100BASE-T NIC.  This setup would acquire a lease and work flawlessly through an AT&T 2WIRE router.  No special setup was needed other than enabling DHCP/BOOTP on the printer.

I then moved to an area not serviced by AT&T.  My new provider, CableOne, provided me with an Arris Touchstone Gateway.  All of the computers on my LAN will acquire leases without issue, but the printer will not.

I've looked at every setting available through my gateway's web interface and can find no setting that will permit the printer to acquire a lease or would otherwise cause/fix this situation.

I have reset the printer settings to factory defaults.  The TCP/IP section of the configuration settings on the printer will show the default IP of 192.0.0.192; the status will show "55 - BOOTP/DHCP IN PROGRESS"

The printer's NIC is communicating, as Wireshark will show IGMP messages from the printer to a couple of different multicast addresses.

Any hints in diagnosing are appreciated.  If further info is needed, please let me know.

[sabretooth04]

Please provide the following relevant information so someone can help including:

Printer Model - done
Complete and Detailed Problem Description -
Operating System of computer (including service pack revision) -
Connection Method - USB, Hardwired LAN, Wireless? -
Make and model of router and modem? -
Error messages - on printer screen and/or computer, any blinking light patterns?
If wireless, when the problem occurs, what is status of Blue Wireless light on printer, on, off or blinking? –

Power off printer and router. Power on router and wait 3 mins, power on printer. Does it connect to the router now? Do you have a valid IP address?

What is the IP of your router/gateway device?  Your printers IP is not correct.

[Stoa]

Hello sabretooth04, thanks for your reply.

I thought I had provided most of that information, but here goes:

Detailed problem description - see original post - too detailed to repeat.

OS of computer:  I have seven different OSs on this LAN, including OpenBSD, FreeBSD, Arch Linux, Gentoo, slackware, and windows Vista, SP2.

Connection is ethernet.

Make and model of modem:  Make: Arris; Model: Touchstone Data Gateway.

Error messages: none.

Printer has been powered off/on multiple times to no avail.  The printer is sending DHCP Discover requests (multiple) but not receiving a DHCP offer from the router/modem.

So the question is, what is wrong with the network/router/moden that it will not respond to the DHCP Request?

[sabretooth04]

What is the IP of your Gateway? What is the IP of your printer?

[Stoa]

What is the IP of your gateway: 24.116.197.12.

What is the IP of your printer:  That's the problem!  My printer cannot acquire a lease!  It only has it's default IP of 192.0.0.192.

[sabretooth04]

Well your all screwed up. Not even the same network.

Set the IP of the Gateway to 192.168.1.1. DHCP starting address at 192.168.1.50. Ending address at 192.168.1.100.

Set the printer to a static IP of 192.168.1.10. Now you are on the same network.

[Stoa]

I think we are miscommunicating.  My *public* gateway address is as I stated.  My subnet ID is 192.168.0.1.  My DHCP server has addresses available from 192.168.0.2 through 192.168.0.254.

The printer is on the same LAN because it is behind the same router (the one and only router).

The printer is broadcasting DHCP Discover requests, as it should be, from 0.0.0.0; the problem is the router's DHCP server is not responding with an offer.

[davidzuts]

Lets make this real easy.  On the printer go to the EIO menu and then configure the jet direcard manually at the printer.  Easy to do as you all have to do is change any no to yes and it will give you access to make the necessary changes.  You have to change the method on the printer from bootp or dhcp to manual and then you will be able to assign a physical ip address.  Once you make the changes run a config page on the printer to make sure they have stuck and then use the address you gave the printer to load on the computer as a local tcp/ip printer.