Hi There

I have a Router VPN Setup using Lan 2 Lan which connects fine. However, I can only Tracert the DNS and not any other PC on the Domains network

Main Network
My Domain Controller is on 192.168.2.5
My SQL Server is on 192.168.2.6
My Draytek Router is on 192.168.2.254 and has DHCP turned off.

Remote users network
Draytek Router 192.168.1.1

Below are the tracert results from Remote network to DC

C:\Users\Name>tracert 192.168.2.5

Tracing route to DC1.vt.local [192.168.2.5]
over a maximum of 30 hops:

1 7 ms <1 ms 1 ms 192.168.1.1
2 20 ms 20 ms 19 ms 192.168.2.254
3 21 ms 20 ms 20 ms dc.vt.local [192.168.2.5]

Trace complete.

Below are the tracert results from Remote network to SQL Server

C:\Users\Name>tracert 192.168.2.6

Tracing route to SQL.vt.local [192.168.2.6]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 20 ms 20 ms 19 ms 192.168.2.254
3 * failes

From the Tracert I can see that the traffic is hitting the DC from Remote users network but failes to hit the SQL server.

Can anyone help as to why this might be?

Any help would be much appreciated.

Thank you.

My guess - Routing configuration or blocked by firewall...

Can you ping 192.168.2.6 from 192.168.2.254? (either by telnet'ing into the router and "IP PING 192.168.2.6", or via "Diagnostics | Ping Diagnostics" in the Web GUI.

Can you ping 192.168.2.254 from 192.168.2.6?

What does Tracert 192.168.1.1 show when issued on 192.168.2.6? ... is there a default gateway configured that sends it to 192.168.2.254 (or a route entry for 192.168.1.0/24)

Thanks for your reply.

I did a tracert from 182.168.2.5 to Remote network and it hopped to 192.168.2.1 instead of 2.254 so it was a routing issue on our DC which I then edited and now I'm able to ping out from main network to the remote networks and also vise versa

Our TPI now works remotely too which is wicked!