Traceroute to my IP doesn't trace

  • Thread starter Thread starter 4mchennai
  • Start date Start date
  • Replies Replies 2
  • Views Views 2,701

4mchennai

Newbie
Messages
2
Location
NA
ISP
Airtel
Hi

I have used the following site to trace route to my IP it stops at airtel server and doesn't route the request further. Does that mean airtel as an ISP doesn't allow incoming traffic? But how does my BT client works? It reports that my NAT is OK.

Here is the result from Online Traceroute using my IP at that time....

Also https://www.grc.com/x/portprobe=34567 reports that my port is open. So obviously this site is able to connect me

then why is that traceroute or accessing my website from the browser (Using url http://122.xxx.xxx.xxx:34567/) doesn't work ??

Tracing route to 122.xxx.xxx.xxx ...

1 161.58.14.161 (161.58.14.161) 0.416 ms 0.390 ms 0.260 ms
2 ge-1-2-0.378.r01.stngva01.us.wh.verio.net (204.2.127.185) 0.397 ms 0.444 ms 0.323 ms
3 vl-5.r03.stngva01.us.bb.gin.ntt.net (129.250.27.215) 31.211 ms 128.946 ms 4.464 ms
4 xe-4-0-0.r21.asbnva01.us.bb.gin.ntt.net (129.250.2.18) 0.539 ms 0.746 ms 0.678 ms
5 p16-0.sprint.asbnva01.us.bb.gin.ntt.net (129.250.9.54) 0.923 ms 0.616 ms 0.530 ms
6 sl-bb20-dc-10-0-0.sprintlink.net (144.232.20.135) 1.518 ms 2.549 ms 1.628 ms
7 sl-bb26-rly-6-0.sprintlink.net (144.232.20.13) 3.052 ms 2.596 ms 2.713 ms
8 sl-bb24-pen-12-0.sprintlink.net (144.232.20.110) 4.924 ms 4.902 ms 4.837 ms
9 sl-bb27-pen-14-0.sprintlink.net (144.232.16.82) 53.610 ms 20.892 ms 18.953 ms
10 sl-bb21-nyc-2-0.sprintlink.net (144.232.20.96) 6.715 ms 6.632 ms 6.790 ms
11 sl-gw39-nyc-4-0-0.sprintlink.net (144.232.13.56) 6.320 ms 6.381 ms 6.319 ms
12 sl-bhart-6-0.sprintlink.net (160.81.228.74) 285.052 ms 279.239 ms 278.305 ms
13 59.145.11.82 (59.145.11.82) 285.263 ms 278.592 ms 285.132 ms
14 202.56.193.26 (202.56.193.26) 291.238 ms 284.574 ms 288.459 ms
15 ras-Chn-250.227.95.61.airtelbroadband.in (61.95.227.250) 299.529 ms 286.984 ms 281.474 ms
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
 
Do you get incoming/remote connections to your BT client? If yes, then your port is forwarded, traceroute will in no way confirm whether you can be connected to on BT or not, there is no relation between the two.
 
BT Reports NAT is OK. And I am getting healthy DL speeds.What about web server traffic? I have made the same change to add one more port to be forwarded for my webserver on my desktop. That is not working. I can get the router login page when I assign 80 for port forwarding. But not for any other port they simply respond with server not found. (yes I made the server to listen to port for which I have setup forwarding)
 
Back