Dragon76 0 Posted July 4, 2017 Posted July 4, 2017 Nod32 has an HTTP protocol checker that when enabled blocks google drive from connecting to the internet. Is there a way to have this enabled and still have google drive function correctly?
TheMalwareDiscoverer 1 Posted July 4, 2017 Posted July 4, 2017 Hi dragon how it blocks google drive? It won't charge the page or it doesn't allow to upload files?My eset works great with Google Drive; try updating eset itself and also eset virus database. If it don't work Maybe try changing the standard port from 80 to 443
ESET Staff Gonzalo Alvarez 66 Posted July 4, 2017 ESET Staff Posted July 4, 2017 Hi @Dragon76 If you refer to the "Verification of HTTP protocol" by default is active and there is no problem with Google Drive (I can tell you by the machines near to me. The Google drives update fine. Can you submit an screenshot of the configuration you mention it?
Dragon76 0 Posted July 16, 2017 Author Posted July 16, 2017 Thanks for the suggestion. Changing the port worked perfectly.
Administrators Marcos 5,741 Posted July 16, 2017 Administrators Posted July 16, 2017 2 hours ago, Dragon76 said: Thanks for the suggestion. Changing the port worked perfectly. Please post a screen shot of the setting where you changed the port. If you did it at a wrong place, you could disable web access protection.
itman 1,924 Posted July 16, 2017 Posted July 16, 2017 You need to re-add port 443 in addition to port 85.
Dragon76 0 Posted July 17, 2017 Author Posted July 17, 2017 The minute I add 443 back Google Drive refuses to sync. It works great if I only have port 85. Is there an alternative optional port other than 443 that one can try?
itman 1,924 Posted July 17, 2017 Posted July 17, 2017 (edited) Does Google Drive have a URL associated with it? Only thing I can think of would be to exclude the URL associated w/Google Drive from Eset SSL protocol scanning. You definitely need port 443 specified for HTTPS scanning. Edited July 17, 2017 by itman
Recommended Posts