Guest User!

You are not Sophos Staff.

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

SATC replacement - Server Endpoint

We had a customer put a case in yesterday about having the Server Endpoint Software configured to replace the failing SATC software. I advised I knew it was in the pipe but hadn't heard it had been released yet, and then he shared these two links:

Set up SATC with Sophos Server Protection

Sophos Firewall: SATC with Server Protection

I worked through it with him, and I'm happy to report it all worked a treat across multiple browsers and clients on his THIN Client. Just thought I'd give anyone a heads up who has been waiting and may have missed the announcement. 



This thread was automatically locked due to age.
Parents
  • has anyone experienced intermittent issues since deploying this?
    I've installed the Server Protection EAP, ran the powershell to migrate the SATC ini settings to the registry, installed the old SATC and rebooted, and all was working fine. 
    but intermittently users get (on chrome) a page to say 'the information you're about to submit is not secure' and clicking 'send anyway' loads up the Sophos window to entering credential to authenticate.

    Not too long after, it seems to fix itself.

    Thanks

  • Do you have "Show captive Portal to unknown user" in the firewall active? Try to disable this. 

    __________________________________________________________________________________________________________________

  • Hi, we do have that active. We have always had that active even with the old SATC. Would disabling this help with the issue / is it a known problem with the new SATC built into server protection EAP? Most of the time is does work fine, but intermittently it does stop working and then loads  'the information you're about to submit is not secure' chrome error. 

    cheers

  • I would recommend to disable this and check again. It looks like the captive Portal, which cannot work for this portal. 

    __________________________________________________________________________________________________________________

Reply Children
  • Just had a user report the issue and I disabled the captive portal and it instantly fixed it - looking promising! Thank you

  • I'm not sure it's quite that simple. What's probably happening is there is a short period of time before the authentication request gets passed via heartbeat.

    So by disabling the captive portal prompt all you're doing is then letting the user browse unauthenticated (via whatever associated policy) until the auth request gets passed, in my experience anything up to 120 seconds. So not a show stopper, but worth being aware of.

    I'm happy to be corrected. 

    ------------------------------------------------

    worlds number one free ICMP monitoring platform: https://pinescore.com

Share Feedback
×

Submitted a Tech Support Case lately from the Support Portal?