Canon IR C5235 - start network failed after firmware update.

**Pierre-69** · 12-09-2019

Hello,
After Firmware update on IR C5235, I'm unable to connect to the network.
At boot, I get "starting IP network ..." and "Verify TCP/IP". Everything was verfied and with the initial IP address (before update), I get "IP conflict" writen on the display ( There is no conflict with this IP on the network, may be only inside the copier ).
I tried with DHCP, but nothing is working...
The firmware update seems to be good in the logs, but the network is dead....
Anybody can help me about this problem please ?
Is it possible to restore the old firmware from HDD ?
Thanks,

**alex@wocltd.com** · 12-09-2019

how did you do f/w update? the fault you list has happened at my work when technician has gone back not forward with f/w via ota

**Pierre-69** · 12-09-2019

I was in service mode when I updated the firmware. I don't remember exactly, but I verified server parameters, select the firmware and launched the update. I didn't stop any process.
How did you solve this network problem after f/w update ?

**teckat** · 12-09-2019

How do I test for a possible IP address conflict or duplicate IP address on the network?

Answer :
This article provides step-by-step instructions with screen shots on how to properly and accurately test for a possible duplicate IP address or IP address conflicts on a network. Two methods are discussed:

Method 1 - Ping the Device, Unplug the Device, and Ping the Device Again (DO NOT USE) this is not an accurate method:

This method is the most common and popular way, that people use in trying to identify or test for a possible duplicate IP address on a network. Unfortunately, this is not an accurate way to test for a possible IP address conflict on a network. This method is not accurate and will lead you to an INCORRECT conclusions. It is strongly recommended that you use Method 2 instead.
Step 1: Type the command ping .

You then get a response from what you think is the device that you are testing.

Step 2: You then go to the printer (or device) and disconnect the Ethernet cable from that printer (or device)
Step 3: Type the command ping .

You then ping the device again and this time you get no response from the ping.

So, now you believe that you don't have any duplicate IP address or IP conflicts on your network and you believe that the IP address that you just pinged is the one going to the device that you are testing.
THIS CONCLUSION IS NOT ALWAYS CORRECT:
All that you just proved or tested, is that the device or IP address that you just pinged responded to your ping request. This is not an accurate method for testing for the possibility of an IP conflict on the network.

Method 2 - Using the ARP Table (USE THIS METHOD):
The PROPER and ACCURATE METHOD of testing for a duplicate IP address or IP address conflicts is to perform the following:
Step 1: Type the command ping .

You then get a response from what you believe is the device that you are testing.

Step 2: Type the command arp -a .

A list of the IP address to MAC address mappings (the ARP table of the PC) will display.

Step 3: Write down the MAC address that responded to the ping command of that IP address.
Step 4: Remove or disconnect the network cable that is connecting the printer (or device) to the network.
Step 5: Type the command arp -d .

This will remove the IP address to MAC address mapping that you just pinged from the computer's ARP table. If you don't perform this important step, the computer will no longer look for the IP address that you are pinging. It will now only look for the reply from the MAC address of the IP address that was last associated with that IP address.

Step 6: Type the command ping . Did any device respond to this ping?

Please keep in mind that if there is another device on the network that is using the same IP address, it will take a while for that device to regain control or begin to responding to the ping command. It is suggested that you wait at least 10 to 15 minutes. Also keep in mind that if this problem is not happening several times on a regular daily basis, it will be more difficult to find.

In this example after performing the above steps and waiting a few minutes, we were able to identify that some other device did begin to respond to the ping command that we were troubleshooting. Being that the original device is still disconnected from the network as per step 4, nothing should ever respond to the ping command for the IP address of the original device.

Step 7: Look at the MAC address (Physical Address) that now responded to the ping command (if any), while the original device was disconnected, via the arp -a command. If the MAC address is different from the original MAC address you wrote down in step 3, then there is a different device using the same IP address (a duplicate IP address).

Write down the MAC address (Physical Address) that corresponds with the IP address (Internet Address) that responded to the ping command when the original device was still disconnected from the network. This will be your only proof that some other device is configured with the same IP address that was assigned to the original device.

By looking at the first six (6) characters of the MAC address, you can now identify who the other device's manufacturer is. You can then begin to look around the office with the customer's network administrator for the device using the duplicate IP address.

In our example, we are now able to identify that the first six (6) digits of the MAC address that is now responding to the ping command are 00-0b-cd. According to the attached file MAC_Address_List.pdf, this is a Compaq device of some kind, not a Canon device. After searching the customer location, it was determined that a Compaq Desktop PC was using the same IP address as the Canon device.

**Pierre-69** · 12-09-2019

I tried everything... I thought about new MAC address in the network card after f/w update ( conflict with the arp cache), and thus, I changed IP address, but ping from the copier failed.
The copier detect the cable link, but nothing else. Get IP from DHCP server failed, new IP failed ... unable to communicate with the network.
I think the problem is inside the copier ( internal conflict between network config files after the f/w update )

**alex@wocltd.com** · 12-09-2019

can you confirm f/w version you updated to? - when it happened at my place had to get main controller in both instances

**giogi** · 12-09-2019

Initialize all parameters and reset. try LOOP BACK with ping command 127.0.0.1

**copier tech** · 12-09-2019

Originally Posted by Pierre-69

Hello,
After Firmware update on IR C5235, I'm unable to connect to the network.
At boot, I get "starting IP network ..." and "Verify TCP/IP". Everything was verfied and with the initial IP address (before update), I get "IP conflict" writen on the display ( There is no conflict with this IP on the network, may be only inside the copier ).
I tried with DHCP, but nothing is working...
The firmware update seems to be good in the logs, but the network is dead....
Anybody can help me about this problem please ?
Is it possible to restore the old firmware from HDD ?
Thanks,

What firmware version were you on before AND after the update?

It is possible to downgrade the firmware using service mode which can cause issues.

Leave the machine on DHCP & Auto IP while testing if you have an IP conflict most likely a cell phone/laptop has picked up your copiers IP.

**Copylady72** · 12-10-2019

Originally Posted by Pierre-69

I tried everything... I thought about new MAC address in the network card after f/w update ( conflict with the arp cache), and thus, I changed IP address, but ping from the copier failed.
The copier detect the cable link, but nothing else. Get IP from DHCP server failed, new IP failed ... unable to communicate with the network.
I think the problem is inside the copier ( internal conflict between network config files after the f/w update )

Did you disconnect the cable from the printer and try to ping the original IP from a pc or laptop that is on the network? If it replies with the printer not connected, there is a conflict. The dhcp lease usually lasts 24 hours. Is it possible another device grabbed it while updating and rebooting?

If you are 100% that there is no conflict, I would do an MMI clear in service mode.

Sent from my SM-N950U using Tapatalk