
Posted: Mon Jan 10, 2005 4:06 pm
Well, he either set up a script or he's just some anal kid with nothing better to do?
It's a different IP this time, and rather interesting. Hreere's the details:
++++++++++++++++++++++++++++++++++++++++++
01/10/05 11:01:35 IP block 155.252.241.112
Trying 155.252.241.112 at ARIN
Trying 155.252.241 at ARIN
OrgName: NFEC
OrgID: NFEC-2
Address: Washington Navy Yard
Address: 1322 Patterson Avenue
Address: Suite 1000
City: Washington
StateProv: DC
PostalCode: 20374-5065
Country: US
NetRange: 155.252.0.0 - 155.252.255.255
CIDR: 155.252.0.0/16
NetName: NAVFAC-1
NetHandle: NET-155-252-0-0-1
Parent: NET-155-0-0-0-0
NetType: Direct Assignment
NameServer: NAVFACDNS.NAVFAC.NAVY.MIL
NameServer: NAVFACDNS2.NAVFAC.NAVY.MIL
Comment:
RegDate:
Updated: 2004-09-07
TechHandle: MP359-ARIN
TechName: Pineda, Marino
TechPhone: +1-805-982-2651
TechEmail: PINEDAMS@nitc.navfac.navy.mil
OrgTechHandle: MP359-ARIN
OrgTechName: Pineda, Marino
OrgTechPhone: +1-805-982-2651
OrgTechEmail: PINEDAMS@nitc.navfac.navy.mil
# ARIN WHOIS database, last updated 2005-01-09 19:10
# Enter ? for additional hints on searching ARIN's WHOIS database.
+++++++++++++++++++++++++++++++++++++
Maybe the Navy should be told about this?
As far as the FCC, I doubt they're interested. If the true originating IP can be found, they might be convince to terminate the person's service. A minor inconvenience at leat. After that, I think it takes personal legal action... But there might be an organisation that would be interested? But since I'm just a member here, there's not much I can do about it except 'complain'
Okay, since he used a US government military server to do his latest damage, I thought I'd ask the military for some help

We'll see if I get anything more than a stock reply...
<font size=-1>[ This Message was edited by: RichS on 2005-01-10 08:14 ]</font>