err_socket_not_connected error

[duzzie]

Hi all,

 

We have started having issues withing the last week with some of our Win 10 machines coming up with err_socket_not_connected error. They have worked fine for months and other machines in the same room/ou work fine. It is happening on both Chrome and IE, tried re-install of Chrome, reset all settings and still the same.

 

Does anyone have any ideas please.

[benjie]

Have you tried reset the TCP/IP stack?

 

Use the following commands from a privileged command prompt.

netsh winsock reset catalog

netsh int ipv4 reset reset.log

netsh int ipv6 reset reset.log

[duzzie]

Have you tried reset the TCP/IP stack?

 

Use the following commands from a privileged command prompt.

 

Hi, thanks for the reply. Tried and still no luck.

[duzzie]

Quick update, we have just removed Sophos and both Chrome and IE are working again. Anybody else come across this? We will investigate a bit further.

[russlp]

are you using eSafe at all? we have this issue sometimes but only on machines that have the eSafe client installed.

[duzzie]

are you using eSafe at all? we have this issue sometimes but only on machines that have the eSafe client installed.

 

Hi, yes we are using esafe. We will try uninstalling that as well and and trying again. We did have a lot of issues last year with esafe and SSL certificates.

 

Thanks

[russlp]

We found uninstalling eSafe then running 'netsh winsock reset' brought it back to life. We have Sophos Central too so wonder if Sophos thinks eSafe is up to no good.

[duzzie]

We found uninstalling eSafe then running 'netsh winsock reset' brought it back to life. We have Sophos Central too so wonder if Sophos thinks eSafe is up to no good.

 

It does indeed look like a combination of Sophos and eSafe, we have spoken to both of them without much luck so far. Will post once we get a fix.

 

Thanks.