jimboyle1981
asked on
Unable to traceroute using Draytek Vigor 2820
Hi everyone,
I have a problem I was hoping someone can help me with please, we have 2 offices, with a Draytek Vigor 2820 router installed at each office. Each has a static IP Address
I have configured a LAN > LAN connection between the routers. This shows as connected under Connection Management.
The LAN > LAN connection is an IPSec Tunnel with 3DES_SHA1 Auth
Network 1 Router IP is 192.168.1.1
Network 2 Router IP is 10.10.30.1
Staff in both offices can access the Internet Ok,
I can ping internal addresses on both networks from the Draytek ping utility on the router config page but I am unable to trace to any of the addresses, does anyone have any ideas what this could be.
If I even try and trace to the routers own address from the routers config page, I get the following:
traceroute to 10.10.30.1, 30 hops max through WAN1 protocol ICMP
1 Request timed out. *
2 Request timed out. *
Trace complete.
I am really stuck with this one.
Thanks.
I have a problem I was hoping someone can help me with please, we have 2 offices, with a Draytek Vigor 2820 router installed at each office. Each has a static IP Address
I have configured a LAN > LAN connection between the routers. This shows as connected under Connection Management.
The LAN > LAN connection is an IPSec Tunnel with 3DES_SHA1 Auth
Network 1 Router IP is 192.168.1.1
Network 2 Router IP is 10.10.30.1
Staff in both offices can access the Internet Ok,
I can ping internal addresses on both networks from the Draytek ping utility on the router config page but I am unable to trace to any of the addresses, does anyone have any ideas what this could be.
If I even try and trace to the routers own address from the routers config page, I get the following:
traceroute to 10.10.30.1, 30 hops max through WAN1 protocol ICMP
1 Request timed out. *
2 Request timed out. *
Trace complete.
I am really stuck with this one.
Thanks.
Tracert uses ICMP Ping across each hop in the path. Any hop that will not respond times out, as above. Some hops will not respond to ping, perhaps because of firewall rules. Any device that you are able to ping should respond to tracert. But, if there are any hops in the path that won't respond to ping, they will time out.
ASKER
Thanks for the info, but IP Addresses I can ping Ok I cannot trace to, as you can see below:
Pinging 10.0.1.5 with 64 bytes of Data:
Receive reply from 10.0.1.5, time=100ms
Receive reply from 10.0.1.5, time=100ms
Receive reply from 10.0.1.5, time=120ms
Receive reply from 10.0.1.5, time=100ms
Receive reply from 10.0.1.5, time=100ms
Packets: Sent = 5, Received = 5, Lost = 0 (0% loss)
traceroute to 10.10.30.1, 30 hops max through WAN1 protocol ICMP
1 Request timed out. *
2 Request timed out. *
Trace complete.
Still struggling with this.
Pinging 10.0.1.5 with 64 bytes of Data:
Receive reply from 10.0.1.5, time=100ms
Receive reply from 10.0.1.5, time=100ms
Receive reply from 10.0.1.5, time=120ms
Receive reply from 10.0.1.5, time=100ms
Receive reply from 10.0.1.5, time=100ms
Packets: Sent = 5, Received = 5, Lost = 0 (0% loss)
traceroute to 10.10.30.1, 30 hops max through WAN1 protocol ICMP
1 Request timed out. *
2 Request timed out. *
Trace complete.
Still struggling with this.
Alright, I don't know your equipment, but would you have tracert blocked at some point? For example:
access-list 101 deny icmp any any traceroute
Or, in some cases, it might be done through a GUI.
Sorry I can't be more help...
access-list 101 deny icmp any any traceroute
Or, in some cases, it might be done through a GUI.
Sorry I can't be more help...
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.