MXB455w pulling zeroconf IP address

[mttech]

I’ve got an MXB455w that is pulling a zeroconfig IP address, such as 169.xxx.xxx.xxx(zeroconf), whenever it is power cycled. It is set for static IP and wired only network. Can someone enlighten me on why and where it is receiving this. Is there a network service or protocol setting that needs to be disabled? It is in a small 2 person office, one has Windows7, the other Windows10. When the NIC pages are printed the first page shows the zeroconf IP, the second page shows the static IP. I must use the zeroconf IP to access the copier webpage.

[Phil B.]

I’ve got an MXB455w that is pulling a zeroconfig IP address, such as 169.xxx.xxx.xxx(zeroconf), whenever it is power cycled. It is set for static IP and wired only network. Can someone enlighten me on why and where it is receiving this. Is there a network service or protocol setting that needs to be disabled? It is in a small 2 person office, one has Windows7, the other Windows10. When the NIC pages are printed the first page shows the zeroconf IP, the second page shows the static IP. I must use the zeroconf IP to access the copier webpage.

other than playing with the IP addy ... what have you done? try a new net cable... are the lights on the nic lit?

[mttech]

The NIC and cable are fine. I got them printing for now by changing the printer IP address in port configuration in the driver to the zeroconf address, but this is just a work around.

[Phil B.]

The NIC and cable are fine. I got them printing for now by changing the printer IP address in port configuration in the driver to the zeroconf address, but this is just a work around.

so if you set it up on DHCP it doesn't pick up an address?

[mttech]

It will pick up an address with DHCP that is in the 192.xxx.xxx.xxx format. Once the copier is power cycled the address changes to the 169.xxx.xxx.xxx(zeroconf) format. For now I have disabled auto power shutoff and asked customer not to turn copier off as it is printing with the changes I made in the driver. After some research I believe it has to do with mDNS being enabled in the network service settings. I am going to disable it tomorrow and see what happens.

[JLSam]

It will pick up an address with DHCP that is in the 192.xxx.xxx.xxx format. Once the copier is power cycled the address changes to the 169.xxx.xxx.xxx(zeroconf) format. For now I have disabled auto power shutoff and asked customer not to turn copier off as it is printing with the changes I made in the driver. After some research I believe it has to do with mDNS being enabled in the network service settings. I am going to disable it tomorrow and see what happens.

Sound like you are having a classic case of an IP CONFLICT.

Basically, whenever you restart, another device is getting your IP in the network. *NOTE* No, it does not matter that you have your machine as static, in fact, that may be the problem.**

SOLUTION:
Simply reserve your IP on the router. Some routers call it "IP allocation", others "DHCP Reservation". Whatever you want to call it, you want to RESERVE the IP address to the MAC address of the printer. If you need help doing this, contact their IT. Or any computer tech worth their salt should be able to do this simple task, in less than a minute.

Good luck.

[mttech]

Disabling mDNS in the network service settings solved my problem. I attached the NIC pages. I don't think I did a very good job of explaining what was going on. Thanks for all the replies.

[Phil B.]

It will pick up an address with DHCP that is in the 192.xxx.xxx.xxx format. Once the copier is power cycled the address changes to the 169.xxx.xxx.xxx(zeroconf) format. For now I have disabled auto power shutoff and asked customer not to turn copier off as it is printing with the changes I made in the driver. After some research I believe it has to do with mDNS being enabled in the network service settings. I am going to disable it tomorrow and see what happens.

so when it picks up the 192.xxx.xxx.xxx di you make that a STATIC addy for the machine?

if it keeps dropping the addy.. you might have their IT folks look into it.