Well, as I stated in my very first message, traceroute on a Windows
machine correctly traces all 11 hops to salesforce.com, hence not a
general traceroute issue.
   

On Thu, 15 Apr 2010 16:11:47 -0400 (EDT), Julian Thomas wrote:

   

On Thu, 15 Apr 2010 13:01:40 -0400 (EDT) Hakan wrote:
     

No difference:

[D:\]tracerte -n salesforce.com
traceroute to salesforce.com (204.14.234.33), 30 hops max, 38 byte
packets
1  10.20.30.1  0 ms  0 ms  0 ms
2  192.168.1.1  0 ms  10 ms *
3  * * *
4  * * *
5  * * *

       

That tells us that it's not a DNS issue; just a case of the next stop after 192.168.1.1 not
responding to ICMP packets.
--