Traceroutes aren't successful
Where would we be able to allow traceroutes? We keep getting a "Request timed out" error every time it gets past the local router.
Anuroopsundd
can you try pathping yahoo.com
ASKER
Anuroopsundd,
I learn something new everyday. I'd never even heard of pathping before. This is the end result:
I learn something new everyday. I'd never even heard of pathping before. This is the end result:
Do you have a proxy?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
It is most probably that their provider is not allowing the response to the route..
if you see response is coming back from the last Hop when it reaches the destination (google).
if it was with their firewall then the response should not have come back from google at last hop.
and google.com server seems to be their very near to the provider.. see response time of 28ms..
below sites are in india so have to leave your provider.
can you try ... tracert timesofindia.com
or google.co.in
if you see response is coming back from the last Hop when it reaches the destination (google).
if it was with their firewall then the response should not have come back from google at last hop.
and google.com server seems to be their very near to the provider.. see response time of 28ms..
below sites are in india so have to leave your provider.
can you try ... tracert timesofindia.com
or google.co.in
ASKER
These are the new tracert results. Same as the other ones: 
Yep, the last response differs from the intermediate because there is no 'time exceed' there :)
Still could be a firewall, be it at the provider or local (the 10.20.1.1 perhaps?).
Still could be a firewall, be it at the provider or local (the 10.20.1.1 perhaps?).
ASKER
Pinging the "india" address got me nowhere so I when to the browser & typed it in. It gave me "http://timesofindia.indiatimes.com/" so I traceroute that. Same result: 
We do have a Barracuda Web Filter 610 in place to filter traffic coming in & going out. My computer has been placed on an exempt list so it's not suppose to block ANY traffic coming or going but I'm not sure about it blocking TTL packets.
We do have a Barracuda Web Filter 610 in place to filter traffic coming in & going out. My computer has been placed on an exempt list so it's not suppose to block ANY traffic coming or going but I'm not sure about it blocking TTL packets.
the result for India server are also from akamai server. .that means.. local replica server in your location.. which even the 13ms tells us....
one more tracet to ip below..
tracert 203.101.83.197
tracert 59.163.16.5
tracert 122.160.220.72
one more tracet to ip below..
tracert 203.101.83.197
tracert 59.163.16.5
tracert 122.160.220.72
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Earlier stated tracert attempts: 
rigan123,
whatismyip.com stated that I don't have a proxy (which is what I figured). I've tried the http://lg.level3.net/traceroute/traceroute.cgi site twice & these are my results:
It looks like it could be the ISP.
rigan123,
whatismyip.com stated that I don't have a proxy (which is what I figured). I've tried the http://lg.level3.net/traceroute/traceroute.cgi site twice & these are my results:
It looks like it could be the ISP.
yes, seems your isp is blocking the UDP ports 33434-33534
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
C:\Users\sundd>tracert 66.195.246.226
Tracing route to mail.southaven.org [66.195.246.226]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms MYWIRELESS [x.x.X.X]
2 2 ms 2 ms 4 ms 10.0.0.1
3 33 ms 40 ms 42 ms X.X.x.x.
4 3058 ms 2913 ms 2813 ms x.x.x.x
5 29 ms 27 ms 28 ms 203.101.83.197
6 270 ms 267 ms 269 ms 125.62.187.126
7 276 ms 326 ms 276 ms las-b3-link.telia.net [213.248.98.237]
8 * 264 ms 264 ms las-bb1-link.telia.net [213.155.130.124]
9 * * * Request timed out.
10 336 ms 331 ms 398 ms mem1-ar3-ge-0-0-0-0.us.twt
.186]
11 338 ms 340 ms 338 ms mail.southaven.org [66.195.246.226]
Trace complete.
i am also able to reach.......
Tracing route to mail.southaven.org [66.195.246.226]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms MYWIRELESS [x.x.X.X]
2 2 ms 2 ms 4 ms 10.0.0.1
3 33 ms 40 ms 42 ms X.X.x.x.
4 3058 ms 2913 ms 2813 ms x.x.x.x
5 29 ms 27 ms 28 ms 203.101.83.197
6 270 ms 267 ms 269 ms 125.62.187.126
7 276 ms 326 ms 276 ms las-b3-link.telia.net [213.248.98.237]
8 * 264 ms 264 ms las-bb1-link.telia.net [213.155.130.124]
9 * * * Request timed out.
10 336 ms 331 ms 398 ms mem1-ar3-ge-0-0-0-0.us.twt
.186]
11 338 ms 340 ms 338 ms mail.southaven.org [66.195.246.226]
Trace complete.
i am also able to reach.......
ASKER
The .226 address refers to our externally facing Cisco ASA firewall interface. 66.195.246.225 is our default gateway (TWTelecom switch).
Your gateway(ISP) may have multiple IP assigned ,multiple interfaces and multiple gateways.So, you need to contact to them.
ASKER
Thanks for all the help. The problem has been solved. Our firewall was blocking ICMP so traceroutes & pings weren't always going through.