Sophos incompatible program sharepoint server

Hi Jak Sorry for not replying sooner been very busy. Thanks, John. I'm afraid it's one application or the other on these platforms. Hi Jak Thanks for the information I had a feeling that was going to be the answer looks like I will just have to keep the web protection disabled until we can afford to replace the machines which could be a long time off. Thanks again, John. Post as a guest Name. Email Required, but never shown.

The Overflow Blog. Podcast Helping communities build their own LTE networks. Podcast Making Agile work for data science. Featured on Meta. New post summary designs on greatest hits now, everywhere else eventually.

Related 1. Hot Network Questions. Question feed. Policies and exceptions. Data control list. General settings. Address group. Web server. Web servers. Protection policies. Authentication policies. Authentication templates. Advanced protection. VPN overview.

IPsec policies. WAN link manager. IPv6 router advertisement. Cellular WAN. IP tunnels. Dynamic DNS. Static routing. SD-WAN policy routing. Upstream proxy. LDAP server.

Active Directory server. Multi-factor authentication MFA. Web authentication. I tried both with and without front-end authentication delegation on the UTM, and I enabled basic authentication on the relevant site only - disabling Windows NTLM authentication after observing the issue ID 9. Any suggestions? It is going to be a deal breaker if I can't get this working. It is important to ensure that the back-end SharePoint only has basic authentication enabled, check the HTTP headers for this.

The next step is to modify the basic authentication settings in IIS, and change the default domain in the basic authentication settings. This means that just specifying a username works fine. When the UTM does authentication delegation, it only sends the plain username to the back-end web server.

This means that the authentication delegation will fail unless the default domain is set in the IIS properties for the external website. However, when using this method, Word and other Office apps fail because I believe that the UTM is presenting them the forms based authentication page when you try and check out a document, and the Office tries to connect to the SharePoint web services. ISA is better in this respect as it only does forms based authentication for browser clients based on the headers sent in the HTTP request, otherwise it falls back to basic.

I overcame this by changing the authentication delegation on the front-end in the UTM to basic. When users now connect to the SharePoint site externally, they have to provide just their username and password, and the UTM does the authentication to the back-end server.