Traceroute Mystery!

n4gix

SOH-CM-2016
For some reason, I've been unable to reach my employer's website (or ftp server) for the past five days: http://eaglesoftdg.com :(

Here is the results of a tracert. As can be seen, it appears to be "blocked" at ADD2NET-INC...

Anyone have any idea what might be the problem?
--------------------------------
Code:
Tracing route to eaglesoftdg.com [67.210.116.65]
over a maximum of 30 hops:
 
  1    <1 ms    <1 ms    <1 ms  Development [192.168.2.1] 
  2    21 ms    23 ms    25 ms  c-98-227-248-1.hsd1.in.comcast.net [98.227.248.1] 
  3     8 ms    10 ms    10 ms  te-2-1-ur02.hammond.in.chicago.comcast.net [68.85.131.77] 
  4    10 ms    10 ms    11 ms  be-80-ar01.area4.il.chicago.comcast.net [68.87.230.153] 
  5    11 ms    10 ms    11 ms  pos-1-11-0-0-cr01.chicago.il.ibone.comcast.net [68.86.95.9] 
  6    10 ms    11 ms    11 ms  xe-9-2-0.edge1.Chicago2.Level3.net [4.71.248.25] 
  7    11 ms    11 ms    11 ms  vlan51.ebr1.Chicago2.Level3.net [4.69.138.158] 
  8    35 ms    35 ms    35 ms  ae-3-3.ebr2.Denver1.Level3.net [4.69.132.61] 
  9    46 ms    35 ms    34 ms  ae-1-100.ebr1.Denver1.Level3.net [4.69.132.37] 
 10    60 ms    53 ms    53 ms  ae-2-2.ebr2.Dallas1.Level3.net [4.69.132.106] 
 11   136 ms   202 ms   200 ms  ae-4-4.car2.SanDiego1.Level3.net [4.69.133.213] 
 12    86 ms    85 ms    85 ms  ADD2NET-INC.car2.SanDiego1.Level3.net [4.53.122.66] 
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 
It's ok from here

Code:
15   182 ms   182 ms   185 ms  ADD2NET-INC.car2.SanDiego1.Level3.net [4.53.122.70]
16   186 ms   187 ms   187 ms  virgo.lunarpages.com [67.210.116.65]
 
Mystery Solved...

I discovered (after a lot of digging!) that ADD2NET-INC own the lunarpages.com servers, where eaglesoftdg.com is hosted.

I opened a support ticket and got a response back last evening that advised me that their system had automatically blocked my IP address because of repeated ftp login failures. They removed the block and I now have access to the website and ftp accounts restored.

<!--StartFragment -->
An FTP block usually takes about 10 login failures from the same IP address in a 300 second (5 minutes) time frame.

I've suggested that they might give some consideration to having the system do an automatic "unblock" after 24 hours, and only enforce a full block requiring manual intervention after two consecutive "events" within a 48 hour period.
 
Back
Top