RE: (RADIATOR) MAx TNT & MSBlast

2003-08-26 Thread Kevin McKee
35/UDP * 139/TCP * 139/UDP * 445/TCP * 445/UDP * /TCP -Original Message- From: Dave Birkbeck [mailto:[EMAIL PROTECTED] Sent: Monday, August 25, 2003 4:28 PM To: 'Tony Bunce'; 'Sean Watkins (northrock)'; [EMAIL PROTECTED] Subject: RE: (RAD

Re: (RADIATOR) MAx TNT & MSBlast

2003-08-26 Thread Hugh Irvine
ROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Tony Bunce Sent: Friday, August 22, 2003 10:38 AM To: Sean Watkins (northrock); [EMAIL PROTECTED] Subject: RE: (RADIATOR) MAx TNT & MSBlast This problem is actually caused by the "good" blaster worm nachi Nachi pings a host before it

Re: (RADIATOR) MAx TNT & MSBlast

2003-08-26 Thread Jim Brown
ROTECTED]> To: "'Tony Bunce'" <[EMAIL PROTECTED]>; "'Sean Watkins (northrock)'" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Monday, August 25, 2003 7:27 PM Subject: RE: (RADIATOR) MAx TNT & MSBlast > All, > > In addition to

RE: (RADIATOR) MAx TNT & MSBlast

2003-08-25 Thread Dave Birkbeck
Sean Watkins (northrock); [EMAIL PROTECTED] Subject: RE: (RADIATOR) MAx TNT & MSBlast This problem is actually caused by the "good" blaster worm nachi Nachi pings a host before it trys to spread so it doesn't waist its time on non-existent hosts. The problem is that each one of

RE: (RADIATOR) MAx TNT & MSBlast

2003-08-22 Thread Tony Bunce
This problem is actually caused by the "good" blaster worm nachi Nachi pings a host before it trys to spread so it doesn't waist its time on non-existent hosts. The problem is that each one of those pings generates an arp request and with such a high number of pings MAX TNT boxes can't handle t