cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Printer with Static constantly getting caught in IP Conflict Reports

mcholin
Contributor

We have a Canon LBP6670 with a Static IP Address set in the configuration, we can access it via the Web interface and printing is working normally for that device. 

 

The issue we are having is that our Meraki Firewall is monitoring for IP Conflicts on the network and there are days that this particular printer will be involved in 60+ conflicts over an hour period. The IP address that gets reported as conflicting is always different and will be different from 1 second to the next, the only consistency is that the IP Address always falls under the APIPA Scope of 169.254.x.x. We also tried setting the printer to DHCP with a reservation address and the issue continued to happen as if no change had been made. 

 

As mentioned the printer is working on the static IP that we have assigned to it and even when the conflicts are being reported we can remote into the web interface of the prinmter and print to it. What I am wondering is, has anyone here had similar experiences and is there a way to get the printer to stop reporting the various APIPA addresses when it has a static IP or a DHCP one? So far the only way we have been able to stop this device from being reported as a Conflict IP Address was to remove it from the network and use it via DHCP.

10 REPLIES 10

Thank you for the reply.

 

We are not using DHCP on the Meraki, it is hosted from our Windows Server inside the network. The printer also has a static IP address assigned and is always avaialble from that device. And finally, the Client IP Conflict being reported fromour Meraki device is always a 169.254.x.x Address or the APIPA that a system defaults to when not assigned a static or a DHCP address.

 

The reported APIPA address will report a conflict across 10-20 addresses all with the same MAC addresses in the same reports. 

Announcements