troubleshooting Question

How to diagnose results from tracert failing at cr81.fldfl.ip.att.net

Avatar of canuckconsulting
canuckconsultingFlag for United Kingdom of Great Britain and Northern Ireland asked on
NetworkingNetwork AnalysisNetwork Management
12 Comments2 Solutions264 ViewsLast Modified:
I am having trouble connecting to my company's VPN.  The results of a tracert to the vpn address are shown below and ultimately time out at cr81.fldfl.ip.att.net.  

Is this indicative of an AT&T fault?  If so, is there a way to locate that outage to follow its progress?

Tracing route to vpn.***.com [****]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  BThomehub.home [192.168.1.254] 
  2     *        *        *     Request timed out.
  3     *        *        *     Request timed out.
  4     6 ms     6 ms     6 ms  217.41.217.125 
  5    12 ms    13 ms    11 ms  212.140.235.218 
  6    12 ms    11 ms    11 ms  217.41.169.9 
  7    11 ms    10 ms    10 ms  217.41.169.107 
  8    10 ms    10 ms    10 ms  acc1-10GigE-3-3-0.sf.21cn-ipp.bt.net [109.159.251.91] 
  9    19 ms    19 ms    19 ms  core2-te0-13-0-2.ilford.ukcore.bt.net [109.159.251.11] 
 10    19 ms    19 ms    20 ms  109.159.254.197 
 11    17 ms    17 ms    17 ms  166-49-211-250.eu.bt.net [166.49.211.250] 
 12    18 ms    18 ms    18 ms  82.112.101.73 
 13    17 ms    16 ms    17 ms  ae-7.r23.londen03.uk.bb.gin.ntt.net [129.250.6.54] 
 14    20 ms    20 ms    20 ms  ae-0.r22.londen03.uk.bb.gin.ntt.net [129.250.4.85] 
 15    87 ms    86 ms    85 ms  ae-5.r24.nycmny01.us.bb.gin.ntt.net [129.250.2.18] 
 16    86 ms    86 ms    86 ms  ae-13.r05.nycmny01.us.bb.gin.ntt.net [129.250.4.71] 
 17    90 ms    87 ms    87 ms  ae-0.att.nycmny01.us.bb.gin.ntt.net [129.250.9.206] 
 18   128 ms   127 ms   127 ms  cr2.n54ny.ip.att.net [12.122.115.90] 
 19   129 ms   127 ms   127 ms  cr2.wswdc.ip.att.net [12.122.3.38] 
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22   121 ms   123 ms   124 ms  cr81.fldfl.ip.att.net [12.122.1.46] 
 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.
ASKER CERTIFIED SOLUTION
Join our community to see this answer!
Unlock 2 Answers and 12 Comments.
Start Free Trial
Learn from the best

Network and collaborate with thousands of CTOs, CISOs, and IT Pros rooting for you and your success.

Andrew Hancock - VMware vExpert
See if this solution works for you by signing up for a 7 day free trial.
Unlock 2 Answers and 12 Comments.
Try for 7 days

”The time we save is the biggest benefit of E-E to our team. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange.

-Mike Kapnisakis, Warner Bros