Jump to content

Alecun

Members
  • Posts

    8
  • Joined

  • Last visited

Reputation

0 Neutral

About Alecun

  • Birthday 02/08/1970

Profile Information

  • Location
    Chamalires, France
  • Interests
    Fashion, games, cinema, petanque, jumping stilts, roller skating, ice skating
  1. Further to my closed thread my MBAM tray icon is again black however; despite this, file system protection remains checked and MBAM reports that protection is partially enabled. If I check the option to enable malcious website blocking, protection is completely enabled and the tray icon changes to red but returns to black on reboot. I will add that I have unchecked the 'Start malicious website blocking when protection module starts' option because it drives me insane. I never had that enabled on previous versions and the tray icon always stayed red. Does this mean that v1.65.0.1400 now operates differently or do I still have a problem with protection please?
  2. Sorry, I missed the 'Attach this file' button. MBAM.v1.65.0.1400_logs.zip
  3. All the logs scans are attached in a zip archive. There are only 2 logs because I reinstalled MBAM yesterday.
  4. Other than posting logs I have tried uninstalling with mbam_clean, rebooting, reinstalling and restarting 5 times. I also used the cmd line to enable terminal services and despite a further 2 restarts the tray icon remains black on startup forcing me to manually enable protection. Like everyone else here, I have never experienced this with previous updates and believe this version to be defective. Instead of making users waste loads of time with workaround solutions that don't always work would it not be simpler to correct the bug and release a new update? Alternatively, can I reinstall v1.62.0.1300 as that worked fine?
  5. @ 1PW Thanks for your suggestions however, I use Skype as a telephone replacement allowing customers, suppliers, and friends to contact me whenever they wish. This obliges me to have Skype active in online mode which means in the system tray. MBAM's IP blocking is not preventing me from using Skype which is good but I was curious as to why MBAM considered these IP's as malicious as well as why Skype was making outbound connections to those IP addresses without any input from myself? John A's post has kind of answered those questions although I still don't see why ThreeGuser feels that Skype should be on the software to avoid list. @ Mainard Thanks for your reply. Do you see Skype as malevolent, as in should I replace it with something else? I have to admit I find MSN Messenger far more intrusive but at least MBAM doesn't have a problem with it at this time.
  6. 08:48:18 PBC MESSAGE Protection started successfully 08:48:22 PBC MESSAGE IP Protection started successfully 11:03:12 PBC IP-BLOCK 222.65.178.149 (Type: incoming, Port: 63754, Process: skype.exe) 11:03:12 PBC IP-BLOCK 222.65.178.149 (Type: incoming, Port: 63754, Process: svchost.exe) 11:03:12 PBC IP-BLOCK 222.65.178.149 (Type: incoming, Port: 63754, Process: svchost.exe) 12:06:34 PBC DETECTION C:\Users\PBC\AppData\Local\Temp\7zS3110.tmp\check.exe Trojan.Agent QUARANTINE 19:00:13 PBC MESSAGE Scheduled update executed successfully 19:00:43 PBC MESSAGE IP Protection stopped 19:00:45 PBC MESSAGE Database updated successfully 19:00:46 PBC MESSAGE IP Protection started successfully 20:20:49 PBC IP-BLOCK 200.63.43.50 (Type: outgoing, Port: 63754, Process: skype.exe) 20:20:49 PBC IP-BLOCK 200.63.43.50 (Type: outgoing, Port: 63754, Process: skype.exe) 20:20:49 PBC IP-BLOCK 200.63.43.50 (Type: outgoing, Port: 63754, Process: skype.exe) 20:26:25 PBC IP-BLOCK 89.28.94.180 (Type: outgoing, Port: 63754, Process: skype.exe) 20:26:33 PBC IP-BLOCK 89.28.94.180 (Type: outgoing, Port: 63754, Process: skype.exe) 20:26:33 PBC IP-BLOCK 89.28.94.180 (Type: outgoing, Port: 63754, Process: skype.exe) 22:03:20 PBC IP-BLOCK 89.28.24.36 (Type: outgoing, Port: 53704, Process: skype.exe) 22:03:20 PBC IP-BLOCK 89.28.24.36 (Type: outgoing, Port: 63754, Process: skype.exe) 22:03:28 PBC IP-BLOCK 89.28.24.36 (Type: incoming, Port: 63754, Process: skype.exe) 22:03:28 PBC IP-BLOCK 89.28.24.36 (Type: incoming, Port: 63754, Process: svchost.exe) 22:03:28 PBC IP-BLOCK 89.28.24.36 (Type: incoming, Port: 63754, Process: svchost.exe) 00:38:43 PBC IP-BLOCK 213.155.31.248 (Type: outgoing, Port: 63754, Process: skype.exe) 00:38:43 PBC IP-BLOCK 213.155.31.248 (Type: outgoing, Port: 63754, Process: skype.exe) 00:38:51 PBC IP-BLOCK 213.155.31.248 (Type: outgoing, Port: 63754, Process: skype.exe) 06:10:04 PBC IP-BLOCK 89.28.94.180 (Type: outgoing, Port: 63754, Process: skype.exe) 06:10:04 PBC IP-BLOCK 89.28.94.180 (Type: outgoing, Port: 63754, Process: skype.exe) 06:10:12 PBC IP-BLOCK 89.28.94.180 (Type: outgoing, Port: 63754, Process: skype.exe)
  7. Hi, I'm just trying out the product and am concerned by regular IP blocking messages which MBAM claims were initiated by Skype. I've been using Skype for a long time and it has never opened any sites however, being freeware I have no doubt it is supported by ads. Is Skype trying to reach sites to download ad banners please, and if that is the case, why does MBAM consider such sites as malicious?
Back to top
×
×
  • Create New...

Important Information

This site uses cookies - We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.