Canon MP600R WiFi Network Scan/Print Failure

Question

Level 1

10 points

Canon MP600R WiFi Network Scan/Print Failure

Hi there

My setup:

* a Canon MP600R multifunctional printer/scanner
* an Apple iMac running Snow Leopard
* a Dell Laptop running Windows Vista, and
* a Netgear WGT624v3 wireless router.

The printer and the two computers are all wirelessly connected to the router - there are no USB cables or wired LAN connections being used between these machines. All the machines have statically configured IP addresses (printer included).

I can print and scan reliably from/to the Windows laptop. Printing from the Mac used to work reliably, but scanning to/from the iMac only worked once in a blue moon.

To try to fix this, I updated the drivers on the Mac to the latest versions for Mac OS X 10.6 (Snow Leopard), and now I can't print or scan at all. The software I've been using is:

From Canon Europe:
* mp600rosxcp102620ea8-2.dmg - CUPS Printer Driver for OSX (10.26.2)
* mp600rosxns10ea7-3.dmg - MP Drivers for Network (Snow Leopard) (1.00)
* mp600rosxsd12131ej7.dmg - ScanGear CS for OS X (12.13.1)
* mpnosx304ej7.dmg - MP Navigator- MP Navigator for Mac OS X (3.04)
From Apple:
* CanonPrinterDrivers2.3.dmg - Apple's Canon Printer Drivers ( http://support.apple.com/kb/DL899)
From Canon Australia:
* ntosxm270ea8-2.dmg - IJ Network Tool Ver. 2.7.0

After many delete/reinstall steps on the Mac (following PAHU's advice!) and much Googling - including disabling/enabling firewall settings, IPv6 settings and even various router RIP settings - I could do with some help please!
__

What appears to be happening is that the Mac can't 'see' the printer, whereas the PC can - the drivers all seem to be installed in a similar way, and once set up (using the one-off USB connection step that the installers seem to like) they all have the right MAC address info. However the Mac Network Scan Utility shows a warning next to the printer's MAC address, whereas the PC is happy. Likewise, the PC's printer utilities can tell me about ink levels, the Mac's one gives me a communication error and puts the printer into paused mode.

This leads me to believe it was something going on on the network. I can, however, ping the printer from the Mac and access it's web configuration interface - so it's not that the printer's unreachable from the Mac.

To try to see what was going on in a bit more detail, I installed Wireshark and did some captures of the use of the Network Tool and Scan Utility.

On the PC (192.168.0.4), which works, it appears to direct the BJNP discovery commands direct to the printers IP address (192.168.0.2).
On the Mac (192.168.0.5), which fails, it appears to be broadcasting BJNP discovery messages to the subnet (192.168.0.255) and receiving ICMP Parameter problem responses from the printer.

So, is this likely to be:
A. the Canon drivers on the Mac
B. the Netgear router doing something to stop the broadcast discovery, or
C. something in the printer firmware?

If so, any ideas how to workaround it - for example, can I 'force' the Mac version of the drivers to not do broadcast discovery and simply go direct to the IP address like the PC?

Any help, pointers, gratefully received!

Mac OS X (10.6.4)

Posted on Sep 12, 2010 4:07 AM

Reply

Answer 1

Best reply

PAHU

Level 6

16,705 points

Sep 12, 2010 6:40 PM in response to andy.wood

I think that the results you are seeing with the Wireshark packet capture are more an indication of how the Windows driver works vs the Mac driver.

To add the MP600R network printer the Canon tool included with the Windows driver does a subnet broadcast to locate the printer. Once find it then creates a direct IP-based connection from the computer to the printer.

With the Mac, you select the Default Add Printer browser view and then wait for the MP600R to appear. Usually the scanner component appears very quickly, shown as a Bonjour Scanner in the Kind column. And if you wait several more seconds the printer component will also appear, with the Kind column showing 'canonijnetwork'. The Canon protocol uses multicast to advertise the printer on the subnet, hence the result you saw. But once the printer is added then like Windows, the communication is direct IP.

So regarding your questions as to a likely culprit I suggest that:
A. the Canon drivers on the Mac - 70% chance
B. the Netgear router doing something to stop the broadcast discovery - 30% chance
C. something in the printer firmware - 0% chance

The reason I believe that A is most likely the cause is that you mention that you have installed multiple drivers. For Mac OS X 10.6.4, the Canon driver for the MP600R is already included with the OS and will be a version 10.26.0, the same that you downloaded from Canon. Running the Apple / Canon v2.3 update would have updated the v10.26 driver to v10.30.3.0. But if you installed any Canon downloaded driver after running this update then there could be a bad mix of driver versions on the Mac. Personally I would trash the contents of the BJPrinters folder located in HD > Library > Printers > Canon and then empty the Trash and restart the Mac. I would then run the CanonPrinterDrivers2.3.dmg installer again and leave it at that for now. Then add the printer, selecting the Default browser view and wait. The scanner should appear first and then seconds later the printer should also appear.

If neither the printer nor scanner appear then B. could the cause. In the past I performed a packet sniff on a local subnet for a Canon wireless network device and one Mac running OS X 10.5.8 with an Airport wireless router as the access point.

Typical packets being sent and received included:
- Canon BJNP Discover, port 8611
- Canon BJNP Get Printer Identity, port 8611
- Canon BJNP Print Job Details, port 8611
- Canon BJNP Get Printer Status, port 8611

This data is generated when the printer status monitor is first opened or generating print jobs. The data is also generated when the printer is interrogated for error information and ink level indication.

The network scanning function and IJ Network Tool also generated the following types of packets:

- Canon BJNP Discover, port 8612
- Canon BJNP Get Printer Identity, port 8612

These packets will be generated every 5-20 seconds and are necessary for the Push Scan functionality when using the IJ Network Tool. The IJ Network Tool needs to actively poll the Canon AIO to detect button presses on the Control Panel.

If the NetGear is blocking these non-standard ports then this would stop the Mac from seeing the MP600R on the network. I would connect to the Netgear's internal web page and see if you can disable all port filtering/firewalls as a test.

With regards to C not being a cause, if the firmware was a cause then I would expect Windows to fail also. Since Windows is working fine then I would say that the firmware is not the cause.

Hope this helps and reply if needed.

Pahu

Reply

Answer 2

andy.wood Author

Level 1

10 points

Sep 13, 2010 8:01 AM in response to PAHU

Hi PAHU

Thank you very much for responding - particularly with such detailed and reasoned advice!

I have just tried deleting the BJPrinter folder, restarting and reinstalling only the Apple Canon Printer Drivers 2.3. On opening Print & Fax -> Add Printer I don't see anything in the window (no Bonjour Scanner or canonijnetwork) - I have left it open for more than 20 minutes now and still nothing. 😟

Using wireshark, I can see the Canon BJNP Discover packets to both 8611 and 8612 (and some mdns and db-lsp-disc packets). I can see the printer responding with error responses too:

45620 12463.295007 192.168.0.5 192.168.0.255 canon-bjnp1 BJNP Printer Command: Discover
ffffffffffff001d4ff85a7a08004500002c9b21000040115d 4bc0a80005c0a800ffdd9521a30018ec93424a4e5001010000 0001000000000000
45621 12463.295093 192.168.0.5 224.0.0.1 canon-bjnp1 BJNP Printer Command: Discover
01005e000001001d4ff85a7a08004500002c332f00000111e5 e3c0a80005e0000001dd9521a30018ce39424a4e5001010000 0001000000000000
45622 12463.415604 192.168.0.2 192.168.0.5 ICMP Parameter problem (Pointer indicates the error)
001d4ff85a7a000085847dde080045000024b3c70000400145 bac0a80002c0a800050c00f3ff000000000000000000000000
45623 12463.416790 192.168.0.2 192.168.0.5 ICMP Parameter problem (Pointer indicates the error)
001d4ff85a7a000085847dde080045000024b3c80000400145 b9c0a80002c0a800050c00f3ff000000000000000000000000

This pattern repeats every 8 seconds or so for the scanner and roughly every 25s for the printer port.
__

This extract (while typical of what's happening now) was actually taken from a lengthy capture I made yesterday which shows that, after quite a long period of time, it suddenly starting to work. This fits with my previous experience of seeing it 'coming and going' very intermittently (e.g. when leaving Add Printers open for an hour or more). When it started working it looked like this:

45637 12488.297178 192.168.0.5 192.168.0.255 canon-bjnp1 BJNP Printer Command: Discover
ffffffffffff001d4ff85a7a08004500002ce8240000401110 48c0a80005c0a800ffc1d021a300180859424a4e5001010000 0001000000000000
45638 12488.297260 192.168.0.5 224.0.0.1 canon-bjnp1 BJNP Printer Command: Discover
01005e000001001d4ff85a7a08004500002cc6670000011152 abc0a80005e0000001c1d021a30018e9fe424a4e5001010000 0001000000000000
45639 12488.307919 192.168.0.2 192.168.0.5 49616 BJNP Printer Response: Discover
001d4ff85a7a000085847dde08004500003cb3cb0000401145 8ec0a80002c0a8000521a3c1d00028b712424a4e5081010000 0001000000000010000108000604000085847ddec0a80002
45640 12488.308037 192.168.0.2 192.168.0.5 49616 BJNP Printer Response: Discover
001d4ff85a7a000085847dde08004500003cb3cc0000401145 8dc0a80002c0a8000521a3c1d00028b712424a4e5081010000 0001000000000010000108000604000085847ddec0a80002

The only thing I could see different between the discovery packets were the id and the source port - so I'm really puzzled as to what could be going on here!

Do you have any ideas? And does this change your percentage probabilities at all?!
__

(BTW the only traffic seen on the Mac between it failing and it working is:

45624 12463.739808 192.168.0.5 17.72.255.11 ntp NTP NTP client
45625 12463.774362 17.72.255.11 192.168.0.5 ntp NTP NTP server
45626 12478.606981 192.168.0.5 255.255.255.255 db-lsp-disc DB-LSP-DISC Dropbox LAN sync Discovery Protocol
45627 12478.607356 192.168.0.5 192.168.0.255 db-lsp-disc DB-LSP-DISC Dropbox LAN sync Discovery Protocol
45628 12478.668319 192.168.0.2 192.168.0.5 ICMP Parameter problem (Pointer indicates the error)
45629 12478.669571 192.168.0.2 192.168.0.5 ICMP Parameter problem (Pointer indicates the error)
45630 12480.098770 192.168.0.1 192.168.0.255 router RIPv2 Response
45631 12481.432048 192.168.0.5 192.168.0.255 netbios-ns NBNS Name query NB WORKGROUP<1d>
45632 12481.702507 192.168.0.5 192.168.0.255 netbios-ns NBNS Name query NB WORKGROUP<1d>
45633 12481.972805 192.168.0.5 192.168.0.255 netbios-ns NBNS Name query NB WORKGROUP<1d>
45634 12483.890302 192.168.0.5 192.168.0.255 netbios-ns NBNS Name query NB <01><02> _MSBROWSE_<02><01>
45635 12484.160651 192.168.0.5 192.168.0.255 netbios-ns NBNS Name query NB <01><02> _MSBROWSE_<02><01>
45636 12484.430912 192.168.0.5 192.168.0.255 netbios-ns NBNS Name query NB <01><02> _MSBROWSE_<02><01>
)

Reply

Answer 3

PAHU

Level 6

16,705 points

Sep 13, 2010 9:08 PM in response to andy.wood

Thanks for the new logs. It certainly does show that there is a response issue from the printer (.2). As to why it would start working again at some point and then stop again is tricky.

I am not sure if the MP600R supports this but with my MP980 & MP990 I can enter the IP address into a web browser and view the network settings for the printer. If you select to add the printer again, and if either the scanner or printer fail to appear in the Default Add Printer view, try connecting to the internal web page of the printer to see if the printer is alive. And if you do get some sort of web view, go back to the Add Printer to see if the MP600R has appeared.

Can you also ensure that your firewall is off for this testing and any other application that has blocking capabilities (such as Intego's Virus Barrier).

Reply

Answer 4

andy.wood Author

Level 1

10 points

Sep 14, 2010 12:54 AM in response to PAHU

Hi PAHU

Thanks again for the good advice.

I've switched off my Mac firewall and checked that I can see the printer's web configuration interface (which is available very quickly after switching it on). Still no luck with Add Printers. 😟
__

However, I realised that the PC would be receiving the Mac's broadcast discovery packets and decided to sniff them there - with some very interesting results:

Mac TX

431 142.095345 192.168.0.5 192.168.0.255 canon-bjnp1 BJNP Printer Command: Discover
ffffffffffff001d4ff85a7a08004500002c176600004011e106c0a80005c0a800ffdf2921a30018 eb00424a4e50010100000000000000000000
432 142.095502 192.168.0.5 224.0.0.1 canon-bjnp1 BJNP Printer Command: Discover
01005e000001001d4ff85a7a08004500002c5b1e00000111bdf4c0a80005e0000001c2cf21a30018 e900424a4e50010100000000000000000000
433 142.125723 192.168.0.5 224.0.0.251 mdns MDNS Standard query PTR canon-bjnp1.tcp.local, "QM" question
01005e0000fb001d4ff85a7a080045000045ed000000ff112cfec0a80005e00000fb14e914e90031 3fb30000000000010000000000000c5f63616e6f6e2d626a6e7031045f746370056c6f63616c0000 0c0001
434 143.127275 192.168.0.5 224.0.0.251 mdns MDNS Standard query PTR canon-bjnp1.tcp.local, "QM" question
01005e0000fb001d4ff85a7a080045000045fb5c0000ff111ea2c0a80005e00000fb14e914e90031 3fb30000000000010000000000000c5f63616e6f6e2d626a6e7031045f746370056c6f63616c0000 0c0001
435 145.264621 192.168.0.5 192.168.0.255 canon-bjnp2 BJNP Scanner Command: Discover
ffffffffffff001d4ff85a7a08004500002c236700004011d505c0a80005c0a800fff13a21a40018 d7ee424a4e50020100000000000000000000
436 145.264772 192.168.0.5 224.0.0.1 canon-bjnp2 BJNP Scanner Command: Discover
01005e000001001d4ff85a7a08004500002c791200000111a000c0a80005e0000001ede121a40018 bced424a4e50020100000000000000000000
437 145.372415 192.168.0.2 192.168.0.5 ICMP Parameter problem (Pointer indicates the error)
001d4ff85a7a000085847dde080045000024a1b70000400157cac0a80002c0a800050c00f3ff0000 00000000000000000000
438 145.373129 192.168.0.2 192.168.0.5 ICMP Parameter problem (Pointer indicates the error)
001d4ff85a7a000085847dde080045000024a1b80000400157c9c0a80002c0a800050c00f3ff0000 00000000000000000000

But the PC received:

2 1.951770 AppleCom_f8:5a:7a Broadcast IP Bogus IP header length (0, must be at least 20)
ffffffffffff001d4ff85a7a0800000000000000000000110018c0a80005c0a800ffdf2921a30018 0000424a4e50010100000000000000000000
3 1.952808 AppleCom_f8:5a:7a IPv4mcast_00:00:01 IP Bogus IP header length (0, must be at least 20)
01005e000001001d4ff85a7a0800000000000000000000110018c0a80005e0000001c2cf21a30018 0000424a4e50010100000000000000000000
4 1.954155 192.168.0.5 224.0.0.251 mdns MDNS Standard query PTR canon-bjnp1.tcp.local, "QM" question
01005e0000fb001d4ff85a7a080045000045ed000000ff112cfec0a80005e00000fb14e914e90031 3fb30000000000010000000000000c5f63616e6f6e2d626a6e7031045f746370056c6f63616c0000 0c0001
5 2.969728 192.168.0.5 224.0.0.251 mdns MDNS Standard query PTR canon-bjnp1.tcp.local, "QM" question
01005e0000fb001d4ff85a7a080045000045fb5c0000ff111ea2c0a80005e00000fb14e914e90031 3fb30000000000010000000000000c5f63616e6f6e2d626a6e7031045f746370056c6f63616c0000 0c0001
6 5.119995 AppleCom_f8:5a:7a Broadcast IP Bogus IP header length (0, must be at least 20)
ffffffffffff001d4ff85a7a0800000000000000000000110018c0a80005c0a800fff13a21a40018 0000424a4e50020100000000000000000000
7 5.121002 AppleCom_f8:5a:7a IPv4mcast_00:00:01 IP Bogus IP header length (0, must be at least 20)
01005e000001001d4ff85a7a0800000000000000000000110018c0a80005e0000001ede121a40018 0000424a4e50020100000000000000000000

So, it looks to me like the PC is seeing the same thing that the printer is complaining about: something (presumably the router?) is zeroing an important section of the broadcast packets.

(Interestingly, the Bonjour packets go through fine.)

Does that rather squarely point the finger at the router as the cause of the problem? Any idea what bit of functionality/setting might do that?!

Reply

Answer 5

PAHU

Level 6

16,705 points

Sep 14, 2010 2:15 AM in response to andy.wood

Looking at the packets received at the PC it does appear that the bjnp1 packets are being 'filtered' by the router, although looking at the packet data received it appears to be the same content.

I also looks like the Bonjour packets are being impacted if you look at what the PC is receiving (refer to the bjnp2 discover).

Comparing your results to a new sniff I did this arvo, I think the two ICMP problems are meant to be UDP transmissions from the Canon to the Mac which are coming from port 8612. But looking at the packet sizes for your entries they appear to be the same size as I get so I am not sure why Wireshark indicates a problem. I will do some more testing and get back to you. In the meantime I suggest you check the settings in the Netgear. Things like MAC address filtering or port filtering are the key names to look for.

To be continued...

Reply

Answer 6

PAHU

Level 6

16,705 points

Sep 15, 2010 1:35 AM in response to PAHU

Spent some time looking at your captures and comparing to mine. It does look like the packet showing the ICMP Parameter problem is either being incorrectly sent by the MP600R or being modified between the printer and the Mac.

For example, the response you get to the "canon-bjnp2 BJNP Scanner Command: Discover" is;

192.168.0.2 192.168.0.5 ICMP Parameter problem (Pointer indicates the error)
001d4ff85a7a000085847dde080045000024a1b70000400157cac0a80002c0a800050c00f3ff0000 00000000000000000000

In comparison, the response I get to the same "canon-bjnp2 BJNP Scanner Command: Discover" is;

00236c980a76000085ec966008004500002c6c51000040117cef646464556464646321a4e04b0018 d8af424a4e50810282000000000000000000

This shows that my Mac (00236c980a76) receives a response from my MP980 (000085ec9660) with a payload of (424a4e50) which is BJNP in ASCII. This is sent from port 8612 on the Canon to 49756 on the Mac.

Your payload shown above does not mention the BJNP protocol. But the other post where you did get a response did show the BJNP protocol in the payload.

So I don't know why this is happening but my suggestion would be to remove the Netgear from the path and test again. Ad-hoc mode, where the printer connects directly to the Mac is not officially supported by Canon but does work when you enable Internet Sharing on the Mac. So you could try a connection this way or you could get an Ethernet cable and connect directly from the Mac to the printer and manually set an IP address for both devices. You could then capture the printer and scanner discovery and compare.

The whole point of this would be to prove the MP600R is sending out the packets correctly and that it is the router that is altering the packet. Given Windows works fine with the printer would suggest that the printer is okay, but would also suggest the router is okay. So that leaves the Mac and as to why it would alter an incoming packet is beyond me.

Good luck with the testing and let me know how it all goes.

Pahu

Reply

Answer 7

andy.wood Author

Level 1

10 points

Sep 15, 2010 1:51 AM in response to PAHU

Hi Pahu

Thank you very very much for looking into this.

I have now come to the conclusion it's the Netgear WGT624v3 corrupting the broadcast packets. I tried a reverse of the above (watching the PCs packets on both the PC and the Mac) and can see it doing the same thing with those.

PC transmit:

1 0.000000 192.168.0.4 255.255.255.255 canon-bjnp1 BJNP Printer Command: Discover
ffffffffffff001dd93dbf4d08004500002c018700008011788ec0a80004ffffffffe07a21a30018 ab3e424a4e5001010000001a000000000000
2 0.000159 192.168.0.4 255.255.255.255 canon-bjnp1 BJNP Printer Command: Discover
ffffffffffff001dd93dbf4d08004500002c018800008011788dc0a80004ffffffffe07a21a30018 ab3e424a4e5001010000001a000000000000
3 0.081377 192.168.0.2 192.168.0.4 ICMP Parameter problem (Pointer indicates the error)
001dd93dbf4d000085847dde080045000024a7e800004001519ac0a80002c0a800040c00f3ff0000 00000000000000000000
4 0.082374 192.168.0.2 192.168.0.4 ICMP Parameter problem (Pointer indicates the error)
001dd93dbf4d000085847dde080045000024a7e9000040015199c0a80002c0a800040c00f3ff0000 00000000000000000000

Mac received:

1 0.000000 HonHaiPr_3d:bf:4d Broadcast IP Bogus IP header length (0, must be at least 20)
ffffffffffff001dd93dbf4d0800000000000000000000110018c0a80004ffffffffe07a21a30018 0000424a4e5001010000001a000000000000
2 0.001585 HonHaiPr_3d:bf:4d Broadcast IP Bogus IP header length (0, must be at least 20)
ffffffffffff001dd93dbf4d0800000000000000000000110018c0a80004ffffffffe07a21a30018 0000424a4e5001010000001a000000000000

I think it works on the PC because it ignores the failed broadcast and just goes on to send the commands direct to the printer's IP. This is possibly because the PC drivers are a different version (older - drivers 2.0.0/tools 2.5.0).

The other thing that makes me believe it is the router is that appears to be that other broadcast packets are affected - for example, this netbios one.

PC sent:

1 0.000000 192.168.0.4 192.168.0.255 netbios-ns NBNS Name query NB WPAD<00>
ffffffffffff001dd93dbf4d08004500004e012a00008011b721c0a80004c0a800ff00890089003a 72f7c7ae011000010000000000002046484641454245454341434143414341434143414341434143 414341434141410000200001

Mac received:

1 0.000000 HonHaiPr_3d:bf:4d Broadcast IP Bogus IP header length (0, must be at least 20)
ffffffffffff001dd93dbf4d080000000000000000000011003ac0a80004c0a800ff00890089003a 0000c7ae011000010000000000002046484641454245454341434143414341434143414341434143 414341434141410000200001

Again it looks like the IP header section (starting 28th octet in) is being zeroed, and the printer is sending out ICMP errors because of this - interestingly it does this in response to the corrupt netbios packets too!

I therefore am certain that there's something wrong with my router - but having switched pretty much every setting on it off and on, changed ip address ranges and subnets - I can't get it to work. 😟
__

I'll give it a go with a crossover cable as you suggested, and I will let you know - I think it's very likely to succeed!

So again, thank you very much for spending time looking into this - it's very much appreciated.

You deserve to be recognised by Canon and Apple for providing such patient and thorough customer service!!!

Reply

Answer 8

Sep 15, 2010 2:41 PM in response to andy.wood

I had a similar problem with a BT Home Hub and a Brother printer. The only way I could get a reliable connection via WiFi was:
System Preferences
Print and Fax
Add a Printer
Click the IP tab
Enter the printer's IP address
In the Print using dropdown choose your installed printer

That worked for me

Reply

Answer 9

andy.wood Author

Level 1

10 points

Sep 21, 2010 8:59 AM in response to PAHU

Hi Pahu

Just to say, I connected the Mac and Printer directly using a crossover cable and manually configured IP addresses - and it works.

Needless to say, I'll be replacing the Netgear router as it is definitely at fault.

The scanner still doesn't appear as a Bonjour scanner - but I think that may be because this model doesn't support that feature. However, the network scan, from printer console and MP Navigator, are now both working perfectly.

Many thanks for your suggestion and all your help!

Reply