From: m@rtij.nl.invlalid   
      
   On Fri, 13 Aug 2010 12:40:10 -0400, Jim Mack wrote:   
      
   >   Trace 2.2.2.134   
   >   
   >    1 192.168.1.1      (m0n0wall.internal ok) -------   
   >   12 154.54.40.190    (te0-1-0-4.ccr21.ord01...isp) 13 154.54.31.21   
   >   (te3-2.ccr01.dtw04...isp) 14 38.112.37.82   
   >   (vl3501.na31.b020673-1.dtw04...isp) 15   No Response   
   >   
   > What that seems to say is that the route from 2.2.2 to 1.1.1 is missing,   
   > because 1.1.1 should be reached on any request for a 2.2.2 address.   
   >   
   > Or am I misinterpreting what traceroute is telling me?   
      
   Yes, you are misinterpreting. It means no response is received, nothing   
   more, nothing less. There can be many reasons for that, but the most   
   common is that hop 14 does not have a correct route to hop 15, or hop 15   
   has no correct route to hop 14 for the response.   
      
   I personally would fire up a lan-sniffer to see what is happening, it is   
   often the quickest way to diagnose such problems.   
      
   HTH,   
   M4   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)