Thread Info
  • State Suggested Answer
  • Locked Locked
  • Replies 14 replies
  • Answers 1 answer
  • Subscribers 15 subscribers
  • Views 5594 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Central kills Dymo Label Printers using AthenaNet device manager

Darth_Boss

Has anyone run into this before?  Sophos central is killing Dymo Label Printers using AthenaNet device manager.  None of our registration PCs have been able to print labels for almost 2 weeks now.  I have an open ticket but no resolution has been found yet.  Disabling the "Sophos Web Filter Service" allows the printers to work.  When the service is enabled no blocked website events are showing up on the client or on the Central console.  We were halfway through a conversion from Enterprise console to central and we are at a standstill until we get this resolved.  Can anyone help?  Thanks.  



This thread was automatically locked due to age.
  • 0 in reply to Darth_Boss

    Just tagging in, I have some Dyno Printers and want to follow up. 

    Respectfully, 

     

    Badrobot

     

  • 0 in reply to jak

    Jak, the OS is Windows 10.  You were right all along.  The loopback address 127.0.0.1 has to be in the threat protection policy.  I already had it tagged in the Global Settings, Website Management list, and applied to all the policies.  It was there from our conversion from Enterprise console.  However, this did not allow the device manager to run.  It specifically had to be in the threat protection policy.  Your help with this is greatly appreciated!  

    If anyone else encounters this, add 127.0.0.1 as a website exemption in whatever threat protection policies that are applied to the clients.

    Thank you Jak and everyone else who offered suggestions!

    Darth Boss

  • 0 in reply to Badrobot

    badrobot, the fix was to add 127.0.0.1 as a website exemption in whatever threat protection policies that are applied to the clients.  Just tagging it in the global settings, website management list and applying it to the policies doesn't work--it has to be in the threat protection policy as a website exemption.

     - Darth Boss 

Unfiltered HTML