cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
Valued Advisor
Valued Advisor

Re: WC 7830, Air Print, printing from iPhones issue

Airprint and MOPRIA are essential the same thing (Airprint is made by Apple, MOPRIA is made by printer companies), yet in this case 1 works and the other doesn't.

But MOPRIA will still work if you enable it and then disable mDNS later, while Airprint will not.

 

In this case, they are absolutely able to communicate as they can view CWIS via Safari on the iDevices.

 

The issue in this case (The top post) is almost certainly mDNS being blocked at the router level.

 

But the OP never came back to say if the issue got resolved or not.

Please be sure to select "Accept Solution" and or select the thumbs up icon to enter Kudos for posts that resolve your issues. Your feedback counts!

Joe Arseneau
0 Kudos
Highlighted
Valued Member
Valued Member

Re: WC 7830, Air Print, printing from iPhones issue

Hi! OP here!....

 

I think Joe is on the right track...we went there and disconnected the copier from the network jack, plugged in a switch, then plugged in the copier to the switch along with my laptop running kali Linux for wireshark...captured about 10 min worth of data and then analyzed...during that time I was trying to print from the iPhone and it wouldn't even pop up...had the client then go to a desktop and print, I noted the ip address...then looked in Wireshark for the ip address of the copier...nothing...then looked up the client ip address and saw it used mdns but the ip was a totally different ip on the copier side ...their ip scheme is 192.168.169.xxx and on wireshark said 255.0.0.0

That being said it definitely seems like the router is the problem but I have no way to really prove it because the HPs and brothers are being seen...only the xerox isnt

0 Kudos
Highlighted
Valued Advisor
Valued Advisor

Re: WC 7830, Air Print, printing from iPhones issue

From the Wireshark documentation:

 

An IPv4  network  number  can  be  written  as a dotted quad
(e.g.,192.168.1.0), dotted triple (e.g., 192.168.1),
dotted pair (e.g,172.16),   or   single   number   (e.g.,  10);
 the  netmask  is 255.255.255.255 for a dotted quad (which means that it's  really
a  host  match),  255.255.255.0 for a dotted triple, 255.255.0.0
for a dotted pair, or 255.0.0.0 for a single  number

 

 

So 255.0.0.0 isn't incorrect.

Please be sure to select "Accept Solution" and or select the thumbs up icon to enter Kudos for posts that resolve your issues. Your feedback counts!

Joe Arseneau
0 Kudos