I probably had outlook open because the internal ip that was being scanned is not routed too by the nat server, so I guess any activity to that ip had to be initiated by it. I'm just wondering why my firewall picked it up as a portscan. well thanks for the reply
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Wednesday, March 06, 2002 3:50 AM To: Mark Matrafajlo Subject: Re: comcast port scans If the portscan is on port 53, it'll be answers to DNS queries. Otherwise, it's possibly some form of loadbalancing. Alternatively, someone cracked it with one of the BIND bugs and has been using it to launch attacks. CONFIDENTIALITY: This e-mail and any attachments are confidential and may be privileged. If you are not a named recipient, please notify the sender immediately and do not disclose the contents to another person, use it for any purpose, or store or copy the information in any medium.
