• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Would someone who has Comcast do a tracert for me?

techs

Lifer
If you know how to look up you own i.p. would you do a tracert anywhere and see if your first jump is to an i.p. with the same first 2 numbers as yours or to another?
I am trying to find out if its normal to have an ip of 75.xxx and have the first jump go to 73.xxx
thanks
 
IP: 69.137.XXX.XXX


Tracing route to www.l.google.com [64.233.161.99]

over a maximum of 30 hops:



1 1 ms <1 ms <1 ms 192.168.1.1

2 * * * Request timed out.

3 8 ms 8 ms 9 ms ge-1-18-ur02.gambrills.md.bad.comcast.net [68.86.255.229]

4 10 ms 9 ms 7 ms te-9-1-ur01.gambrills.md.bad.comcast.net [68.87.129.17]

5 8 ms 9 ms 10 ms te-7-1-ar01.capitolhghts.md.bad.comcast.net [68.87.129.22]

6 8 ms 8 ms 9 ms po-90-ar02.capitolhghts.md.bad.comcast.net [68.86.252.214]

7 11 ms 11 ms 12 ms COMCAST-IP.edge1.Washington1.Level3.net [4.79.231.10]

8 10 ms 11 ms 9 ms xe-11-1-0.edge1.Washington1.Level3.net [4.79.231.9]

9 9 ms 28 ms 11 ms GOOGLE-INC.edge1.Washington1.Level3.net [4.79.228.38]

10 10 ms 9 ms 9 ms 64.233.175.171

11 16 ms 12 ms 14 ms 216.239.48.190

12 10 ms 11 ms 16 ms od-in-f99.google.com [64.233.161.99]



Trace complete.





Pinging www.l.google.com [64.233.161.99] with 32 bytes of data:



Reply from 64.233.161.99: bytes=32 time=13ms TTL=244

Reply from 64.233.161.99: bytes=32 time=10ms TTL=244

Reply from 64.233.161.99: bytes=32 time=10ms TTL=244

Reply from 64.233.161.99: bytes=32 time=10ms TTL=244



Ping statistics for 64.233.161.99:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 10ms, Maximum = 13ms, Average = 10ms

 
for those that don't know how, you can go to Start -> Run (or Start button + R key) type cmd hit enter while in the command prompt type ipconfig to get your IP address if the number starts with 192.168 then you're behind a router so check from within your router's settings page, probably under status or use http://www.ipchicken.com/.

then you can type tracert www.google.com > trace.txt
and
ping www.google.com > ping.txt to save your ping and trace routes to text files.
 
Originally posted by: EliteXen
for those that don't know how, you can go to Start -> Run (or Start button + R key) type cmd hit enter while in the command prompt type ipconfig to get your IP address if the number starts with 192.168 then you're behind a router so check from within your router's settings page, probably under status or use http://www.ipchicken.com/.

then you can type tracert www.google.com > trace.txt
and
ping www.google.com > ping.txt to save your ping and trace routes to text files.

Hmm. Your first jump (past your router) timed out. Would you mind trying again?
Much thanks.

 
I've noticed my first hops always time out on my comcast connections in multiple locations that i use comcast. It shouldn't matter
my IP: 76.20.XXX.XXX
Tracing route to www.l.google.com [74.125.19.147]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.10.1
2 8 ms 10 ms 9 ms 73.77.128.1
3 10 ms 9 ms * ge-3-1-ur01.stockton.ca.stockton.comcast.net [68
.87.202.205]
4 * * 10 ms te-9-4-ar01.stockton.ca.stockton.comcast.net [68
.87.202.9]
5 13 ms 12 ms 11 ms te0-7-0-0-ar01.sfsutro.ca.sfba.comcast.net [68.8
6.90.154]
6 * 14 ms 14 ms COMCAST-IP.edge1.SanJose1.Level3.net [4.79.43.13
8]
7 77 ms 13 ms 16 ms xe-11-0-0.edge1.SanJose1.Level3.net [4.79.43.137
]
8 48 ms 224 ms 231 ms ae-12-69.car2.SanJose1.Level3.net [4.68.18.4]
9 14 ms 14 ms 15 ms GOOGLE-INC.car2.SanJose1.Level3.net [4.79.43.146
]
10 26 ms 17 ms 16 ms 209.85.251.98
11 15 ms 15 ms 13 ms cf-in-f147.google.com [74.125.19.147]

Trace complete.
 
Back
Top