Jump to content

Persistent schannel errors - Internet protection module: 1236


Go to solution Solved by stackz,

Recommended Posts

  • ESET Insiders

Windows 7x64 Pro

 

Modules:

Virus signature database: 12627 (20151126)
Rapid Response module: 7077 (20151126)
Update module: 1060 (20150617)
Antivirus and antispyware scanner module: 1474 (20151111)
Advanced heuristics module: 1162 (20150923)
Archive support module: 1239 (20150929)
Cleaner module: 1114 (20151004)
Anti-Stealth support module: 1091 (20151117)
Personal firewall module: 1289 (20151019)
ESET SysInspector module: 1254 (20150924)
Real-time file system protection module: 1010 (20150806)
Translation support module: 1411.3 (20151009)
HIPS support module: 1206 (20151117)
Internet protection module: 1236 (20151116)
Web content filter module: 1046 (20150925)
Advanced antispam module: 2845 (20151126)
Database module: 1072 (20150831)
Configuration module (33): 1191B.3 (20151009)
LiveGrid communication module: 1020 (20150807)
Specialized cleaner module: 1010 (20141118)
Banking & payment protection module: 1055 (20151117)
 

ESS updated Internet protection module to 1236 and ever since then I cannot connect with SSL scanning enabled to any https URL (including this forum). At present I've had to disable SSL scanning for all browsers and Windows Live Mail.

Scanning was fine with the previous module, IIRC v1226.1

Link to comment
Share on other sites

  • ESET Insiders

I switched to pre-release updates and SSL scanning is working fine.

 

Virus signature database: 12628P (20151126)
Rapid Response module: 7079 (20151126)
Update module: 1060 (20150617)
Antivirus and antispyware scanner module: 1474 (20151111)
Advanced heuristics module: 1162 (20150923)
Archive support module: 1240 (20151109)
Cleaner module: 1116 (20151113)
Anti-Stealth support module: 1091 (20151117)
Personal firewall module: 1292 (20151111)
ESET SysInspector module: 1257 (20151113)
Real-time file system protection module: 1011 (20151112)
Translation support module: 1429 (20151119)
HIPS support module: 1206 (20151117)
Internet protection module: 1238 (20151124)
Web content filter module: 1046 (20150925)
Advanced antispam module: 2846P (20151126)
Database module: 1072 (20150831)
Configuration module (33): 1213B.8 (20151124)
LiveGrid communication module: 1020 (20150807)
Specialized cleaner module: 1010 (20141118)
Banking & payment protection module: 1055 (20151117)
 

Link to comment
Share on other sites

  • Administrators

Please enable generation of complete application memory dumps in the advanced setup -> Tools -> Diagnostics, then try to reproduce the issue. Check if there are some dumps created in the Diagnostics folder (for the complete path check the path setting in that setup section).

 

If no dumps are created, enable protocol filtering advanced logging in the Diagnostics setup and reproduce the issue. Finally supply me with 2 pcapng files created in the Diagnostics folder.

 

Also try enabling pre-release updates to see if installing the very latest version makes a difference. With pre-release updates enabled, you should have Internet protection module 1238 installed.

Link to comment
Share on other sites

  • ESET Insiders

Well that was short lived. lol
Boot up this morning and SSL scanning is fubarred even on pre-release updates.

Reverted to regular update channel, but still not functioning.

Attached is requested pcap logs.

SSL_Diagnostics.zip

Edited by stackz
Link to comment
Share on other sites

  • Administrators

Now there is IPP module 1226.2 available and 1238 on pre-release servers. Does it now work with 1226.2 and switching to pre-release updates re-introduces the issue? If so, please try the following with 1238 installed:

- restart the computer (do not run any applications after the system starts)

- disable SSL/TLS scanning and click OK

- enable SSL/TLS scanning and click OK

- try to reproduce the issue.

 

We look forward to hearing from you about your findings.

Link to comment
Share on other sites

  • ESET Insiders
  • Solution
Does it now work with 1226.2 and switching to pre-release updates re-introduces the issue?

 

 

 

Yes, 1226.2 works just fine.

Updating to 1238 reintroduced the SSL problems.

  1. Reboot, run browser - SSL problems. Toggle SSL settings - still SSL problems.
  2. Reboot, Toggle SSL settings, run browsers -  SSL working fine.

Finally reverted back to 1226.2 and SSL is still fully functional.

Edited by stackz
Link to comment
Share on other sites

  • ESET Staff

It would help us a great deal if you could do the following:

1. Download procdump from https://technet.microsoft.com/en-us/sysinternals/dd996900.aspx and Process Monitor from https://technet.microsoft.com/en-us/sysinternals/processmonitor.aspx

2. Update from prerelease update servers, this should reintroduce the problems, possibly after a reboot

3. When that happens, run

procdump -ma ekrn.exe

4. Start Process Monitor, start monitoring, open some pages that end with error, stop monitoring

5. Send me the ekrn dump and process monitor log

 

Thanks a lot.

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...