Skip to main content
craigbert
craigbert
New Member
January 5, 2020
Solved

Can't see device (printer) on other interface

  • January 5, 2020
  • 2 replies
  • 23455 views

Hello All,

 

I am a bit new to this level of networking, but I am trying to learn.

I have a printer on one interface that needs to be accessible from the other two.

My product is a FortiWiFi 60D, version 5.6.12.

My config is:

wan1 = connection between small office and internet

physical LAN = 10.10.79.X

wifi1 = device is located here 10.10.80.X

wifi2 = 10.10.180.X

wifi3 = 10.10.81.X (Guest)

I can ping the printer from LAN, wifi1, and wifi2, but it doesn't show up in AirPrint like it used to (prior to FortiWifi 60D being installed) which makes it difficult for the Apple products to connect to it and print.

In "Addresses" under "Policy & Objects" I have it defined as: "Canon Printer", subnet, 10.10.80.34/32, interface = "any", Show in Address List = enabled, Static Route Configuration disabled.

In IP4Policy the very first policy I have is:

Name: Printer #1 Policy

Incoming Interface: physical LAN, wifi1, and wifi2

Outgoing Interface: wifi1

Source: physical LAN, wifi1, and wifi2

Destination: "Canon Printer"

Schedule: Always

Service: ALL

Action: Accept

NAT = Enabled

IP Pool Config: Use Outgoing Interface Address

None of the Security Profiles are Enabled

Log Allowed Traffic: Enabled with "All Sessions"

Policy is Enabled.

 

Anyone have any idea what I am missing?  I have been messing around with this for a couple days and the hair loss is getting to be a bit much.

;)

Thanks.

 

 

    Best answer by Dave_Hall

    @craigbert

     

    Devices on wifi1 (10.10.80.X) should be able to communicate with the Canon Printer (10.10.80.34/32) directly unless you have blocked Intra-SSID Traffic. Devices on the other subnets (LAN, wifi2, wifi3) should have firewall polices configured to direct traffic to "wifi1/Canon Printer".  NAT is not needed unless the Canon Printer itself does not allow for non-subnet connections (and can not be configured for such). Check the routing monitor to make sure there is a route showing up for 10.10.80.X.

    As for airprint, see KB #FD33598 or KB#FD36500 for setting up multicast traffic.

     

    2 replies

    Toshi_Esumi
    SuperUser
    Toshi_Esumi
    SuperUser
    January 6, 2020

    Why do you need the NAT? That's likely the problem.

    craigbert
    craigbertAuthor
    New Member
    January 6, 2020

    Hi @Toshi, thanks for the reply.

     

    I would have thought so to, but without the NAT enabled neither the physical LAN nor the other wifi network can even ping the printer let alone connect to it.

    So it *seems* that enabling NAT gets me a little closer.  But to be fair maybe it only appears that way because I am missing something else.

    ShawnZA
    ShawnZA
    New Member
    January 6, 2020

    You need to disable NAT and make sure your routing is correct, you should be able to ping it if NAT is disabled unless there is a rule blocking it or no route to destination....

     

    AirPrint is based (partly) on Bonjour, which is essentially a service discovery protocol that operates within a single subnet

    So if your device is in another subnet it will likely not discover it automatically... there are other ways of getting that working correctly.

     

    But first get that NAT sorted on that rule, no need for NAT between internal networks.

    jonsmith
    jonsmith
    New Member
    January 30, 2020

    The same issue also happens to me. When I try to print using the HP Designjet T520 printer from my PC the interface didn't show the printer. Could be the computer can't able to find the printer IP address.

    Dave_Hall
    Dave_Hall
    New Member
    January 30, 2020

    Hi Jon.

     

    If you can ping the printer's IP address then I say the issue is simply a "discovery" issue - if we are talking about one or two printers - you probably just want to manually specific the IP address for the printer when setting it up (e.g configure a TCP/IP port).  Also if the printer's IP address should be accessible via web browser if ICMP packets are blocked.

     

    This thread was about getting devices on wifi to "discover" a lan printer, so 3 interfaces (subnets) are involved.  Are you having a similar issue? 

     

    jonsmith wrote:

    The same issue also happens to me. When I try to print using the HP Designjet T520 printer from my PC the interface didn't show the printer. Could be the computer can't able to find the printer IP address.

    sw2090
    SuperUser
    sw2090
    SuperUser
    June 23, 2020

    He wrote he wants to see the printer in airprint.

    Airprint bascially uses bonjour which is udp multicast.

    You will need to set up multicast policies to make airprint work.

     

     

    Terms & ConditionsAccessibility statement