Toshi Esumi wrote:
In your last traceroute, the first hop was "172.16.200.17". But it's not in the vmnet8 subnet:172.16.102.0/24. Is 172.16.200.17 one of IP addresses the SonicWall FW has? Do you have the same problem when you don't run VMWare? (Maybe you already commented this but I don't remember.) What kind of output of "tracert 64.41.140.167" do you get when you run this on a Windows client? Is it exactly the same as the one you posted?
Toshi
172.16.200.17 is not listed in my SonicWall. tracert in VMWare/Windows2k shows: C:\>tracert 64.41.140.167 Tracing route to www.global.sonicwall.com [64.41.140.167] over a maximum of 30 hops: 1 15 ms <10 ms 16 ms 172.16.200.17 2 <10 ms 15 ms <10 ms vtelinet-216-66-108-205.vermontel.net [216.66.10 8.205] 3 16 ms 15 ms 16 ms g11-2.core01.bos01.atlas.cogentco.com [38.112.23 .169] 4 16 ms 31 ms 16 ms p5-0.core01.jfk02.atlas.cogentco.com [66.28.4.11 8] 5 16 ms 31 ms 31 ms p4-0.core02.dca01.atlas.cogentco.com [66.28.4.81 ] 6 31 ms 32 ms 31 ms p14-0.core01.iad01.atlas.cogentco.com [154.54.2. 198] 7 94 ms 31 ms 16 ms cpr1-ge-8-1.VirginiaEquinix.savvis.net [208.173. 10.181] 8 31 ms 32 ms 31 ms dcr1-so-6-1-0.Washington.savvis.net [208.173.52. 114] 9 32 ms 31 ms 47 ms bcs2-so-5-0-0-500.Washington.savvis.net [204.70. 192.174] 10 93 ms 94 ms 94 ms dcr1-so-5-0-0.SanFranciscosfo.savvis.net [204.70 .192.149] 11 94 ms 94 ms 94 ms bhr1-pos-13-0.SantaClarasc5.savvis.net [208.172. 147.110] 12 93 ms 94 ms 94 ms csr1-ve242.sc4.savvis.net [216.34.2.243] 13 * * * Request timed out. 14 * * * Request timed out. 15 * * * Request timed out. 16 * * * Request timed out. 17 * * * Request timed out. 18 * * * Request timed out. 19 * * * Request timed out. 20 * * * Request timed out. 21 * * * Request timed out. 22 * * * Request timed out. 23 * * * Request timed out. 24 * * * Request timed out. 25 * * * Request timed out. 26 * * * Request timed out. 27 * * * Request timed out. 28 * * * Request timed out. 29 * * * Request timed out. 30 * * * Request timed out. Trace complete. James W