On 9/5/05, beeplove <[EMAIL PROTECTED]> wrote: > I am not familiar with tcptraceroute.
It works just like the regular traceroute, but instead of sending UDP or ICMP packets with increasing TTLs, it sends a TCP SYN packet to the port you specify. > Say, Host A is able to reach at domain:80 but host B is not. > Would tcptraceroute be able to detect host B couldn't reach at > domain:80 because of some route issue of its parent network, not by > the firewall of domain:80? It's impossible to be sure. If the trace from host B terminates at a node very near to the target domain, say right on the target host or just before it, you can say with some confidence that the target has firewalled you. But this is not an undeniable proof. Like you said, routing issues both in the forward and reverse path can be the cause. -- Mojahed ------------------------ Yahoo! Groups Sponsor --------------------~--> Get fast access to your favorite Yahoo! Groups. Make Yahoo! your home page http://us.click.yahoo.com/dpRU5A/wUILAA/yQLSAA/hYOolB/TM --------------------------------------------------------------------~-> To unsubscribe send a blank mail to: [EMAIL PROTECTED] Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/bdlug/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
