This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Firewall Problem: Invalid Checksum

EMC v5.2.1.197

ES&C v10.3

I'm using the trial version of the endpoint goodies, and after successfully getting filezilla server and pidgin to work, teamviewer and spiceworks still fail due to an invalid checksum error.  I have unchecked the "use checksums" box under the general tab, added the programs as trusted under the applications tab, allowed the processes to create hidden processes, and double checked that the checksums do match between the whitelist and the log file.  Still getting:

11:50:50 AM teamviewer_service.exe OUT REFUSED TCP 95.211.37.198 HTTP Invalid Checksum

Thoughts, suggestions?

:45625


This thread was automatically locked due to age.
Parents
  • Hello AlexD,

    thoughts first :smileywink::

    unchecked the "use checksums" box

    As this applies to all applications and is used to verify the integrity of a known application, it should not considered as solution - I assume you temporarily turned it off for troubleshooting only.

    trusted ... create hidden processes ...

    This is more like desperately turning knobs and flipping switches, not a systematic approach :smileyhappy:. While Reason might not always be immediately intuitive there is no obscure cause behind it - if it says Invalid checksum then it is Invalid checksum. Application rules (trusted) are considered only after an application has been positively identified and neither is a hidden process involved nor would the allow launch setting affect the connectivity of the parent application.

    I don't think there is a bug or some peculiarity of these applications involved. Please note that a checksum decision "sticks" until the process is restarted. I.e. if teamviewer_service.exe is blocked due to invalid checksum it nevertheless keeps running. Any subsequent attempt by it to access the network will be blocked - even if you then add its checksum or untick Use checksums as the check is made at the first connection attempt only. 

    HTH

    Christian

    :45635
Reply
  • Hello AlexD,

    thoughts first :smileywink::

    unchecked the "use checksums" box

    As this applies to all applications and is used to verify the integrity of a known application, it should not considered as solution - I assume you temporarily turned it off for troubleshooting only.

    trusted ... create hidden processes ...

    This is more like desperately turning knobs and flipping switches, not a systematic approach :smileyhappy:. While Reason might not always be immediately intuitive there is no obscure cause behind it - if it says Invalid checksum then it is Invalid checksum. Application rules (trusted) are considered only after an application has been positively identified and neither is a hidden process involved nor would the allow launch setting affect the connectivity of the parent application.

    I don't think there is a bug or some peculiarity of these applications involved. Please note that a checksum decision "sticks" until the process is restarted. I.e. if teamviewer_service.exe is blocked due to invalid checksum it nevertheless keeps running. Any subsequent attempt by it to access the network will be blocked - even if you then add its checksum or untick Use checksums as the check is made at the first connection attempt only. 

    HTH

    Christian

    :45635
Children
No Data