VPN trace route
- by Jake
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?