Link to home
Start Free TrialLog in
Avatar of garymiller
garymiller

asked on

HP 2055 Lost the IPV4 config settings under Network Config

I have an HP 2055DN that was working fine until a reboot today. It had started acting strange, which precipitated the reboot.

After the reboot, no network activity was taking place. After minor troubleshooting to eliminate cabling, I looked at the network config. I can now only see DHCP, Manual, and IPV6 as configuration options under the Network Config menu.

I have an identical printer in back. checked it, and sure enough the IP BYTE's, GW BYTES', SM BYTE's, are all there and configured. Replace this printer with "bad" printer and after changing the IP, it works fine as expected.

So, somehow, the printer lost it's IPV4 menu options. I reset back to factory, and no changes under the Network Config Menu.

Any ideas before I make this a USB printer for the rest of it's life?
Avatar of cooledit
cooledit
Flag of Ireland image

latest firmware installed/updated.
ASKER CERTIFIED SOLUTION
Avatar of davorin
davorin
Flag of Slovenia image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Always update the firmware first, then try it. If your unit is still under warranty, you can always harass HP :)
Avatar of garymiller
garymiller

ASKER

You know, it never occurred to me to check the DHCP option for being turned off, as it had always been configured as static. So, for some reason, the printer either on its own reverted to DHCP, or one of the users messed with it. I don't think they did, knowing them, but of course it is possible.

It looks like this is going to be the solution. Disabled DHCP and of course, the V4 options are back!

Thank you.
You are welcome. It had happened to me that exactly the same printers have lost network configuration in past. I don't know why, but I would blame more electricity problems then users.
I think you are right. They were having issues, and turned it off and back on, and that is when it probably happened. Thanks again !