Problems with HP printers

[GaborO]

Please note that we've found the reason of network printing being blocked by the LogMeIn AV Firewall.

We will add an option to the AV policy to enable network printing early next year.

[timau]

Any updates on this.. (It not just HP printers it most bands of printers) 

Also not just on Wifi Public networks also on Private and domain networks.

[bswedhin]

When I run the command Get-NetConnectionProfile it shows the NetworkCategory = DomainAuthenticated and the  DomainAuthenticationKind = Ldap. 

If I try to run the commnand 

Set-NetConnectionProfile -InterfaceAlias Wi-Fi -NetworkCategory Private

I get errors because it is a computer that is joined to our domain. So this does not resolve our issues.

Several users still can not print while on Wi-Fi, they get print errors. We have done everything possible to fix this. from removing drivers to checking subnets to accessing the printers web UI. Some people can print to the printer, so We know it is not a problem with the printer.  (we only started having these problems after we installed the LMI suite)

Please help resolve this asap

Thank you

[DiegoDash]

In a little while we will be in 2025 and there is no solution, no update.

[KateG]

Hi @DiegoDash , @bswedhin , @timau , 

I've reached out to the team for an update, I don't have a timeline for a fix at the moment, but will keep this thread updated. Thanks for bumping this and for your patience. 

[timau]

The reply I've had from Logme Tech support is horrendous - they don't acknowledge the problem exists. instead they seem to think it has something to do with remote printing.

--
Hello,

I investigated this and the environment you provided with the printer is related to the article in question, to which the only solution we offer is what is stated in that article.

If you have any questions, please let me know!

Regards,

Sergio | Customer Care Manager
----
Hello,

Thanks for your response.

The nature of this case is related to remote printing - wireless printers, and that's the information that was provided to you.

On the other hand, if you need to know how the remote printing feature + how to troubleshoot any networking issue, also how the product works, you can check the following articles:
Remote Printing.
LogMeIn Pro and Firewalls.

If you have any further questions, please let me know!

Regards,

Sergio | Customer Care Manager

[bswedhin]

I'm supprised that there's no fix for this on going issue.  It is effecting Wi-Fi network printing not remote printing. The only symtom that the users has is "Print Error" after a couple minutes of sending the print job, and it stays in que. 

The only possible fixes we have found which are usually only temporary fixes are:

Format and reload the OS (seems like a waste of time)

Create a new IP port for the printer (sometimes works)

disconnect from Wi-Fi and reconnect (may or may not fix issue and is only temporary)

restart computer (do not shut down) (again may only fix temporary)

Delete printer and drivers then reinstall printer (again may only fix temporary) 

If anyone finds any other solutions, please let us know.

[timau]

(Ive told Logmein Support many many times its not remote printing and they keep saying it is - not sure how they cant understand that...)

The immediate ways to fix:

Set the network to private (that fixes a lot) but not 100% of the time and not permanent  it will still error depending on printer and drivers sometimes. We have the error on Ethernet connections also domain and private networks)

Creating a new Rule with Firewall disabled appears to fix it 100% of the time – in fact the printer will burst into life as soon as it applies.

[DiegoDash]

It doesn't make sense for us to disable Logmein's firewall for the printer to work. It's been an error for years and we don't have anything working providing data for this correction. Paying and not using the firewall is unacceptable. Does the board know about this?

[timau]

I agree disabling the firewall SHOULDN'T be the only option to print reliably!

Logme in must have know about this for a long time - yet they continue to sell it (We just purchased it) The Tech support saying its just a remote issue show the lack of what I can see being any care or responsibility.

For an integrated offering its actually very lacking in features that you would expect of any AV package. To then find out we must manually remove it on EACH computer is also unbelievable in this day and age.