Forum Discussion

Former Member's avatar
Former Member
6 years ago
Solved

Logmein Antivirus firewall blocking network printing

Has anyone else run into this and is there a way to resolve?

We use IP based printing and after installing Logmein Antivirus (with firewall enabled in the policy), we've experienced issues with printing. Jobs get stuck in the spooler and sometimes the printer shows offline in Windows devices. We've worked around this for now by turning Logmein firewall off and enabling Windows firewall. There are not a ton of options in the policy creator. It would be nice to be able to add firewall exceptions if needed.

  • I had a problem with network printers also. It was only some of the locations we manage, not all.

    To get ours to work, I tried some things: editing group policy AD (for domain computers) and local GP for non-domain. I added firewall rules into there for the IP ranges needed and ports etc.

     

    I also realised the machines failing were on network connections set as "Public". I used a powershell script and the LMI One2Many feature to change all the network connections to "Private". This was only on the machines not on the AD domain. Luckily in our case, we name all the network adapters on machines the same "Broadband" because we have 2 network cards in use and need to differenciate.

     

    Set-NetConnectionProfile -InterfaceAlias Broadband -NetworkCategory Private
    Set-NetConnectionProfile -InterfaceAlias OtherNetwork -NetworkCategory Private

     

    After making these changes, it's all fine.

    Not sure if the Windows Firewall Group Policy rules are having any effect though as LMI seems to manage to firewall. I could easily test by blocking something on GP and see if it takes effect.

29 Replies

  • TwilightZone's avatar
    TwilightZone
    Active Contributor
    5 years ago

    I had a problem with network printers also. It was only some of the locations we manage, not all.

    To get ours to work, I tried some things: editing group policy AD (for domain computers) and local GP for non-domain. I added firewall rules into there for the IP ranges needed and ports etc.

     

    I also realised the machines failing were on network connections set as "Public". I used a powershell script and the LMI One2Many feature to change all the network connections to "Private". This was only on the machines not on the AD domain. Luckily in our case, we name all the network adapters on machines the same "Broadband" because we have 2 network cards in use and need to differenciate.

     

    Set-NetConnectionProfile -InterfaceAlias Broadband -NetworkCategory Private
    Set-NetConnectionProfile -InterfaceAlias OtherNetwork -NetworkCategory Private

     

    After making these changes, it's all fine.

    Not sure if the Windows Firewall Group Policy rules are having any effect though as LMI seems to manage to firewall. I could easily test by blocking something on GP and see if it takes effect.

  • jayce007's avatar
    jayce007
    New Contributor
    5 years ago
    That's not an acceptable answer. Disabling the software is the only solutions? Is LogMeIn looking into this?
  • AshC's avatar
    AshC
    Retired GoTo Contributor
    5 years ago

    Hi everyone,

    I am sorry this is affecting your regular work flows, and the only workaround for now is to disable the LogMeIn Firewall there.  Network printers (connects back on a different port) are not compatible with LMI AV Firewall and you should switch using the Windows Firewall if network printing functionality is needed.

     

  • jimboelter's avatar
    jimboelter
    Active Contributor
    5 years ago
    Come on LogMeIn support, help us customers out!!!!
  • Oscarkim's avatar
    Oscarkim
    New Contributor
    5 years ago

    Experiencing the same issue.  Halting rollout of LMI AV in our organization until this is resolved.

  • Same issue.

    Disable firewall, printer works. Enabled it does not.

     

    I can see a solution for BEST but not for LogMeIn version. 

  • alobdell's avatar
    alobdell
    Active Contributor
    6 years ago

    I have had the same issue!!! Come on LogMeIn can we get some help with this feature.

     

    Adam

  • We are experiencing the same issue and have not been able to find a solution so far other than turning off firewall.