Browse but not trace 1

[MasterRacker]

I have a web address for a surveillance system that I can browse to for viewing however a traceroute goes 14 hops then can't find anything after. I can't ping the address either. I know you can configure a device to not respond to pings and I assume that's what going on there - could that be blocking the trace as well?

Jeff
[small][purple]It's never too early to begin preparing for [/purple]International Talk Like a Pirate Day
"The software I buy sucks, The software I write sucks. It's time to give up and have a beer..." - Me[/small]

 

[james1982]

yes I suspect that is the case.
The ping request is potentially getting as far as there router and then failing.
Do you know the router address? Try pinging this

 

[MasterRacker]

No I don't.

I'm not worried about the ping anyway. I was just curious about the fact that I could browse to the site but not trace the route fully.

Jeff
[small][purple]It's never too early to begin preparing for [/purple]International Talk Like a Pirate Day
"The software I buy sucks, The software I write sucks. It's time to give up and have a beer..." - Me[/small]

 

[Noway2]

If there is a device in the chain that is set to not respond to ICMP traffic, which seems to be a common default setting on most routers (at least home variety ones) this will cause traceroute to stop at that node.

 

[MasterRacker]

I figured it was something like that. Thanks.

Jeff
[small][purple]It's never too early to begin preparing for [/purple]International Talk Like a Pirate Day
"The software I buy sucks, The software I write sucks. It's time to give up and have a beer..." - Me[/small]

 

[james1982]

Well explained Noway2 - thats basically what I was getting at