Skip to main content
bshimkus
bshimkus
New Member
September 14, 2017
Solved

Losing connect to HP Laserjet MFP 425DN on wireless clients...

  • September 14, 2017
  • 1 reply
  • 14854 views

The environment is this:

 

FortiGate 60E (5.6.2)

FortiAP-224D (5.6)

HP LaserJet m425dn (running latest firmware)

Mac OSX 10.12.6

 

The printer is connected to the "internal" switch on the FortiGate.  The FortiAP is also connected and being managed via the FortiGate.  IPv4 policies are in place to allow all traffic to and from the wireless network to the internal switch.  No restrictions should be in place preventing any traffic from going to and from the subnets.

 

I have also created a multicast policy that allows Bonjour from internal to wireless and wireless to internal.

 

My Mac clients are losing connection to the printer shortly after connecting to it.  For example, if you use the HP Utility, you can discover and add the printer to the client, however when going to print, the client loses connection.  I don't have any Windows systems to test against at this time.

 

The printer responds to ping (and they could telnet) from wireless clients, but any attempt to print or scan results in losing connection to the printer.

 

I've looked through the FortiView logs and found that only ping, TCP/8080, TCP/8289, and SNMP_GetRequest are show as traffic between the client and the printer.

 

Any ideas?

 

bks

    Best answer by bshimkus

    bdouble wrote:

    I am having this exact same issue with a 60E and 221B AP, and an HP printer connected by ethernet to the internal interface. My firmware is 5.4.5. 

    I was able to "fix" the issue.  I ended up creating a software switch on the FortiGate-60E that contained the physical interface the printer was connected to and the SSID's on the FortiAP-224D.

     

    Presto!  It worked.  I was able to AirPrint from iPhone and an OSX 10.12.x client.  Extended features such as scanning worked as well from the MFP.

     

    I mess with multicast policies for a solid hour and then just gave up.  I really did like the idea of separate networks for 2.4Ghz, 5Ghz, and wired connections, but it did complicate things.  I would have loved to been able to brag to my network buddies that I figured it out, but I guess I'll have to wait another day. :)

     

    Even though I have FortiOS 5.6.2 on the FortiGate, these instructions still provided good guidance:

     

    http://cookbook.fortinet.com/combining-wifi-and-wired-networks-with-a-software-switch/

     

    I hope that helps!

     

    bks

     

     

     

    1 reply

    bshimkus
    bshimkusAuthor
    New Member
    September 14, 2017

    Did a cold reset on the printer, no change.

     

    Tried connecting directly to the FortiGate on an internal interface (same group of interfaces that the printer is on) and same issue.

     

    Off to open a ticket with Fortinet...

     

    bks

    bshimkus
    bshimkusAuthor
    New Member
    September 15, 2017

    If there are any Fortinet employees out there, the ticket is 2362207.

     

    bks

    bdouble
    bdouble
    New Member
    September 15, 2017

    I am having this exact same issue with a 60E and 221B AP, and an HP printer connected by ethernet to the internal interface. My firmware is 5.4.5. 

    Terms & ConditionsAccessibility statement