Hi,
My client is having issues connecting to a specific web site, though the site itself is fine for me. It is a site he has been able to access perfectly well for some time. All users in this LAN have the same issues and I have flushed the DNS on all PC's, servers and routers. That is about as far as I can go as my understanding of network troubleshooting doesn't go very far beyond ping!
I have performed a traceroute from several internet based servers, all give me success as they find the web site, but when I perform a traceroute from inside the clients LAN it tijes out at a given IP address.
This is an example of a good traceroute from outside the clients LAN:
Tracing route to circuitlinksupport.com.au [216.67.224.50] over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.0.245
2 14 ms 14 ms 15 ms anchor-hg-1-lo100.router.d
emon.net [194.159.161.32]
3 14 ms 13 ms 13 ms anchor-access-3-s153.route
r.demon.ne
t [194.159.161.97]
4 15 ms 13 ms 14 ms anchor-inside-3-g2-0-2.rou
ter.demon.
net [194.159.161.70]
5 15 ms 15 ms 16 ms park-border-1-g4-0-0.route
r.demon.ne
t [194.70.98.106]
6 16 ms 15 ms 14 ms ge-6-18.car1.London2.Level
3.net [212.187.160.125]
7 25 ms 28 ms 17 ms ae-31-51.ebr1.London2.Leve
l3.net [4.68.117.30]
8 15 ms 16 ms 15 ms ae-1-100.ebr2.London2.Leve
l3.net [4.69.132.122]
9 24 ms 16 ms 17 ms ae-2.ebr1.London1.Level3.n
et [4.69.132.146]
10 17 ms 14 ms 16 ms ae-1-100.ebr2.London1.Leve
l3.net [4.69.132.118]
11 87 ms 85 ms 88 ms ae-43.ebr1.NewYork1.Level3
.net [4.69.137.74]
12 88 ms 88 ms * ae-2.ebr1.Newark1.Level3.n
et [4.69.132.98]
13 * 87 ms 87 ms ae-14-55.car4.Newark1.Leve
l3.net [4.68.99.136]
14 92 ms 91 ms 91 ms WBS-CONNECT.car4.Newark1.L
evel3.net [4.71.148.26]
15 90 ms 90 ms 100 ms 208.116.63.254
16 * 89 ms 91 ms server6.ezbudgethosting.co
m [216.67.224.50]
Trace complete.
And this is an example of the bad one from inside the LAN:
Tracing route to circuitlinksupport.com.au [216.67.224.50] over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.0.245
2 27 ms 26 ms 33 ms anchor-hg-4-lo100.router.d
emon.net [194.159.161.35]
3 27 ms 29 ms 27 ms anchor-access-4-s156.route
r.demon.ne
t [194.159.161.193]
4 29 ms 27 ms 26 ms anchor-inside-4-g6-0-4.rou
ter.demon.
net [194.159.161.94]
5 30 ms 29 ms 27 ms park-border-1-g4-0-0.route
r.demon.ne
t [194.70.98.106]
6 29 ms 28 ms 29 ms ge-6-18.car1.London2.Level
3.net [212.187.160.125]
7 29 ms 37 ms 35 ms ae-32-52.ebr2.London2.Leve
l3.net [4.68.117.62]
8 31 ms 30 ms 35 ms ae-2.ebr1.London1.Level3.n
et [4.69.132.146]
9 30 ms 30 ms 37 ms ae-1-100.ebr2.London1.Leve
l3.net [4.69.132.118]
10 104 ms 111 ms 108 ms ae-42.ebr1.NewYork1.Level3
.net [4.69.137.70]
11 106 ms 111 ms 106 ms ae-2.ebr1.Newark1.Level3.n
et [4.69.132.98]
12 98 ms 100 ms 98 ms ae-14-55.car4.Newark1.Leve
l3.net [4.68.99.136]
13 103 ms 103 ms 103 ms WBS-CONNECT.car4.Newark1.L
evel3.net [4.71.148.26]
14 102 ms 109 ms 103 ms 208.116.63.254
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete.
So, does this mean the problem is with the server where the traceroute times out, is it a problem inside my clients LAN, or is it a bit of both?
Looking forward to learning something today :-)
Start Free Trial
