From: Jung, Jin (jin.jung@lmco.com)
Date: Wed Aug 13 2003 - 11:55:47 GMT-3
Hi Brian,
Did you block tcp and udp port 135 ?
Does it brake windows netbios?
I only blocked 4444 and 69, should I block 135 too?
Thanks...
-----Original Message-----
From: George Gittins [mailto:g.gittins@edinburg.esc1.net]
Sent: Wednesday, August 13, 2003 9:43 AM
To: ccielab@groupstudy.com
Subject: FW: Virus Alert - W32.Blaster.Worm
Why port 135? Can you should a access -list
George Gittins
Network Maintenance Supervisor
ECISD
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Brown, Patrick (NSOC-OCF}
Sent: Tuesday, August 12, 2003 7:58 PM
To: 'Snow, Tim '; ''ccielab@groupstudy.com' '
Subject: RE: Virus Alert - W32.Blaster.Worm
Getting about 20,000 hits a second on ACL referencing port 135. Plus Arp
process is going through the roof until acl is applied.
Patrick B
-----Original Message-----
From: Snow, Tim
To: 'ccielab@groupstudy.com'
Sent: 8/11/2003 10:14 PM
Subject: Virus Alert - W32.Blaster.Worm
Anyone else going through the W32.Blaster.Worm?
http://securityresponse.symantec.com/avcenter/venc/data/w32.blaster.worm
.htm
l
Big pain in the ....
Tim
Timothy Snow
CCIE #12042
EDS - Network Operations
MS 3B
1075 W. Entrance Drive
Auburn Hills, MI 48326
* phone: +01-248-754-7900
* mailto:timothy.snow@eds.com
pager: 888-351-4584
www.eds.com
This archive was generated by hypermail 2.1.4 : Tue Sep 02 2003 - 18:53:58 GMT-3