Sophos Web Appliance SMBv1 Dependecy.

We are in the process of upgrading the SMB/AD integration components on the Web Appliance and will be publishing an update to the product as soon as that work is complete and fully tested. This will allow the SWA to connect to AD services that have disabled SMBv1.

We hope to do this before the end of July.

Rollout of v4.3.3, with SMB v2 support, started this week. We are rolling it out gradually to customers over the next few weeks.

I've noted that already 2 days ago.  

Gradually meaning randomly, or meaning Sophos targets particular hardware or OVA first ?

All our SWA releases are published to appliances in stages, with each stage making the release available to larger groups of customers. Group selection is pretty much random, although we generally use the same groupings across a number of releases.

All our SWA releases are published to appliances in stages, with each stage making the release available to larger groups of customers. Group selection is pretty much random, although we generally use the same groupings across a number of releases.

4.3.3 installed on both of our WEB Gateways.  Authentication to domain still fails.

Same errors including "No Netlogon" share found.  Worry not, the share is there ...  

Any firewall rules to setup on DCs and Desktops to make 4.3.3 work ?

I have just shutdown the firewall on all of my DCs to test connection.  Same errors.

Can you please enable Remote Assistance and we'll connect to your SWA to investigate.

Done.  Both appliance are enabled to support.  Case open.  Support can reach me by phone anytime tonite and tomorrow.

OK.  Here's our status as of Friday night.  It may help someone ... Sophos support call to help.  We tried the same procedure as of 2017-9-7 6:28 PM.  Same error as both screen shots we posted then.

We subsequently unchecked "Auto-detect advanced settings".  Even-though "Verify Settings" failed, fields were filled up correctly.  Then we changed port 3268 to port 389.  "Verify Settings" finally succeeded.

We put 3268 back afterward. "Verify Settings" failed at first, but succeeded at the second attempt.  Our other SWG (we have more than one) succeeded in returning to port 3268 immediately.  Which means succeeded at joining the domain.

Observations:  

1- Maybe returning to 3268 on the first SWG failed because we did leave enough time to the appliance before we clicked "applied".

2- On my Windows Domain Controller logs. Not a single 389 or 3268 request was dropped.  We event tried to join SWG to AD with all firewalls deactivated on all domain controllers.  It is clearly not a question of firewall.

3- Sophos requirements tell UDP 3268 should be activated.  We were not able to catch any such request on all of our firewalls for as long as we can read logs.  Furthermore, UDP 3268 is barely mentioned on Google.  And I haven't found docs on Microsoft's web site yet.  This requirement seems to be an error.  TCP 3268, as it should, is frequently requested (by other devices as well).

4- Why Sophos does not use SLDAP, port 3269 instead of unsecured LDAP, port 3268, is beyond me.

I understand 4.3.3 is a beta version.

So how exactly was this issue fixed??

We have the exact same issue - saying no Netlogon share was found. I don't get it....

It is not fixed.  Still cannot connect to Windows 2016 active directory.