I think they may be.  I will have them give that a try.  They sent me 
their external IP address and I ended up with the same results trying to 
tracert back to them.  It seems to go astray at the medford charter.com 
backbone.  If that is what is happening.


On 2/2/2011 8:58 AM, Tony Zakula wrote:
> Are they a Charter customer?  If they are, have them call Charter.
> Their business tech support has always been excellent for us.  They
> should be able to pinpoint this pretty easy as they can usually go
> into the clients router and send a signal from there to anywhere else
> on their network.
>
> Tony Z
>
>
> On Wed, Feb 2, 2011 at 10:43 AM, Orin WellsHIDDEN@lls@awasco.com>  wrote:
>    
>> One of our clients reported that from one of their facilities outgoing email
>> was timing out on a regular basis.  I had him do a tracert to the server.
>> All was well as you can see from the results below.
>>
>> BUT when I did a tracert from my workstation back to any of the
>> mdfd.or.charter.com nodes (Medford, Oregon on Charter.com) I was told the
>> nodes were unreachable.  I then tried this from the server with the same
>> results.   I have never seen this before so I don't know if this is our
>> problem or if this is "normal" behavior for the charter backbone which may
>> allow tracert/ping traffic in only one direction.  Anyone have any thoughts
>> on this?
>>
>> I tried a tracert on the ip address from the email I got from the client
>> which may be a different physical facility I think but in the process of
>> verifying.  This worked to a point.  First the response time jumped to 130ms
>> once it hit Charter.com and then two hops later simply "timed out".   When I
>> did the same from the server all went well as it went from Seattle, to
>> Denver, to Chicago to Washington DC where it started timing out as it hit
>> Charter.com nodes but did respond from three Virginia nodes.  All on the way
>> from Seattle to Portland Oregon - less than 200 miles as the crow flies.
>> Sometimes you have to wonder about the efficiency of the network traffic
>> routing.
>>
>> Any ideas?  Can this be the problem?  That is Charter.com backbone or is
>> that how they always behave?  If so how in the world can one diagnose a
>> problem like this?
>>
>>
>> 1     *        *        *     Request timed out.
>>
>>    2     8 ms     7 ms     8 ms  acr01thdlor-gbe-1-30.mdfd.or.charter.com
>> [96.34.
>>
>> 104.50]
>>
>>    3    13 ms    15 ms    13 ms  acr01klflor-vln-20.klfl.or.charter.com
>> [96.34.10
>>
>> 4.20]
>>
>>    4    15 ms    14 ms    15 ms  dtr02mdfdor-vln-19.mdfd.or.charter.com
>> [96.34.10
>>
>> 4.106]
>>
>>    5    21 ms    18 ms    19 ms  crr01mdfdor-tge-0-1-0-2.mdfd.or.charter.com
>> [96.
>>
>> 34.105.226]
>>
>>    6    23 ms    23 ms    24 ms  tuk-edge-09.inet.qwest.net [67.148.50.33]
>>
>>    7    43 ms    42 ms    43 ms  63.146.27.218
>>
>>    8    43 ms    42 ms    44 ms  ae-7.r20.snjsca04.us.bb.gin.ntt.net
>> [129.250.5.5
>>
>> 2]
>>
>>    9    60 ms    60 ms    62 ms  ae-4.r20.sttlwa01.us.bb.gin.ntt.net
>> [129.250.3.5
>>
>> 2]
>>
>>   10    65 ms    61 ms    61 ms  po-2.r00.sttlwa01.us.bb.gin.ntt.net
>> [129.250.2.2
>>
>> 05]
>>
>>   11    60 ms    64 ms    64 ms  xe-7-3.r00.sttlwa01.us.ce.gin.ntt.net
>> [198.104.2
>>
>> 02.54]
>>
>>   12    63 ms    61 ms    62 ms  tge-4-3.cr0-c300.sea.accretive-networks.net
>> [207
>>
>> .246.129.22]
>>
>>   13    62 ms    62 ms    61 ms  mid-columbiahousingauthority.org
>> [207.66.134.61]
>>
>>
>>
>>      
>