Jump to content

MbamFan2000

Members
  • Posts

    3
  • Joined

  • Last visited

Reputation

0 Neutral
  1. Excellent, thanks! It's working fine now. Thanks again for your help.
  2. P.S. to my original post above: An aside, I don't understand why Mbam didn't give me a pop-up warning like other users get. It *should* have done that, because under the "Protection" tab I've always had a checkmark in the box for "Show tooltip balloon when malicious website is blocked." If I'd got the notifications, it would have made it a lot easier to figure out that it was Mbam blocking the website, instead of going through a bunch of rigamarole trying to troubleshoot things. In any case, I still need to know if the site is safe, is it a false-positive? or ? Thanks again for any help.
  3. Mbam is blocking access to depositphotos.com (a commercial clip-art site). The blocking just started today - it was working fine for several weeks before that. The IP address that's being blocked is 88.85.68.227 . I don't know if the website suddenly became malicious and I should let it be blocked and just cancel my $$ paid subscription there? (I'd rather not do that though, I need that subscription). Or is it a Mbam false positive? How do I know if it's safe to allow the site, or just write it off as a suddenly-new malware site? Advice would be appreciated. Here's today's Mbam log, formatted a bit for easier reading, with my computer/login name deleted for privacy: 2014/04/15 17:03:49 -0700 * * MESSAGE Executing scheduled update: Daily | Silent2014/04/15 17:04:20 -0700 * * MESSAGE Starting database refresh2014/04/15 17:04:20 -0700 * * MESSAGE Stopping IP protection2014/04/15 17:04:20 -0700 * * MESSAGE Scheduled update executed successfully: database updated from version v2014.04.13.09 to version v2014.04.15.112014/04/15 17:04:21 -0700 * * MESSAGE IP Protection stopped successfully2014/04/15 17:04:43 -0700 * * MESSAGE Database refreshed successfully2014/04/15 17:04:43 -0700 * * MESSAGE Starting IP protection2014/04/15 17:04:55 -0700 * * MESSAGE IP Protection started successfully2014/04/15 17:33:33 -0700 * * IP-BLOCK 88.85.68.227 (Type: outgoing, Port: 57559, Process: chrome.exe)2014/04/15 17:33:41 -0700 * * IP-BLOCK 88.85.68.227 (Type: outgoing, Port: 57562, Process: chrome.exe)2014/04/15 17:33:49 -0700 * * IP-BLOCK 88.85.68.227 (Type: outgoing, Port: 57565, Process: chrome.exe)2014/04/15 17:34:05 -0700 * * IP-BLOCK 88.85.68.227 (Type: outgoing, Port: 57593, Process: chrome.exe)2014/04/15 17:34:05 -0700 * * IP-BLOCK 88.85.68.227 (Type: outgoing, Port: 57596, Process: chrome.exe)2014/04/15 17:34:05 -0700 * * IP-BLOCK 88.85.68.227 (Type: outgoing, Port: 57599, Process: chrome.exe)2014/04/15 17:34:13 -0700 * * IP-BLOCK 88.85.68.227 (Type: outgoing, Port: 57609, Process: chrome.exe)2014/04/15 17:34:13 -0700 * * IP-BLOCK 88.85.68.227 (Type: outgoing, Port: 57612, Process: chrome.exe)2014/04/15 17:34:13 -0700 * * IP-BLOCK 88.85.68.227 (Type: outgoing, Port: 57615, Process: chrome.exe)2014/04/15 17:35:10 -0700 * * IP-BLOCK 88.85.68.227 (Type: outgoing, Port: 57648, Process: chrome.exe)2014/04/15 17:37:50 -0700 * * IP-BLOCK 88.85.68.227 (Type: outgoing, Port: 57759, Process: chrome.exe)2014/04/15 17:38:31 -0700 * * IP-BLOCK 88.85.68.227 (Type: outgoing, Port: 57777, Process: chrome.exe)2014/04/15 17:40:47 -0700 * * IP-BLOCK 88.85.68.227 (Type: outgoing, Port: 57808, Process: chrome.exe)2014/04/15 17:44:32 -0700 * * IP-BLOCK 88.85.68.227 (Type: outgoing, Port: 57826, Process: chrome.exe)2014/04/15 17:46:09 -0700 * * IP-BLOCK 88.85.68.227 (Type: outgoing, Port: 57866, Process: chrome.exe)2014/04/15 17:46:25 -0700 * * IP-BLOCK 88.85.68.227 (Type: outgoing, Port: 57878, Process: chrome.exe)2014/04/15 17:50:42 -0700 * * IP-BLOCK 88.85.68.227 (Type: outgoing, Port: 57938, Process: chrome.exe)2014/04/15 17:50:50 -0700 * * IP-BLOCK 88.85.68.227 (Type: outgoing, Port: 57943, Process: chrome.exe)2014/04/15 17:50:50 -0700 * * IP-BLOCK 88.85.68.227 (Type: outgoing, Port: 57946, Process: chrome.exe)2014/04/15 17:50:58 -0700 * * IP-BLOCK 88.85.68.227 (Type: outgoing, Port: 57949, Process: chrome.exe)2014/04/15 17:54:59 -0700 * * IP-BLOCK 88.85.68.227 (Type: outgoing, Port: 58078, Process: chrome.exe)2014/04/15 17:55:32 -0700 * * IP-BLOCK 88.85.68.227 (Type: outgoing, Port: 58086, Process: chrome.exe)2014/04/15 17:59:41 -0700 * * IP-BLOCK 88.85.68.227 (Type: outgoing, Port: 58097, Process: chrome.exe)2014/04/15 18:03:33 -0700 * * IP-BLOCK 88.85.68.227 (Type: outgoing, Port: 58146, Process: chrome.exe)2014/04/15 18:30:04 -0700 * * IP-BLOCK 88.85.68.227 (Type: outgoing, Port: 58446, Process: chrome.exe)2014/04/15 18:30:28 -0700 * * IP-BLOCK 88.85.68.227 (Type: outgoing, Port: 58453, Process: chrome.exe)2014/04/15 18:32:21 -0700 * * IP-BLOCK 88.85.68.227 (Type: outgoing, Port: 58476, Process: chrome.exe)2014/04/15 18:32:21 -0700 * * IP-BLOCK 88.85.68.227 (Type: outgoing, Port: 58481, Process: chrome.exe)2014/04/15 18:32:29 -0700 * * IP-BLOCK 88.85.68.227 (Type: outgoing, Port: 58484, Process: chrome.exe)2014/04/15 18:37:34 -0700 * * IP-BLOCK 88.85.68.227 (Type: outgoing, Port: 58573, Process: chrome.exe)2014/04/15 18:59:08 -0700 * * IP-BLOCK 88.85.68.227 (Type: outgoing, Port: 58789, Process: chrome.exe) It took me a while to figure out that it was Mbam blocking the site, otherwise I wouldn't have kept trying to access the page so many times - at first I thought it was some DNS issue or something (tried to refresh the DNS etc). Then I just started typing the IP number directly into the browser's address bar, but the page still wouldn't load. Turns out it was Mbam blocking access, but why?? Thanks for any help or advice.
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.