TR8520 - cant find on the network

[emsantil2]

Tried looking through the community but cant find a solution. My printer suddenly can't communicate with the network. I noticed it as i tried to print and jobs sat in the que. Worked neither through my PC or smartphone. It's connected to my router which i can see on the printer screen and as a connected device when i check through my router. I've tried all solutions posted.

1. cycling router/printer on off (specifically turning printer off, unplugging router for several minutes, plugging back in and powering printer back on
2. I tried resetting to factory and reconnecting to the router. Successfully connected, but still no communication. 
3. I deleted all drivers. When I try to reinstall, the printer can't be found on the network (auto or manual search)
4. I disabled firewall
5. ensured frequency was 2.4GHz

Nothing I try seems to be working. Any suggestions?

[Stephen]

Hello there!

Welcome to the Canon Community!

Try the automatic setup software at https://canon.us/TR8520Setup 

It should automatically uninstall Canon drivers and software on your computer, install the most up-to-date drivers and software, and pair your printer with your WiFi network. 

Once you've done that, let us know how it goes.

If you need one-on-one, live assistance, visit https://canon.us/account to determine your support entitlements. 

[emsantil2]

Hi,

This did not work. I am stuck on step 2. The printer is still not detected on the network, despite being connected to the wireless router. 

[Patrick]

Hi emsantil2,

With your PIXMA TR8520 on, please tap the Wi-Fi icon in the lower left corner of your TR8520's display.

If a password message appears, tap Yes.

On the next screen, is the name listed to the right of SSID the same name that your PC is connected to ?

Please scroll down the list, is the number listed next to Signal Strength greater than 50% ?

Lastly, write down the numbers next to IPv4 address.

Next, we will check the conenction:

1.  On your computer, please press the Windows key on your keyboard and the letter R, then let both go.

2.  In the Run window that appears, please type CMD and click OK.

3.  In the Command Prompt window that appears, please type:

PING xxx.xxx.xxx  <--where those x's are the number that you wrote down from above.  For example: PING 192.168.1.33

4.  Then press the Enter key on your keyboard.

Results will appear.  In those results, do you see "Timed Out" ?  "Destination host unreachable" ? or "Sent = 4, Received = 4, Lost = 0" ?

Did this answer your question? If so, please click the Accept as Solution button below so that others may find the answer as well.

[emsantil2]

Hi, yes, greater than 50%. I tried the command prompt. The result is "destination history is unreachable"

[Patrick]

Hi emsantil2,

To keep each device unique, the router will assign each device an IP address.

The device and it's IP address are saved in the router in what is called a "routing table".

"Destination host unreachable" means that the router knows there is a device connected with that IP address, but does not know how to send data to it.

This is caused by an issue with the routing table not being updated on the router.

Typically, turning off the printer, unplugging the router, reconnecting the router and turning the printer back on resolves this issue, as the routing table will refresh.

Please turn your PIXMA TR8520 off.

Next, please go to your router and unplug the power cord from the back of your router.

Wait 1-2 minutes and then reconnect the power cord to your router.

Once back online, please turn your printer back on.

When ready, please follow the steps I provided in my last post to determine the IP address of your printer (it may have changed) and then perform the PING command on your computer using that IP address.

If "Timed Out" and "Destination Host Unreachable" do not appear, please attempt to print.

Did this answer your question? If so, please click the Accept as Solution button below so that others may find the answer as well.

[emsantil2]

Hi Patrick,

I tried this solution previously as I have seen it recommended on other replies. The host was still unreachable. I'll try it again, but what would be the next step if that fails?