Traceroute Timing Out
coleslawyum
Enthusiast - Level 2

I have one particular problem with one of my hosting servers, which just happens to be my main server that I use for my business web site and emails. I ran a traceroute and found out that it times out after 14. I've reset my IP address and it would fix the problem for a few minutes, but then it would timeout again. I am still able to access my web site through a web proxy. Can anyone shed some thoughts about what the problem might be? Thanks.

traceroute results:

traceroute to svaha.com (68.171.210.251), 64 hops max, 52 byte packets

 1  192.168.1.1 (192.168.1.1)  0.714 ms  0.346 ms  0.302 ms

 2  l100.nycmny-vfttp-158.verizon-gni.net (98.113.142.1)  4.312 ms  4.871 ms  4.480 ms

 3  g0-13-2-1.nycmny-lcr-22.verizon-gni.net (130.81.137.40)  8.361 ms  7.484 ms  8.149 ms

 4  ae2-0.ny5030-bb-rtr1.verizon-gni.net (130.81.199.178)  6.877 ms

    ae4-0.ny5030-bb-rtr2.verizon-gni.net (130.81.163.232)  6.580 ms *

 5  0.xe-2-1-1.xl4.iad8.alter.net (152.63.41.169)  16.222 ms

    xe-12-1-1-0.phil-bb-rtr1.verizon-gni.net (130.81.23.59)  9.548 ms  9.881 ms

 6  tengige0-7-4-0.gw1.iad8.alter.net (152.63.35.157)  17.834 ms

    0.xe-3-0-1.xl3.iad8.alter.net (152.63.3.61)  19.905 ms

    0.xe-4-1-3.xl4.iad8.alter.net (152.63.5.141)  15.544 ms

 7  tengige0-4-0-0.gw1.iad8.alter.net (152.63.32.233)  16.635 ms

    tengige0-6-2-0.gw1.iad8.alter.net (152.63.35.141)  16.051 ms

    tengige0-4-4-0.gw1.iad8.alter.net (152.63.33.41)  18.361 ms

 8  * * ash-bb3-link.telia.net (80.91.252.90)  16.680 ms

 9  nyk-bb2-link.telia.net (213.155.134.145)  16.338 ms

    ash-bb4-link.telia.net (213.155.133.232)  15.640 ms

    ash-bb3-link.telia.net (80.91.252.92)  19.912 ms

10  nyk-bb1-link.telia.net (213.155.134.148)  14.210 ms

    nyk-bb1-link.telia.net (213.155.131.238)  14.930 ms

    nyk-bb1-link.telia.net (62.115.138.22)  15.289 ms

11  chi-bb1-link.telia.net (80.91.249.110)  33.242 ms

    chi-bb1-link.telia.net (80.91.247.17)  33.475 ms

    chi-bb1-link.telia.net (62.115.137.59)  34.208 ms

12  chi-b21-link.telia.net (62.115.139.249)  33.184 ms  33.447 ms

    chi-b21-link.telia.net (62.115.139.193)  33.118 ms

13  123net-ic-304910-chi-bb1.c.telia.net (62.115.38.246)  57.044 ms  57.951 ms  59.272 ms

14  138.209.171.68.securenet-server.net (68.171.209.138)  54.233 ms  57.681 ms *

15  * * *

16  * * *

17  * * *

18  * * *

19  * * *

20  * * *

21  * * *

22  * * *

23  * * *

etc…

0 Likes
1 Solution

Correct answers
Re: Traceroute Timing Out
coleslawyum
Enthusiast - Level 2

Thanks so much. I actually contacted my Host and they figured out what it was. My IP was being blocked because of port scanning. If anyone can explain that to me, i would greatly appreciate it. I am unaware of what my computer was doing at the time.

View solution in original post

0 Likes
Re: Traceroute Timing Out
tns2
Community Leader
Community Leader

The timeouts are coming after first going through a major foreign carrier.  Not Verizon.  Probably nothing Verizon can do  about it.

0 Likes
Re: Traceroute Timing Out
coleslawyum
Enthusiast - Level 2

Thanks so much. I actually contacted my Host and they figured out what it was. My IP was being blocked because of port scanning. If anyone can explain that to me, i would greatly appreciate it. I am unaware of what my computer was doing at the time.

0 Likes
Re: Traceroute Timing Out
smith6612
Community Leader
Community Leader
 
@coleslawyum wrote:

Thanks so much. I actually contacted my Host and they figured out what it was. My IP was being blocked because of port scanning. If anyone can explain that to me, i would greatly appreciate it. I am unaware of what my computer was doing at the time.


Port Scanning occurs when an application attempts to search for services by scanning ports repeatably. Port scanning can be mistaken for misconfigured software (for example, SFTP or e-mail clients) trying to obtain a valid connection. Port scanning can also be triggered by vulnerability scanning tools, which often aim to look for open ports on a host that could be exploited.

If you are getting banned repeatably by your host, you may want to just double check any programs you have installed pointing to your host, and make sure there's a restriction in place for how many failed connection attempts to have before giving up. Of course, check your computer for malware, too.

Re: Traceroute Timing Out
coleslawyum
Enthusiast - Level 2

Thank you for the explanation. I'm scanning for malware as I type this. 

0 Likes