On Thu, 17 Jul 2003 09:30:26 GMT, "-=ô;ö=-" <Not.Telling@nowhere.com> wrote:

:^) Please check your firewall logs for any of the below listed trapped IP Addresses and let's
:^) see if we have any "Bingo's"..Also, post your suspicious one's in this thread and maybe we
:^) can defeat the *******s at their own game..Could be time for a full scale retaliatory
:^) strike..
:^)
:^) This is a list of the most recent and active random port scanning IPAddresses, all have
:^) accumulated over 200+ hits each in the last week attacking differentports at random,
:^) seems awfully damned strange Verizon Security has not seen this sortof activity on their
:^) radar screens, maybe they have and know where and who is perpertrating these incessant
:^) scans...
:^)
:^) 4.3.170.235, crtntx1-ar5-4-3-170-235.crtntx1.dsl-verizon.net
:^) 4.4.7.196, 1000BMHZ
:^) 4.33.51.202, lsanca1-ar2-051-202.biz.dsl.gtei.net
:^) 4.33.51.203, lsanca1-ar2-051-203.biz.dsl.gtei.net
:^) 4.33.51.204, ST4
:^) 4.33.110.172 (Seems the most Persistant *******)
:^) 4.34.137.192, NEC-Q7UPCSM06UQ
:^) 4.35.41.210, lsanca1-ar8-041-210.lsanca1.dsl-verizon.net
:^) 4.35.57.11, VERIZON-4XAFUE1
:^) 4.35.82.53, EUSER
:^) 4.35.83.53, NICHOLAS
:^) 4.35.122.21, TRAVELMATE
:^) 4.35.123.130
:^) 4.35.123.219,JO
:^) 4.35.128.22, HOME-6G73QN8QN2
:^) 4.35.130.80
:^) 4.35.184.33
:^) 4.62.161.223, lsanca2-ar29-4-62-161-223.lsanca2.dsl-verizon.net
:^) 12.98.109.234,234.muaf.wash.wacdc01r1.dsl.att.net



For Tommy - I don't know why any others want to access my computer.
The reason for a firewall is I don't think they need to access my computer.
They are not targeting me - they scan IP ranges seeing who is online.
Some may be LEA monitoring connections to radical usenet news groups.
Download a message from a suspicious ng and pings appear on the fw log.
Any ng containing the word "privacy" seems to be an example of a suspicious ng.
You read a message posted here and you don't have a firewall?
See below who is accessing your computer.

You may have read in a magazine or in a privacy ng about vendors cooperating with
lea by their software not "seeing" the lea snoopware. Believe it.
The software that monitors my computer sees things my commercial firewalldoes not.

Some of the events noted by a commercial firewall that is pretty good.
Partial listing, my ISP and some others omitted.
Event, Intruder, Intruder IP, Source Port, Destination Port,
UDP port probe, SSS002, 67.96.17.227, 1646, 1434,
HTTP port probe, host025153.redesdelsur.com, 200.69.25.153, 1904, 80,
HTTP port probe, 211.138.246.3, 211.138.246.3, 9360, 80,
MSRPC UDP port probe, CPS3M1K2E, 65.206.67.250, 2605, 135,

Persistent callers - kept changing IP
MSRPC UDP port probe, 210.5.22.20, 210.5.22.20, 28986, 135 ,
MSRPC UDP port probe, 210.5.22.23, 210.5.22.23, 29119, 135,
MSRPC UDP port probe, 218.15.192.95, 218.15.192.95, 29119, 135,
MSRPC UDP port probe, 218.15.192.94, 218.15.192.94, 29119, 135,
MSRPC UDP port probe, 210.5.22.18, 210.5.22.18, 30657, 135,
MSRPC UDP port probe, 218.15.192.106, 218.15.192.106,29119, 135,
MSRPC UDP port probe, 218.15.192.94, 218.15.192.94, 29119, 135,
MSRPC UDP port probe, 218.15.192.83, 218.15.192.83, 31332, 135,

TCP port probe, 12.246.197.197, 12.246.197.197, 1770, 17300
TCP port probe, 80.253.125.30, 80.253.125.30, 1103, 6588,
SOCKS port probe, 80.253.125.30, 80.253.125.30, 1102, 1080,
TCP port probe, adsl-35-117-89.msy.bellsouth.net, 67.35.117.89, 50619, 2195
SubSeven port probe, h00e029865daf.ne.client2.attbi.com, 65.96.179.166, 3838, 27374
NetBIOS port probe, 218.49.178.181, 218.49.178.181, 2439, 139
TCP port probe, 80.253.125.29, 80.253.125.29, 1199, 6588,
TCP port probe, LAPTOP, 64.9.110.144, 4852, 17300,
MSRPC UDP port probe, UNQ-TER-W2K, 65.206.26.171, 1116, 135,
MSRPC UDP port probe, 218.15.192.107, 218.15.192.107, 29119, 135,
SQL port probe, NTSERVERB, 80.19.58.230, 3974, 1433,
MSRPC UDP port probe, 210.5.22.19, 210.5.22.19, 31115, 135,
TCP port probe, c-67-164-197-20.client.comcast.net, 67.164.197.20, 3986, 17300
TCP port probe, user-0c938ck.cable.mindspring.com, 24.145.161.148,4166, 3531
TCP port probe, ip-129-15-82-91.LAW.ou.edu, 129.15.82.91, 2169, 3531
TCP port probe, user-0c938ck.cable.mindspring.com, 24.145.161.148, 4161,3531,
TCP port probe, ip-129-15-82-91.LAW.ou.edu, 129.15.82.91, 2169, 3531,
UDP port probe, user-0c938ck.cable.mindspring.com, 24.145.161.148, 69, 3531
TCP port probe, ip-129-15-82-91.LAW.ou.edu, 129.15.82.91, 2161, 3531,
TCP port probe, user-0c938ck.cable.mindspring.com, 24.145.161.148, 4158,3531,
TCP port probe, 24.145.161.148, 24.145.161.148, 4159, 3531
UDP port probe, 24.145.161.148, 24.145.161.148, , 69, 3531
TCP port probe, 24.145.161.148, 24.145.161.148, 4159, 3531
UDP port probe, 129.15.82.91, 129.15.82.91, 69, 3531,
SubSeven port probe, 65.239.151.132, 65.239.151.132, 1201, 27374,
TCP port probe, 80.253.125.30, 80.253.125.30, 1409, 6588,
SOCKS port probe, 80.253.125.30, 80.253.125.30, 1408, 1080,
SQL port probe, aj.cpe.mvllo.al.charter.com, 24.196.11.66, 3210, 1433,
TCP port probe, 202.67.70.174, 202.67.70.174, 1521, 2293,
TCP port probe, 80.253.125.30, 80.253.125.30, 1899, 6588,
SOCKS port probe, 80.253.125.30, 80.253.125.30, 1896, 1080,
TCP port probe, 202.67.70.174, 202.67.70.174, 1416, 2293,