Should internally routed TCP/IP routes reflect internet travel?

[jwarmuth]

I was testing my vpn and noticed that when I tracert SiteA to SiteB using internal addresses (eg. 192.168.1.50) the route goes onto the public network. I was under assumption that it should go through Site1's VPN router to SiteB's VPN router to the target station and back.

Should be something like..

1 192.168.2.1
2 192.168.1.2
3 192.168.1.123

but it's comes back as this:

I:\>tracert accounting

Tracing route to ACCOUNTING.mydomain.com [192.168.1.123]
over a maximum of 30 hops:

1 32 ms 15 ms 16 ms edtnabxlar02.ab.tac.net [209.115.152.23]
2 16 ms 15 ms 16 ms edtnabxldr01.bb.telus.com [216.123.243.241]
3 <10 ms 31 ms 16 ms edtnabxmgr01.bb.telus.com [205.233.111.139]
4 16 ms 16 ms 31 ms edtnabxmbr01.bb.telus.com [154.11.10.142]
5 15 ms 16 ms 15 ms clgrab31br01.bb.telus.com [154.11.10.150]
6 31 ms 16 ms 15 ms clgrab31gr01.bb.telus.com [154.11.10.170]
7 31 ms 16 ms 15 ms clgrabezdr01.bb.telus.com [208.38.16.129]
8 * 125 ms 172 ms accounting.mydomain.com [192.168.1.123]

Trace complete.


I noticed that it actually travels to another city! Can someone shed light on if this is normal?

This is a Windows 2000 server to Windows 2000 server VPN over DSL in the same city.

Jeff Warmuth
MCSE, CNE
ICQ 129152989