Re: ACS socket may be blocked after Win 10 upgrade?

Does ACS require any of the SMB ports to talk talk with the Windows box? One of the Windows updates breaks SMBv1, and causes much frustration, killing firewalls, anti-virus etc. Might be worth re-enabling to see if it helps. Even more frustrating, the update allows SMBv1 to work but if it hasn't been used for some time it kills it without telling you.

Control Panel -> Programs and Features -> Turn on Windows Features and look for SMBv1. There is a drop down arrow. Make sure all 3 boxes are checked. There is a CLI command that is supposed to do the same thing but I've found it will either tell you it's enabled while missing 1 part, or not enable all 3 pieces.

Clay Carley

On 2018-05-01 10:17, Scott Williams wrote:

On Tue, May 1, 2018 at 10:55 AM, Bob Cagle <bcagle@xxxxxxxxxxx> wrote:
So I've completely uninstalled Sophos, and turned off Windows Defender

-

there is now no anti-virus or firewall of any kind running. I even
upgraded ACS to 1.1.7.3. I am still getting this 'Socket may be

blocked'

error and still unable to connect.

At this point ACS is completely unusable. Not sure what to try next.

I'll be curious to see as others get upgraded to the Win10 Spring 2018
update (version 1803) if ACS breaks for them also.

Thanks

Bob Cagle
IT Manager
Lynk

Just upgraded an extra PC in the office to test this. Now on Win10 Build
1803 - 17134.1 with older ACS 1.1.3 Build id: 4401 and have not encountered
this issue. The client connects as expected.

Hope that helps.