Blocked IP

[costm]

Hi,

a lot of my customers can´t access my internet server, all of them have Verizon as IPS. The problem seems to be a block of ip in the Verizon network. This is the trace:

and so on...

C:\Users\Administrator>tracert 46.166.137.125

Tracing route to 46.166.137.125 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.112.1
2 21 ms 21 ms 21 ms l221.bos-dsl-rtr9.verizon-gni.net [71.243.123.1]

3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.

Can someone explain me why the ip is blocked? What i do for unlock my server?

Thanks

Marco Costella

[dslr595148]

#1 I went to

http://network-tools.com/ 

#2 I selected Network Lookup.

#3 I typed in OR copied in that IP Address.

#4 After I pressed Go, I got info back,

#5 By looking at that info..

That IP Address is not owned by Verizon.

It is owned by Santrex US VPS Services.

---

As to why they are not allowing ping / trace route through, see the info that I found by going to

http://www.grc.com/sn/sn-313.htm

OR

http://www.grc.com/sn/sn-313.txt

OR

http://www.grc.com/sn/sn-313.pdf

--

As how to get access to that /those servers, I believe you would have to contact that ISP/company.

I beleve, they will be able to help you better.

[costm]

Hi,

sure the ip is not owned by verizon, the ip is my and the vedor is santrex. Look my trace in previus poist, that is the ip of verizon that block the trace. From no verizon connection the server works fine and the tracert to. In the trace of http://network-tools.com/ there are no verizon server and work fine too. 

[costm]

additional information: vereizon don't block the trace, this is the trace of santrex:

Tracing route to www.santrex.net [94.242.203.61]over a maximum of 30 hops:
  1    <1 ms    <1 ms    <1 ms  192.168.112.1  2     *       67 ms    83 ms  l221.bos-dsl-rtr9.verizon-gni.net [71.243.123.1]
  3    98 ms   115 ms   101 ms  so-0-3-0-0.bos-core-rtr1.verizon-gni.net [130.81.4.201]  4    60 ms   116 ms    86 ms  so-0-2-0-0.bos-bb-rtr1.verizon-gni.net [130.81.20.84]  5   122 ms   103 ms    32 ms  0.so-0-2-0.xl3.bos4.alter.net [152.63.16.137]  6    29 ms    30 ms    29 ms  0.xe-6-1-2.XL3.NYC4.ALTER.NET [152.63.0.166]  7     *      117 ms   155 ms  gigabitethernet4-0-0.gw1.nyc4.alter.net [152.63.20.97]  8   122 ms   115 ms   110 ms  teliasonera-gw.customer.alter.net [157.130.60.14]  9   141 ms   135 ms   146 ms  nyk-bb2-link.telia.net [213.155.130.244] 10   226 ms   347 ms   225 ms  prs-bb2-link.telia.net [80.91.251.101] 11   183 ms   184 ms   187 ms  prs-b5-link.telia.net [213.155.130.23] 12   208 ms   213 ms   208 ms  rootsa-ic-141100-prs-b5.c.telia.net [213.248.95.182] 13   195 ms   300 ms   214 ms  40g.par-lxb.as5577.net [83.243.12.13] 14   245 ms   192 ms   459 ms  80g.r2-r1.lxb.as5577.net [83.243.12.17] 15   200 ms   214 ms   216 ms  ic-root.lxb.as5577.net [83.243.15.250] 16   257 ms   160 ms   238 ms  home.lu.santrex.net [212.117.169.224] 17   246 ms   253 ms   199 ms  santrex.net [94.242.203.61]
Trace complete.

[smith6612]

Hard to say what the issue is, but this could be a block from someone who used to own your server's IP address before causing some abuse, or it could be the more likely case of a bad routing table somewhere. I'm seeing the same trace issue as you are; failing to get past the Verizon edge router.