Browser

66.109.7.162 (TWC owned node malfunction)

Server is slow when it works, it is often offline completly. 

 

It doesn't show in all sites. It shows in 99%. In fact the only site I found that it doesn't show is google.com.

Here is the trace to google.

Tracing route to www.google.com [172.217.4.228]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 10.0.2.1
2 9 ms 2 ms 2 ms 192.168.0.1
3 20 ms 11 ms 9 ms 142.254.154.117
4 26 ms 22 ms 30 ms ae63.hdbgky0401h.midwest.rr.com [74.128.5.25]
5 13 ms 11 ms 13 ms be30.rcmdkyat01r.midwest.rr.com [65.29.28.110]
6 31 ms 27 ms 28 ms be26.clevohek01r.midwest.rr.com [65.189.140.170]
7 35 ms 36 ms 36 ms bu-ether17.vinnva0510w-bcr00.tbone.rr.com [66.109.6.70]
8 34 ms 34 ms 34 ms 0.ae3.pr0.dca20.tbone.rr.com [107.14.19.160]
9 47 ms 34 ms 35 ms 216.50.76.41
10 35 ms 33 ms 34 ms 207.88.14.190.ptr.us.xo.net [207.88.14.190]
11 36 ms 34 ms 35 ms 207.88.14.165.ptr.us.xo.net [207.88.14.165]
12 42 ms 46 ms 51 ms 216.50.79.62
13 58 ms 53 ms 58 ms 216.239.62.143
14 36 ms 35 ms 83 ms 72.14.236.148
15 43 ms 40 ms 40 ms 108.170.237.42
16 58 ms 65 ms 62 ms 108.170.232.166
17 40 ms 40 ms 40 ms 108.170.243.161
18 45 ms 41 ms 40 ms 108.170.233.85
19 39 ms 40 ms 41 ms ord30s31-in-f4.1e100.net [172.217.4.228]

Trace complete.

 

Here is a trace to pinggoat.com

 

Tracing route to www.pinggoat.com [167.114.156.214]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 10.0.2.1
2 2 ms 4 ms 2 ms 192.168.0.1
3 12 ms 14 ms 9 ms 142.254.154.117
4 24 ms 28 ms 30 ms ae63.hdbgky0401h.midwest.rr.com [74.128.5.25]
5 16 ms 13 ms 11 ms be30.rcmdkyat01r.midwest.rr.com [65.29.28.110]
6 29 ms 31 ms 30 ms be26.clevohek01r.midwest.rr.com [65.189.140.170]
7 41 ms 36 ms 36 ms bu-ether17.vinnva0510w-bcr00.tbone.rr.com [66.109.6.70]
8 35 ms 35 ms 34 ms 0.ae3.pr0.dca20.tbone.rr.com [107.14.19.160]
9 * 2242 ms * 66.109.7.162
10 * * * Request timed out.
11 40 ms 61 ms 40 ms be100-104.nwk-1-a9.nj.us [192.99.146.253]
12 51 ms 48 ms 49 ms be10-1037.bhs-g1-a9.qc.ca [192.99.146.99]
13 48 ms 48 ms 50 ms vl20.bhs-g1-a75.qc.ca [198.27.73.229]
14 50 ms 48 ms 49 ms be50-5.bhs-3b-a9.qc.ca [198.27.73.96]
15 49 ms 47 ms 48 ms dmpro-ca-01.fooservers.com [167.114.156.214]

Trace complete.

 

Here is a trace to www.qperfectdesign.com

 

Tracing route to qperfectdesign.com [23.254.201.204]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 10.0.2.1
2 2 ms 2 ms 2 ms 192.168.0.1
3 12 ms 10 ms 10 ms 142.254.154.117
4 30 ms 29 ms 29 ms ae63.hdbgky0401h.midwest.rr.com [74.128.5.25]
5 14 ms 11 ms 13 ms be30.rcmdkyat01r.midwest.rr.com [65.29.28.110]
6 33 ms 28 ms 43 ms be26.clevohek01r.midwest.rr.com [65.189.140.170]
7 37 ms 36 ms 36 ms bu-ether17.vinnva0510w-bcr00.tbone.rr.com [66.109.6.70]
8 32 ms 36 ms 57 ms 0.ae3.pr0.dca20.tbone.rr.com [107.14.19.160]
9 1679 ms 2219 ms * ge-7-1-6.pr0.chi10.tbone.rr.com [66.109.9.74]
10 * * * Request timed out.
11 * * * Request timed out.
12 63 ms 63 ms 64 ms client-23-238-104-129.hostwindsdns.com [23.238.104.129]
13 60 ms 62 ms 70 ms 192.119.77.7
14 62 ms 64 ms 63 ms client-23-254-201-204.hostwindsdns.com [23.254.201.204]

Trace complete.

 

We have had multiple techs out multiple times and we are told there is no issue. I showed the results to the techs and I was told there was nothing that could be done it was just something I would have to live with. It causes a lot of issues and is unacceptable. 

23 REPLIES 23
Highlighted
Expert

Re: 66.109.7.162 (TWC owned node malfunction)

You have an issue with 2 NAT routers inline... Looks like the one nearest your computer is a Uverse DSL one, lol. Get rid of it

 

Browser

Re: 66.109.7.162 (TWC owned node malfunction)

I don't know how, didn't even know I could. I have serached this. Is there any information available on how to do this?

Expert

Re: 66.109.7.162 (TWC owned node malfunction)

Describe what's between the coax and your computer...

there are apparently 2 routers:

1     1 ms 1 ms 1 ms 10.0.2.1 --- what is this? Looks like a n ex-DSL router
2    2 ms 2 ms 2 ms 192.168.0.1    ---the actual all in one modem router combo

Browser

Re: 66.109.7.162 (TWC owned node malfunction)

Ah, yes on this specific location we have a second router (due to the size of our home we have a second router set up but we have hooked the computer directly to the modem and still have the same issue. 

Why would having 2 routers cause an issue 9 hops away anyway? It has a static ip so it doesn't conflict with other ip configurations.

Browser

Re: 66.109.7.162 (TWC owned node malfunction)

A total network map would look something like this.

 

Coax

Modem / Router combo

  • multiple wireless devices (end users) 
  • Router - ( a few wireless devices, printer & pc) This serves as an access point where other signal doesn't reach.
  • Router - (multiple wireless devices) This serves as an access point where the other 2 routers do not reach.

It doesn't matter where we hook up we have the same issue even if we unhook everything else.

Expert

Re: 66.109.7.162 (TWC owned node malfunction)

ok, I'm sort of seeing the same thing here now:

a tracert to 66.109.7.162 is fine but anything past it kills the ping tme,,, anywhere from 1400+ ms and up.

 

Tracing route to 66.109.7.162 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms DD-WRT [192.168.6.6]
2 1 ms <1 ms <1 ms 192.168.1.1
3 10 ms 9 ms 9 ms 142.254.157.117
4 382 ms 22 ms 22 ms 24.164.114.189
5 10 ms 10 ms 10 ms be20.clhgohcc01r.midwest.rr.com [24.33.103.58]
6 15 ms 14 ms 16 ms be14.clevohek02r.midwest.rr.com [65.29.1.98]
7 16 ms 15 ms 16 ms be25.clevohek01r.midwest.rr.com [65.29.1.32]
8 26 ms 25 ms 24 ms bu-ether17.vinnva0510w-bcr00.tbone.rr.com [66.109.6.70]
9 18 ms 18 ms 23 ms 0.ae3.pr0.dca20.tbone.rr.com [107.14.19.160]
10 18 ms 17 ms 18 ms 66.109.7.162

Trace complete.

 ok, here's mine to that site. Hop 10 is awful

 

Tracing route to client-23-254-201-204.hostwindsdns.com [23.254.201.204]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms DD-WRT [192.168.6.6]
2 1 ms <1 ms <1 ms 192.168.1.1
3 9 ms 8 ms 9 ms 142.254.157.117
4 362 ms 28 ms 18 ms 24.164.114.189
5 11 ms 10 ms 11 ms be20.clhgohcc01r.midwest.rr.com [24.33.103.58]
6 18 ms 15 ms 15 ms be14.clevohek02r.midwest.rr.com [65.29.1.98]
7 18 ms 15 ms 16 ms be25.clevohek01r.midwest.rr.com [65.29.1.32]
8 24 ms 23 ms 23 ms bu-ether17.vinnva0510w-bcr00.tbone.rr.com [66.109.6.70]
9 18 ms 18 ms 19 ms 0.ae1.pr0.dca20.tbone.rr.com [66.109.6.167]
10 1709 ms 2137 ms 1152 ms ge-7-1-6.pr0.chi10.tbone.rr.com [66.109.9.74]
11 * * * Request timed out.
12 * * * Request timed out.
13 60 ms 58 ms 50 ms client-23-238-104-129.hostwindsdns.com [23.238.104.129]
14 51 ms 50 ms 49 ms 192.119.77.7
15 50 ms 51 ms 50 ms client-23-254-201-204.hostwindsdns.com [23.254.201.204]

Trace complete.

this might not be an issue, time to the site isn't bad, just one of the middle hops is slow to return a ping request....

you need to verify you don't have other devices sucking bandwidth or connected to the same site.

also copy and paste the modems signal level and error log pages, don't reset it, need to see real history. go thru only the modems router.

 

Expert

Re: 66.109.7.162 (TWC owned node malfunction)

go into tracert add -w 9999  to it to extend the 3000 ms to 9999, see what the hop past it belongs to. I think it's level 3 and they are throttling TWC traffic again.

 

 

Usage: tracert [-d] [-h maximum_hops] [-j host-list] [-w timeout] target_name

Options:
-d Do not resolve addresses to hostnames.
-h maximum_hops Maximum number of hops to search for target.
-j host-list Loose source route along host-list.
-w timeout Wait timeout milliseconds for each reply.

 

C:\Documents and Settings\HP_Administrator>tracert -w 9999 23.254.201.204

Tracing route to client-23-254-201-204.hostwindsdns.com [23.254.201.204]
over a maximum of 30 hops:

1 2 ms <1 ms <1 ms DD-WRT [192.168.6.6]
2 1 ms <1 ms <1 ms 192.168.1.1
3 18 ms 9 ms 9 ms 142.254.157.117
4 19 ms 21 ms 17 ms 24.164.114.189
5 10 ms 10 ms 10 ms be20.clhgohcc01r.midwest.rr.com [24.33.103.58]
6 10 ms 15 ms 16 ms be14.clevohek02r.midwest.rr.com [65.29.1.98]
7 12 ms 15 ms 15 ms be25.clevohek01r.midwest.rr.com [65.29.1.32]
8 26 ms 22 ms 23 ms bu-ether17.vinnva0510w-bcr00.tbone.rr.com [66.10
9.6.70]
9 19 ms 18 ms 18 ms 0.ae1.pr0.dca20.tbone.rr.com [66.109.6.167]
10 * * * Request timed out.
11 * * * Request timed out.
it's either taking more than 10 seconds or those servers are set to ignore pings...

someone else needs to trace this as we're both routed thru Cleveland.

either NC, Austin or LA... to see if it's a cleveland issue

 

Expert

Re: 66.109.7.162 (TWC owned node malfunction)

do not try to run it thru 2 routers.

 try a public DNS like 8.8.8.8

Browser

Re: 66.109.7.162 (TWC owned node malfunction)

C:\Users\_Quen>tracert -w 9999 www.qperfectdesign.com

Tracing route to qperfectdesign.com [23.254.201.204]
over a maximum of 30 hops:

1 14 ms 1 ms 2 ms 192.168.0.1
2 11 ms 31 ms 10 ms 142.254.154.117
3 105 ms 96 ms 97 ms ae63.hdbgky0401h.midwest.rr.com [74.128.5.25]
4 17 ms 66 ms 14 ms be30.rcmdkyat01r.midwest.rr.com [65.29.28.110]
5 197 ms 103 ms 94 ms be26.clevohek01r.midwest.rr.com [65.189.140.170]
6 109 ms 98 ms 96 ms bu-ether17.vinnva0510w-bcr00.tbone.rr.com [66.109.6.70]
7 105 ms 90 ms 101 ms 0.ae3.pr0.dca20.tbone.rr.com [107.14.19.160]
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 156 ms 98 ms 100 ms client-23-238-104-129.hostwindsdns.com [23.238.104.129]
12 151 ms 140 ms 96 ms 192.119.77.7
13 116 ms 97 ms 97 ms client-23-254-201-204.hostwindsdns.com [23.254.201.204]

Trace complete.

 

I have tried running with 8.8.8.8 and 8.8.4.4 (google public dns)

Both still end up routing through that same ip. I assume it must be the most logical route or even a hardwired outlet to get to the www.