VPN trace route

Posted by Jake on Server Fault See other posts from Server Fault or by Jake
Published on 2010-12-30T03:11:52Z Indexed on 2010/12/30 3:55 UTC
Read the original article Hit count: 312

Filed under:

I am inside an Active Directory (AD) domain and trying to trace route to another AD domain at a remote site, but supposedly connected by VPN in between.

the local domain can be accessed at 192.168.3.x and the remote location 192.168.2.x. When I do a tracert, I am suprised to see that the results did not show the intermediate ISP nodes. If I used the public IP of the remote location, then a normal tracert going through every intermediate node would show.

1    <1 ms    <1 ms    <1 ms  192.168.3.1
2     1 ms    <1 ms    <1 ms  192.168.3.254
3     7 ms     7 ms     7 ms  212.31.2xx.xx
4   197 ms   201 ms   196 ms  62.6.1.2xx
5   201 ms   201 ms   210 ms  vacc27.norwich.vpn-acc.bt.net [62.6.192.87]
6   209 ms   209 ms   209 ms  81.146.xxx.xx
7   209 ms   209 ms   209 ms  COMPANYDOMAIN [192.168.2.6]

Can someone explain how does this VPN tunnelling works? Does this mean VPN is technically faster than without?

© Server Fault or respective owner

Related posts about vpn