Jump to content

Battlecatt

Members
  • Posts

    4
  • Joined

  • Last visited

Reputation

0 Neutral
  1. Hello Firefox, sorry its taking me so long to reply in here. I got the last "Home Use Program" version Of Norton last fall. Not sure of the Version itself, will check tonight and post it in here. Anyway, I am going to have one of our IT guys at the office get me a copy of the newest Home Use Program Version of "Symantec Endpoint" and burn it to a CD so I can take it home and install it. Will take a couple of days to get it. What I did find in the meantime however...... It is deffinately the Norton Firewall that is blocking the ability to update MBAM. I discovered this with a little experimentation (and some desperation lol). I disabled the Norton Firewall (came with the version of Norton im using from the Air Force Home Use Program) and then clicked on the update button for MBAM...WA-LA!!! It worked just fine!!!! MBAM updated fast, quick and with no issues!!! So, I Re-enabled the fire wall then clicked the update button again for MBAM and got the error. I have since tested this by routinely updating MBAM, first by not dis-abling the firewall (and yes I went into the firewall settings and listed every MBAM file I could find as being "PERMITTED" to acces the internet.) and hitting the update button...Always get the error. Dis-able Firewall and click the update button...works flawlessly. I will be installing the Symantec Endpoint later on this week and removing the old Norton. So now I have ANOTHER issue that Ill post about in another thread...Last Night I got new Updates from Microsoft and got the latest "Malicious Software Removal" tool as I always do once a month. After the re-boot to have the new updates take effect, The Malicious Software Removal tool immediately popped up saying I had a Virus. In all the many iterations of getting this tool (seems to be updated once a month or so by microsoft via automatic updates) I have NEVER had this thing find anything before ... let alone pop up any alerts!!!! So I ran it in accordance with its instructions....2 and a half hours later, it finished and said that I have "Win32/Alureon.h" ......... It said to do the following... 1.) "Run a Valid AntiVirus Program with the latest updates." 2.) "Re-Boot Your Computer" So I got the latest "Live Update" for my Norton and ran a full scan. Norton found (1 hour & 26 minutes later) this: "TROJAN.FAKEAV" And apparently its fix action was "cleaned that by deletion". When that was all done, It was late, so rather than re-boot, I shut the computer down and went to bed. So now, Im using this forums wonderful search utility to see who all else has this and how to kill the sucker!! Many Thanks!! Battlecatt
  2. Hi noknojon, Thanks for the info, not sure of any add on packs the Norton may have (or have gotten) only thing I manually run on it is live update and i only ever see it updating the virus files. I will have a look tonight when I get home from work.
  3. Hi, have same problem and I am running Norton A/V Corporate Edition (USAF Approved for Home Use) First couple of times I used Malwarebytes and ran the update there was no problem. Now suddenly I cant update! Not sure what to do at this point. I have un-installed and re-installed Version 1.45 and am still getting this error. I am running XP Home with all the service packs.
  4. Greetings, New here. Just downloaded Malwarebytes a couple of nights ago after a rouge "Security Center" virus infected my machine. After a few "tweeks" of my own, I was able to actually get Malware to update and run. It worked wonderfully!! Fast forward to last night. Surfing along when "WHAM" I get a "new" Rouge (read fake) Security Virus called "Security Soft." It immediately freezes my machine and starts running a supposed "scan" and listing 10 Gagillion things infected, yadda, yadda.... I ignore it and try to fire up Malwarebytes...no dice. Try my browser...locked. Try Norton...no go. Nothing works other than a stupid pop-up ranting of the Doomsday of my machine by this virus. Soooooooo.... I re-boot and immediately upon getting back to my desktop, I hit a restore point, effectively reseting my registry to a couple of days ago, then...having done that, re-boot once more and Ta Da!!! I can Run Malwarebytes!! Did a full scan...all drives...the program once again works flawlessly. Notice!!! I did not try to get the program to get an update. I had a thought that any attempt at the internet would trigger the new virus off again even though I had restored my registry to an earlier time. Malwarebytes finds the little bugger and I have it stomp the ugly out of it. THEN....I ran a "Quick Scan" just to be sure....Oh yeah...it's Gone!!!! I'm a happy camper!!! But alas, it was not to last. After the scans, I tried to get Malwarebytes to get an update....."Connection Failed". Sooooo I open my browser..."DNS Error, Unable to connect, yadda yadda" Open up my network connections and check my ethernet card. Run a repair, everything checks out. Re-boot, try again...nada. Then it occured to me...sometimes, on rare ocassions with XP-Home....settings can get "confused" after so much tweeking of registry files and settings, so I decided to try something simple. If you still cant connect to the internet and your card (ethernet) settings say all is well, right click the connection and disable the card. Yes that's "disable" the card. Wait like 30 seconds then click "Enable." and try again. Some device drivers tend to lock up, in particular after a network attack. In combination with fixing erroneous registry errors, sometimes that may be all it takes to get back on-line. Well, worked for me at least. To get to your network card in XP, go to "Control Panel" select "Network Settings" right click your connection and the rest is pretty simple. Specs: CPU: AMD Phenom Quad Core H/D: 500 Gig RAM 4 gig Antivirus: Norton Corporate Edition with Firewall.
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.