Peasantmk2

OK, thanks. It's uninstalled at the moment, so I'll leave it that way for a few weeks and see what happens. Thanks for the prompt reply. Much appreciated.

Hello, I've been using Google Pay quite happily on my Pixel 2 for a couple of years with no problem, but in the past few months sometimes it hasn't been working. Doing a Google search shows that I'm not the only one with this problem, and there doesn't appear to be an easy solution. A quick fix is just to reboot the phone before use which sorts it, sometimes for a couple of weeks. The problem started around the time I installed ESET Mobile Security, but it may just be coincidence. It wasn't working last week, and I uninstalled ESET at the weekend, and Google pay worked fine this evening. Has anyone else come across this? Thanks.

Hello, I have two windows PC's, one running NOD32, the other on SSP. I have the same problem with both in that Dropbox cannot establish a secure connection if I have SSL/TLS protocol filtering enabled. It connects fine if I disable it. This all worked fine up until this weekend. I'm on version 14.0.22.0 of SSP on the laptop I'm writing this from. I'm wondering if there has been some change to the SSL/TLS in an update, as I have had clients of mine on Gmail (mostly) and Thunderbird who have had email collection problems. I saw in the KB there was a fix for this. Thanks.

Sorry, I've been busy for a while. I'll get onto this hopefully later this week. Thanks for replying.

Hello, I have a small network that uses SME server as a gateway (https://wiki.contribs.org/Main_Page). I run 6 workstations in this, two of which run windows 10. One is a clean install, the other an upgrade from Windows 8.1. In both cases I am having problems with running Windows update when protocol filtering is enabled in ESET Smart Security or NOD32. Windows update errors with error 0x80245006. If protocol filtering is disabled, or enabled, but with ssl/tls filtering disabled, Windows update works fine. I worked with technical support at ESET UK yesterday, and they managed to pin it down to an invalid certificate at the following URL: https://fe2.update.microsoft.com/v6/ClientWebService/client.asmx They found this in the Windows update log. This morning I decided to try connecting one of the workstations to a separate network that did not use SME Server, and Windows update worked as normal. I have raised a bug with the SME project, and the developers are asking for documentation on what is checked when protocol filtering is turned on. I have a copy of the user guide, but as I'm not a developer myself I'm not sure if that will go into enough depth for them. Is there any other documentation I could send them? Also, if anyone has any further ideas as to what may be happening it would be much appreciated. Thank you.