US Cable Support > Comcast HSI > [Connectivity] Can't get to one site, Comcast won't help

reply to baineschile

Re: [Connectivity] Can't get to one site, Comcast won't help

my tracert is the same as yours but I am able to see the site.

reply to sirchief
Here is what I see for traceroute results from both my Comcast connection and from my backup AT&T DSL connection:

C:\>use-comcast
 
Pinging 192.168.9.10 with 32 bytes of data:
 
Reply from 192.168.9.10: bytes=32 time<1ms TTL=64
 
Ping statistics for 192.168.9.10:
    Packets: Sent = 1, Received = 1, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms
 
C:\>route change 0.0.0.0 mask 0.0.0.0 192.168.9.10 metric 10
You are now using the Comcast Business Class connection!
 
C:\>tracert myartslab.com
 
Tracing route to myartslab.com [159.182.16.51]
over a maximum of 30 hops:
 
  1    <1 ms    <1 ms    <1 ms  ap2.dcs-net [192.168.9.10]
  2     1 ms    <1 ms    <1 ms  host6.dcs-net.net [75.146.8.46]
  3    36 ms    40 ms    57 ms  96.191.160.1
  4    10 ms     9 ms     9 ms  xe-4-0-0-0-sur02.murfreesboro.tn.nash.comcast.net [68.85.50.129]
  5    11 ms    11 ms    11 ms  xe-5-1-3-0-ar01.goodslettvll.tn.nash.comcast.net [68.86.176.105]
  6    20 ms    18 ms    19 ms  pos-2-1-0-0-cr01.atlanta.ga.ibone.comcast.net [68.86.90.101]
  7    34 ms    35 ms    86 ms  pos-4-2-0-0-cr01.ashburn.va.ibone.comcast.net [68.86.87.65]
  8    32 ms    32 ms    45 ms  pos-0-5-0-0-pe01.ashburn.va.ibone.comcast.net [68.86.87.14]
  9    34 ms    67 ms   218 ms  er2-tengig3-2.virginiaequinix.savvis.net [208.173.52.125]
 10    33 ms    34 ms    33 ms  cr2-tengig0-7-3-0.washington.savvis.net [204.70.197.246]
 11    42 ms    40 ms    42 ms  cr1-tengig-0-15-0-0.NewYork.savvis.net [204.70.196.117]
 12    41 ms    39 ms    41 ms  hr1-te-8-1-0.NewJerseynj2.savvis.net [204.70.197.14]
 13    42 ms    40 ms    40 ms  das12-v3018.nj2.savvis.net [64.15.236.102]
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 18  ^C
 
C:\>use-att
 
Pinging 192.168.1.254 with 32 bytes of data:
 
Reply from 192.168.1.254: bytes=32 time=18ms TTL=253
 
Ping statistics for 192.168.1.254:
    Packets: Sent = 1, Received = 1, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 18ms, Maximum = 18ms, Average = 18ms
 
C:\>route change 0.0.0.0 mask 0.0.0.0 192.168.9.9 metric 10
You are now using the Windcrest AT&T backup connection!
 
C:\>tracert myartslab.com
 
Tracing route to myartslab.com [159.182.16.51]
over a maximum of 30 hops:
 
  1    <1 ms    <1 ms    <1 ms  ps1.dcs-net [192.168.9.9]
  2     4 ms     3 ms     3 ms  gw4.dcs-net [192.168.8.254]
  3    15 ms    18 ms    33 ms  192.168.1.254
  4   154 ms   150 ms   105 ms  adsl-98-87-54-1.bna.bellsouth.net [98.87.54.1]
  5     *        *       54 ms  70.159.210.120
  6    41 ms    35 ms    39 ms  70.159.210.122
  7    46 ms    36 ms    36 ms  70.159.210.119
  8    38 ms    49 ms    39 ms  12.81.32.52
  9    42 ms    33 ms    34 ms  12.81.32.47
 10    35 ms    34 ms    34 ms  74.175.192.134
 11    45 ms    60 ms    48 ms  cr1.nsvtn.ip.att.net [12.122.148.14]
 12    49 ms    46 ms    49 ms  cr2.attga.ip.att.net [12.122.28.105]
 13    44 ms    41 ms    42 ms  attga03jt.ip.att.net [12.122.84.41]
 14    42 ms    41 ms    50 ms  208.173.60.237
 15    45 ms    44 ms    43 ms  cr2-te-0-0-0-0.atlanta.savvis.net [204.70.200.2]
 16    66 ms    64 ms    68 ms  cr1-bundle-pos1.NewYork.savvis.net [204.70.196.137]
 17    61 ms    61 ms     *     hr1-te-8-1-0.NewJerseynj2.savvis.net [204.70.197.14]
 18    61 ms    61 ms    61 ms  das12-v3017.nj2.savvis.net [64.15.236.98]
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22  ^C
 
C:\>use-comcast
 
Pinging 192.168.9.10 with 32 bytes of data:
 
Reply from 192.168.9.10: bytes=32 time<1ms TTL=64
 
Ping statistics for 192.168.9.10:
    Packets: Sent = 1, Received = 1, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms
 
C:\>route change 0.0.0.0 mask 0.0.0.0 192.168.9.10 metric 10
You are now using the Comcast Business Class connection!
 
 

reply to sirchief
The problem shows up here

9 11 ms 10 ms 11 ms das12-v3018.nj2.savvis.net [64.15.236.102]
10 * * * Request timed out.

The timeout at line 10 indicates the data packets are NOT being routed correctly by 64.15.236.102.
The systen sees the destination IP of the packet, but doesn't have the correct routing table information to pass it on.
Once the packet exceeeds it's TTL(Time To Live), it gets dumped out of buffer.
The only person/persons who can correct this is the sysadmin for savvis.net .
Given enough time, the net will 'discover" a new routing path between the originating IP and the destination IP

Hi, I was having the same exact problem as you but from a completely different state- California. All computers on the network could not connect to myartslab. However, upon removing the router and direct connecting to he modem, the problem wen away. If you're still having problems connecting and see this message, you can try removing your router, if there is one. (posting this from and iPad, so sorry for autocorrect mistakes)