Author Topic: [WTF!?] Sasser on patched system!?!?!?!  (Read 11734 times)

0 Members and 1 Guest are viewing this topic.

Offline RejZoR

  • Polymorphic Sheep
  • Serious Graphoman
  • *****
  • Posts: 9408
  • We are supersheep, resistance is futile!
    • RejZoR's Flock of Sheep
Re:[WTF!?] Sasser on patched system!?!?!?!
« Reply #15 on: June 04, 2004, 08:15:28 PM »
I'm now preparing backups to format the disk. And i'll make two partitions,because i never thought that only 20GB disk can make so much work lol :) Next time i'll have to format only the one on which will Windows be. Just around 3GB left to backup :) If everything will be ok,i'll report here :)
Visit my webpage Angry Sheep Blog

Offline RejZoR

  • Polymorphic Sheep
  • Serious Graphoman
  • *****
  • Posts: 9408
  • We are supersheep, resistance is futile!
    • RejZoR's Flock of Sheep
Re:[WTF!?] Sasser on patched system!?!?!?!
« Reply #16 on: June 05, 2004, 11:12:14 AM »
Oh boy. Today i finally got it. NOD32 was guilty for all these problems and nothing else ::) After fresh install everything was working ok,after i install NOD32 and rebooted,bam that lsass crap popped up again. Now i removed NOD32 and its fine again. I'm returning back to avast! :)
Visit my webpage Angry Sheep Blog

Offline igor

  • Avast team
  • Serious Graphoman
  • *
  • Posts: 11863
    • AVAST Software
Re:[WTF!?] Sasser on patched system!?!?!?!
« Reply #17 on: June 05, 2004, 11:54:41 AM »
Well, I certainly don't want to change your decision  ;D
- but it's certainly very strange... how could NOD be responsible for this thing? (Unless it's trying to prevent/detect the vulnerability and fails miserably by crashing the thing... I wonder if any other NOD users had the same problem...)

Offline RejZoR

  • Polymorphic Sheep
  • Serious Graphoman
  • *****
  • Posts: 9408
  • We are supersheep, resistance is futile!
    • RejZoR's Flock of Sheep
Re:[WTF!?] Sasser on patched system!?!?!?!
« Reply #18 on: June 06, 2004, 10:17:52 AM »
Yesterday i submited info on NOD32 board (Wilders Forums). I also found out that IMON (Mail scanner) couses this. Today there are 4 such cases and looks like new will pop up. Hope ESET programers will help soon heh
Visit my webpage Angry Sheep Blog